AT-AT orbital strike bug on Hoth

Just confirming that this bug has appeared in multiple games where I play as the ATAT, and it does not seem to be associated with being struck by the ion weapons.  Sometimes I get one normal orbital strike, sometimes two, but after that the "R1" symbol just flashes, and you can turn OFF the call for an orbital strike, but you can't actually deploy it.  If there is a reason for the orbital strike not being able to fire a second time, then the icon for the orbital strike should not indicate that it is available to use.  

Yes, I played a game today where the first chance I had to use the orbital strike, it only displayed this bug, never got a chance to use the orbital strike even once.  It's like they made the ATAT behave the same way on Hoth as it does on Endor, which makes it pointless to play the ATAT anymore.  Obviously they tried to change something with the ATAT in the update, and this broke how it works.  

Here is the link to my video of orbital strike being broken on Hoth:

https://battlefront-forums.ea.com/discussion/96935/game-bug-atats-orbital-strike-broken-on-hoth/p1?new=1

Thanks for those videos.  I like playing the AT-AT, when it works it is a great vehicle.  But every other time, I see a new bug.  This past few weeks, I've seen:

Orbital strike fails to deploy

Orbital strike with no "red zone" when choosing target

Flashing "R1" (on PS4) which is stuck flashing and R1 does nothing. 

Heavy laser cannons fail to recharge after use

Primary weapons fails to go into cooldown

Ousted from ATAT before time runs out, and not at phase end

In the past, I used to have a weird bug where when I played the ATAT and it ran out of time just before switching to the hanger phase, I'd be respawned for no apparent reason when the phase changed.  I haven't seen that bug in a while, but I don't think I've been in that particular situation for a few weeks.  

I think it is worth pressing this issue, because it is not on the list of "known issues" that was put out a few days ago by EA in the forums.  There, they do talk about the hijacked ATAT on Endor not firing the orbital strike, but no mention of the glitchy ATAT on Hoth.  It is worth noting that it worked fine with no issues at all before the patch.  Something happened to the ATAT programming in the patch, and it has been quite broken in many ways ever since.  It is a shame, because it was a fun vehicle to play otherwise.  

Any word on whether this is going to get fixed in the next patch?  Wishful thinking maybe.....

**Sigh**

I think the orbital strike bug is related to range. If, for example, you fire it once and then try firing it at a farther distance than the first strike - it won't let you; if you try firing it at a closer distance - it fires occasionally.

Yes, I think they nerfed the range in patch 1.1 (though this detail was NOT in any of the patch notes), but that nerf didn't just affect the range, it affected the entire controls of the ATAT.  There were no other glitches on the ATAT before the patch (I played it with great success before the patch a number of times, so did others and they posted videos), and now it is hit and miss whether your controls for it are going to work.  The frustrating thing is that they had the ATAT right in Battlefront 1, where the "target" area appears red when you are out of range, and blue when it is all clear to call in a strike in that location, and this game only always shows the red, so we have absolutely no way of knowing where we can and can't call in a strike.  And it's a fine line, that is inconsistent depending on which ATAT you are in, and which points you have crossed.  Sometimes you can only strike very close to the ATAT, and some places you can call it in a lot further.  And now the ATAT on Endor is having some of the same glitches, and they are not range-related. 

When you fire the heavy laser canons, sometimes it fails to time out of deployment, in other words, you can fire the heavy lasers for an unlimited time, and it is during that time that the orbital strike goes into the state where it cannot be deployed.  It may be because of accidental hits on the controls where the two abilities are tying to deploy simultaneously.  So if the devs trying to fix this want to try something, try activating both abilities one immediately after the other.  Like, as fast as your trigger fingers can move.  That may be what is causing the problems.