[FIXED] weapon dialog differences??

[marksdoran]

I see a difference in the weapons/loadout dialog between the new game and the older C:MANO in the following case:

Steps to reproduce
1) start game
2) load scenario (these pics are from Northern Inferno pt3 fast and furious)
3) launch individual one F-5 with the Bullpup loadout
4) select the F-5
5) open weapons dialog (any method, all give same result)
6) notice difference in loadout display for aircraft hardpoints

I tried looking at aircraft loadouts in a couple of different scenarios under the new engine and the results seem consistent. Is this by design or did something get lost?? If this is by design, what's the recommended way to check what weapons are left on board once aircraft have started to expend weapons??

[ Sorry about the screenshot overlays -- I tried to upload two but apparently this forum s/w only allows one per post :p ]

[JOhnnyr]

ORIGINAL: marksdoran

I see a difference in the weapons/loadout dialog between the new game and the older C:MANO in the following case:

Steps to reproduce
1) start game
2) load scenario (these pics are from Northern Inferno pt3 fast and furious)
3) launch individual one F-5 with the Bullpup loadout
4) select the F-5
5) open weapons dialog (any method, all give same result)
6) notice difference in loadout display for aircraft hardpoints

I tried looking at aircraft loadouts in a couple of different scenarios under the new engine and the results seem consistent. Is this by design or did something get lost?? If this is by design, what's the recommended way to check what weapons are left on board once aircraft have started to expend weapons??

[ Sorry about the screenshot overlays -- I tried to upload two but apparently this forum s/w only allows one per post :p ]

Is it possible the + is just not being displayed? Can you click where it's supposed to be and have it open? Definitely seems like a problem..

[marksdoran]

No, there's no hotspot on the line where the loadout text appears to open the list and clicking where the list of drop tanks and weapons should be doesn't appear to link to the DB. I think it's just missing (...or not supposed to be there at all...but like I said, if not, then what's the alternative UI element to get at the same info -- yes you can get it from the manual attack dialog but that seems wrong given you have the designate a target to even get that far).

Ship weapons dialog looks fine, btw.

[JOhnnyr]

ORIGINAL: marksdoran

No, there's no hotspot on the line where the loadout text appears to open the list and clicking where the list of drop tanks and weapons should be doesn't appear to link to the DB. I think it's just missing (...or not supposed to be there at all...but like I said, if not, then what's the alternative UI element to get at the same info -- yes you can get it from the manual attack dialog but that seems wrong given you have the designate a target to even get that far).

Ship weapons dialog looks fine, btw.

Seem like a bug then?

[marksdoran]

Hmm, ok well I wish this board software would let me edit the title for the thread :/

Hopefully one of the relevant people will see this. Or is there a bug tracker that I'm supposed to log things into like this??

[JOhnnyr]

ORIGINAL: marksdoran

Hmm, ok well I wish this board software would let me edit the title for the thread :/

Hopefully one of the relevant people will see this. Or is there a bug tracker that I'm supposed to log things into like this??

You are good, I was more or less bumping this for better visibility.

[LargeDiameterBomb]

I am encountering this problem as well so I'm glad you reported it. I don't want to overwhelm the developers right now so I'll wait and see if this is solved now when it's been reported.

Interestinlgy, the exact same problem has also happened one time before for me when a CMANO update was rolled out maybe 2 years ago and then the problem was solved with a new build after a quite short while and I was only lurking back then so I couldn't make a bug report.

[Dimitris]

Thanks! Logged as a high-priority issue.

[Dimitris]

Fixed for the next public update.