This is still happening. It'd be nice to get a fix on it.
Four months later...still not addressed. I mostly notice this on maps where there is a vehicle objective. If you aim the torpedo at an AAT, the torpedo locks onto the AAT, then is fired at the locked MTT objective, dealing no damage. I'm sure this is not working as intended ("Let's make a weapon that can't be fired at the target it is locked on to, players will really like that," said no one ever). If the ion torpedo is locked onto an MTT with shields down, then the torpedo often does NOT get fired at the MTT, especially if there is an AAT or ion turret in the proximity of the MTT. This makes no sense. And this has been happening for a long time and should have been fixed ages ago.
It's been over a year since this bug was first reported, in a number of threads, and it is still a problem. I would have hoped that this bug wouldn't appear in the new mode, but it does. For example, you can lock torpedo onto an enemy turret, but it fires off in a different direction at a dead AT-RT instead, even if the player never locked on to the AT-RT in the first place. Another place where this is problematic is on Crait, where torpedos fire onto the massive walkers after the first phase, when those walkers aren't even a possible target anymore. Carefully aiming the torpedos at an intended target, such as an AT-ST, does not help.
I envy you for your patience. They fail in respecting you (a Champion), yet you never fail in respecting them. Bravo. Fortunately for me, I rarely use these types of locking on attacks/abilities, so I don't get frustrated by this BUG. But I can confirm this has already happened to me, in the case of the Heavy's Ion Torpedo. I'll add that case to my testing cases for my next round of tests.
I suppose the locking-on is actually just an unrelated pre-req to fire homing weapons. As the AT-ST has a homing missile that doesn't need to lock-on first, it's clear this game does have homing weapons that don't require a lock-on. So I assume the lock-on serves as a pre-req to fire the guided projectile, but it's when it's launched that it selects the target, not during the lock-on moment. And if they have different ways to select a target, like the lock-on being more restrictive in angle and distance, while the homing projectile just choosing the closer target inside your LoS, this discrepancy is enough to cause the issue you described.
Anyway, these are just suppositions, I'll need time and many tests to try to reach any conclusion on this. As for DICE I hope it stops ignoring this report.
