[FIXED] Units not engaging inbound missiles

[Currahee150]

Ok I need some adult help now. Been getting some really weird behavior. Units will auto engage targets I designate with the Shift key, but inbound supersonic ASMs don't seem to a concern to CGs. Sometimes they shoot, oftentimes they do not. In the attached autosave, ESSMs should be able to shoot, as according to manual engagement, but they do not. In exasperation, I have allowed ROE weapons free and opportunity targets, however while that depletes my MMT magazines, the SAMs still don't behave reliably. Additionally, in the allocate weapons dialogue box, there are often allocated weapons even if they haven't been ordered to fire yet (for example one DDG already had like 200 something ESSMs allocated to targets for some reason.
Will fully acknowledge that there may be some ROE button or rule I missed in an update, but either way I just want to know what's going on. Have latest steam build.

Edit: I see, now that I actually looked at other tech complaints (sorry...), that this has already been reports and is being worked on...in that case just consider this as another data point for solving said bug.

[Geoffropi]

Hello and thanks for your report,

Could you send us the exception log as well ?
We probably already fixed that (for the next build) but we'd like to confirm.

[DWReese]

I'm fairly certain that this bug is related to a bug that I reported a while back.

If a ship has a weapon that could fire, but is restricted by ROE/WRA and that weapon is the longest ranged weapon, then the platform will not shoot.

In other words, say a ship has a RIM 161E, and RIM 174. If an incoming missile is detected, and the RIM 161 could shoot, but you have restricted it to only shoot at ballistic weapons, then it won't shoot. The problem is, the program will then not fire any other weapon since the longest shooter is restricted from firing.

Note: By using the editor and removing the long range weapon, the others start right up and begin firing.

[Dimitris]

This should be fixed in Build 1328.11.

[Currahee150]

Could you send us the exception log as well ?

Of course!...How do I do it? (pardon my ignorance).