[FIXED] 1307.9 Order of battle Exception

[Epsilon442]

Opening the order of battle screen from the game menu causes an exception. This only occurs in the scenario editor and not when playing a scenario normally.

Desktop Screenshot 2023.03.19 - 13.28.20.72.png (4.3 MiB) Viewed 733 times

Desktop Screenshot 2023.03.19 - 13.27.06.76.png (4.69 MiB) Viewed 733 times

[KnightHawk75]

Opening the order of battle screen from the game menu causes an exception. This only occurs in the scenario editor and not when playing a scenario normally.
Desktop Screenshot 2023.03.19 - 13.28.20.72.png
Desktop Screenshot 2023.03.19 - 13.27.06.76.png

Can you post a save? I can't repo in 1307.9 loading a random scene and selecting oob, meaning it may have to do with the case of what's in the contents of what would be in the oob.

[Epsilon442]

As this only occurs in the scenario editor I can give you the .scen file. Its a large work in progress scenario with 1683 active units so that may contribute plus I have used the import/export function to bring in units//installations from another scenario. You should be able to just load the scenario and press O to replicate the exception.
EDIT: attached the wrong save should be fixed now

[KnightHawk75]

Thanks, Hopefully it's helpful to devs.

I loaded it (post edit..) under 1307.9 on fresh restart of the game in the editor and while it took a second or so, it came up.

1309_OOBViewerNewUkr2.jpg (1.17 MiB) Viewed 683 times

Tried it from launching edit scene.
Tried it from launching create new scene then file\load.
Tried it from launching create new scene then file\load recent.
Tried if from launching edit scene, then tried it on each side successfully.
Was there a certain order of events, or does it not matter on your system and it always comes up?

[Epsilon442]

Its hard to pin down I had it couple of times the exception is non fatal so you can just dismiss the message and then reopen the OOB and everything appears to works. I had the exception once just loading into the scenario and pressing OOB button. The second time I was just testing some radar detections so I had lunched some Russian jets and then let the scenario run for a minute at speed 5 before paused before opening the OOB. Hopefully the devs will be able to make something out from the exception error message. Some additional information I am running the steam version of the game with the beta update applied. I am also using windows 11 so that's another potential complication.

Edit: I had been playing with the previous beta for about 20hours including a couple on the offending scenario and had never had any problems with the OOB window. it appears to have started after updating to the new beta.

[Dimitris]

Logged #14927

[Deserere]

Hi Epsilon442, the issue is fixed, it will be included in the next update release, thanks for highlighting this and let me know if any problem persists.