Ares

Control groups and InitialPayload

Bug #1589697 reported by mevitar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ares
Fix Released
Low
AlexB
Ares 0.c

Bug Description

If a unit has anything under the InitialPayload.Types= tag, the control group number won't show for it. All other units show their control groups when selected, but not those with InitialPayload.

Buildings are unaffected by this bug.

Revision history for this message
mevitar (mevitar) wrote :

Just a note: it seems to be like this since the first build that InitialPayload was introduced (15.322.1295, if i checked correctly).

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

I tested with AllowedToStartInMultiplayer=yes units and units built from the War Factory. I see the group number when selecting the unit in both cases.

Revision history for this message
mevitar (mevitar) wrote :

They have PipScale=Passengers, right? Try without it.

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

I can reproduce this. Grouping the transport will not show a number if there are passengers inside, no matter whether it's initial payload or manually added passengers.

Changed in ares:
status: New → Triaged
AlexB (alexander-b)
Changed in ares:
assignee: nobody → AlexB (alexander-b)
milestone: none → 0.c
importance: Undecided → Low
status: Triaged → In Progress
Revision history for this message
mevitar (mevitar) wrote :

16.162.1040, it is now fixed.

AlexB (alexander-b)
Changed in ares:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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