Two different EMPluse SWs affect each other while targeting

Bug #1428208 reported by AetherDawn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ares
Fix Released
High
AlexB

Bug Description

Two different Type=EMPluse SWs.

SuperWeaponA
AutoFire=yes
AITargeting=xxx (eg. Self or Base)
EMPulse.Cannons=A

SuperWeaponB
AutoFire=no
EMPulse.Cannons=B

If you fire SuperWeaponB a bit sooner or later than the moment that SuperWeaponA fires:
sometimes SuperWeaponB may fire at SuperWeaponA's AITargeting instead of your selection,
and sometimes SuperWeaponA may fire at your selection for SuperWeaponB instead of its own AITargeting.

AetherDawn (aetherdawn)
summary: - something weird about EMPluse SW
+ Two different EMPluse SWs affect each other while targeting
Revision history for this message
AlexB (alexander-b) wrote :

This also happens for the Nuke, as there are two fields on HouseClass that store the coordinates for both SW types. Firing one type more than once in rapid succession resets the target before the earlier launches are complete. This could be fixed by putting the target coordinates on the building itself.

Changed in ares:
status: New → Triaged
importance: Undecided → Medium
importance: Medium → Low
Revision history for this message
lovalmidas (lovalmidas) wrote :

Just a sidenote that SuperWeaponA and SuperWeaponB must belong to the same house to observe this effect. I have yet to see this issue occurring between superweapons owned by other houses.

Revision history for this message
AlexB (alexander-b) wrote :

That can't happen. The target coordinates are per-house, that means it always uses the same coords for each player regardless of the SW that fired, but it does not share the this information between players. Each player got its own target location variable.

Revision history for this message
mevitar (mevitar) wrote :

Fixed in 15.286.681

AlexB (alexander-b)
Changed in ares:
milestone: none → 0.a
assignee: nobody → AlexB (alexander-b)
importance: Low → High
status: Triaged → Fix Committed
AlexB (alexander-b)
Changed in ares:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.