[FIXED] Build 1776 various pop-ups on scen open

[TempestII]

Not quite sure what is happening here but there's multiple pop-ups when I open up a scenario I'm working on in build 1776.
Scen and Exception Log attached in one zip file.

20260104 - CMO 1776 Various Error Windows.jpg (473.3 KiB) Viewed 207 times

20260104 - CMO Exception Issues 1776.zip

(1.06 MiB) Downloaded 12 times

[Raptorx7_slith]

This appears to be fixed in the latest beta version as I'm not seeing any of these pop-ups when loading your scenario

[Nikel]

Still may happen in the last build.

It is very difficult to reproduce because apparently is related with the cached RAM.

I do not know the correct words, but the cached memory has to be completely clean of CMO use to reproduce it, if not the exceptions are hidden?

Used this software to clear the cached RAM. Then the fuse exceptions may appear on the screen when you run the scenario. Still may not happen, but it is the best way. Perhaps there are better tools to clear the RAM.

Of course before that just tried to restart the laptop, but did not happen. There must be some randomness in the exceptions.


https://learn.microsoft.com/en-us/sysin ... ads/rammap

18-02-2026 19:02:09!!!WARNING!!! EXCEPTION FUSE REACHED (x8000 exceptions) FOR : -- Bv1.09 RC - Build 1817 -- Object reference not set to an instance of an object. -- Scen : 2026 NATO Summit Showdown -- DB : -- Exception: Object reference not set to an instance of an object.
Stack Trace: at Command_Core.Side.get_UnitsEngagedInOECM(Boolean Refresh)
Call Stack & Error details:
Error at 101060:

18-02-2026 19:02:24!!!WARNING!!! EXCEPTION FUSE REACHED (x160000 exceptions) FOR : -- Bv1.09 RC - Build 1817 -- Object reference not set to an instance of an object. -- Scen : 2026 NATO Summit Showdown -- DB : -- Exception: Object reference not set to an instance of an object.
Stack Trace: at Command_Core.ActiveUnit_CommStuff.get_CommJamUnitsAreAffectingMe()
Call Stack & Error details:
Error at 100240:

ME.png (80.37 KiB) Viewed 79 times

[amizaur]

It happened again for me - with 1817 . When trying to load ANY scenario.
Yesterday 1817 worked for me. Today not.

(last time it happened in 1774, ceased for me with 1776).

1817 bug.jpg (588.53 KiB) Viewed 37 times

Seems like the game cant't see the database. When I try to Create a New Blank Scenario, and then Database Viewer - I can't display any data for any plane/ship/weapon.

bug2.jpg (307.93 KiB) Viewed 37 times

[Nikel]

It happened again for me - with 1817 .

(last time it happened in 1774, stopped with 1776).

in what scenario?

[amizaur]

In any scenario. Can't load any scenario, either standalone or battleset or Workshop.

[Nikel]

OK, that must be a another problem, the errors are different. Perhaps the db file was corrupted.

The devs want only 1 problem per thread, it is better that you start a new one