Dgun prioritisation (for coms)#5764
Conversation
Does some manual shenanigans to gurantee that a dgun will (eventually) be prioritised over a set target/force fire command.
|
Issue is reproducable by setting forcefire/set target and then dgunning the opposite direction. Not really an issue for small or 0 aim deviations, but I assume it's the underlying cause of some dguns not firing. Doesnt feel like a clean fix, though I used it for Dante too. PR is more to get the ball rolling and some insights. From observation, it seems that it's set target and forcefire that conflict with dgun orders, while a commander given a stop command and as such has no target set, prioritises it's dgun without need for workaround even if it shoots other things inbetween. I've tried to unset the target through Spring.SetUnitTarget and the Unitrules param "target_type" as the unit_target_on_the_move gadget does it, but that didnt seem to do the same thing as a stop command, with some linger data that I assume causes the resulting jittering/aim conflict. |
A workaround attempt to avoid forcefire/settarget from conflicting with dgun commands.