[RESOLVED] B1817 multiple errors, game can't acces database, game won't launch

[amizaur]

edit: I wish I noticed THIS line before installing B1817 and creating this thread: "If you have installed CMO only through Steam, wait for it to become available on the Steam public-beta branch." I wonder now if this was the cause of my problems...


Hello there,

I'd like to report an error (or issue) I first encountered with B1774, then it seemed fixed in B1776, and now it returned in B1817. It seems to affect only Beta versions. The Steam official release version works fine. I run a PC with Windows 10 Home, up to date. Recently I replaced mainboard in my PC, but IDENTICAL problems were already happening with B1774 on old mainboard.

It goes like this - game (Beta 1776) works fine. I install a new beta version, this time B1817. Game launches normally (trough Steam or directly) and still works fine. I do some playtesting with new A2A missiles features (more on this in another thread) and all works great.
Next day I launch the game, try to load a scenario (ANY scenario) and I got multiple database related errors. Like this:

1817 bug.jpg (588.53 KiB) Viewed 466 times

I try few times, game launches but I got errors trying to load a scenario, or when I try to open editor and browse the database I see there is no acces, can't see and aircraft/ship/weapon data:

bug2.jpg (307.93 KiB) Viewed 466 times

Then at some point game doesn't want to launch anymore. I click "start" in Steam, launcher pops up, I click "play", game starts to load and... nothing happens, after few seconds the "start" button in Steam is active again. Trying to launch the game executable directly gives same results (some HDD activity then stop). Reboot the computer - no change.

I checked some things. Like file access authorisations. I even moved whole game folder to a different physical disk. I updated .NET framework. Last time (when I had the SAME problem in B1774) I reinstalled whole game. Didn't help.

I did some experiments - tried to launch CMO 1817 main executable with older game files (basically 1674 offical public release installation with only v1817 CMO.exe replaced - of course it didn't work). Then I tried the reverse - to run old game executable (1674) with all beta 1817 game files - and it worked fine). But after replacing 1674 CMO.exe with 1817 CMO.exe - game ceases to start.

Reverting to beta 1776 or 1774 doesn't solve the problem. Only after reverting to official public release 1674 game runs normally.

Now at this moment for some reason (unknown to me) the 1817 again launches, but fails to load any scenario.

I used Sysinternals ProcessMonitor to maybe pinpoint cause of the problem, and is seems problem arises when 1817 tries to acces the database, but I'm not qualified enough in database management to understand cause of the problem. I can send the ProcessExplorer logs if it helps.

The 1817 version also writes some errors to ExceptionLog when I try to acces database, entries like this:

Code: Select all

20.02.2026 21:18:43 -- Bv1.09 RC - Build 1817 -- Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu. -- Scen :  -- DB : 57334daf25e33862c175b267a67b3b66b3ff82c7 -- Exception: Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
Stack Trace:    w Collections.Pooled.PooledList`1.Add(T item)
   w Command_Core.ActiveUnit.GetAllSensors()
   w Command_Core.ActiveUnit.Sensors_ReadOnly()
Call Stack & Error details: 
Error at 101185: 

20.02.2026 21:18:43 -- Bv1.09 RC - Build 1817 -- Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu. -- Scen :  -- DB : 57334daf25e33862c175b267a67b3b66b3ff82c7 -- Exception: Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
Stack Trace:    w Command_Core.ActiveUnit.get_HasEmittingRadars()
Call Stack & Error details: 
Error at 101186: 

20.02.2026 21:18:43 -- Bv1.09 RC - Build 1817 -- Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu. -- Scen :  -- DB : 57334daf25e33862c175b267a67b3b66b3ff82c7 -- Exception: Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
Stack Trace:    w Collections.Pooled.PooledList`1.Add(T item)
   w Command_Core.ActiveUnit.GetAllSensors()
   w Command_Core.ActiveUnit.Sensors_ReadOnly()
Call Stack & Error details: 
Error at 101185: 

20.02.2026 21:18:43 -- Bv1.09 RC - Build 1817 -- Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu. -- Scen :  -- DB : 57334daf25e33862c175b267a67b3b66b3ff82c7 -- Exception: Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
Stack Trace:    w Command_Core.ActiveUnit.get_HasEmittingJammers()
Call Stack & Error details: 
Error at 101186: 

[code]20.02.2026 21:18:43 -- Bv1.09 RC - Build 1817 -- Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu. -- Scen :  -- DB : 57334daf25e33862c175b267a67b3b66b3ff82c7 -- Exception: Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
Stack Trace:    w Collections.Pooled.PooledList`1.Add(T item)
   w Command_Core.ActiveUnit.GetAllSensors()
   w Command_Core.ActiveUnit.Sensors_ReadOnly()
Call Stack & Error details: 
Error at 101185: Error in Exception Handler! OnThreadException
theEx != null
Exception Type: System.NullReferenceException
Message: Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.
StackTrace:    w Command.InternalDBViewer.DisplaySensors(ActiveUnit AU)
   w Command.InternalDBViewer.DisplaySatellite(Satellite theSat)
   w Command.InternalDBViewer.DisplayInfoInDetailsPanel(Int32 _SelectedObjectID, String _SelectedObjectType)
   w Command.InternalDBViewer.DisplaySelection(Boolean ApplyKeywordFilter, Boolean RetainPlatform)
   w Command.InternalDBViewer.LwCyj99Q9ul(Object  , EventArgs  )
   w DarkUI.Controls.DarkListView.SelectItem(Int32 index, Boolean ThrowE)
   w DarkUI.Controls.DarkListView.OnMouseDown(MouseEventArgs e)
   w System.Windows.Forms.Control.WmMouseDown(Message& m, MouseButtons button, Int32 clicks)
   w System.Windows.Forms.Control.WndProc(Message& m)
   w System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Any idea what causes this behaviour, what could the problem be ? I am aware than it may be something untypical on my computer that causes this, but can you help me understand what the source of the problem may be, what should I check or fix beside reinstalling Windows ?

[Dimitris]

You installed B1817 on top of a Steam installation?

If yes, that is probably the source of the problems. We made this available separately as a full-fileset pack because there are a lot of significant file changes.

[amizaur]

Well, yes and no.

First I extracted B817 to Steam game folder (overwriting files). It worked but only few times, then stopped.
After that I tried to run it separately too, from a different folder (only B817 extracted there) and it doesn't work either.

B825 (separate folder) starts, but can't acces database or load any scenario (=stream of errors).

[Dimitris]

At this point it is difficult to ascertain what is broken because of inherent issues in the update, and what broke because you didn't follow the instructions properly.

Please nuke the site from orbit and start again.

[amizaur]

How should I understand a "nuke" ? Uninstalling CMO completly by Steam, restarting computer and installing CMO again would be enough to clean any possible user errors ?

I see the B825.11 is available on Steam now, so this time I can just select Beta instead of unzipping into separate folder.

[YuriyAntropov]

Same erorr...

[YuriyAntropov]

Same erorr...

!Update:
Errors no longer occur and the game launches correctly after I deleted the CMO_WebView2Cache folder from C:\Users\***\AppData\Local + be sure to rename or delete the folder with the previous game version from the root directory (I had version 1776) + run as administrator + without antivirus + cleared the RAM of the old background process with the previous version of CMO.

If this helps, change the thread title to [FIXED]

[amizaur]

Thanks ! Unfortunately for me it didn't help. The game launches, but still can't acces database.
I'm nearly desperate enough to reinstall windows .

[Nikel]

I would try reinstalling webview2 first.

https://developer.microsoft.com/en-us/m ... H#download

[amizaur]

I tried again, after rebooting and run it as administrator and now it works, starts the game and loads scenarios ! Seems the cache was not cleared completly at the first try.

Thanks man !!

I'll try to reinstall webview2 anyway, and try to run it normally (without administrator rights) to narrow the source of the problem, but I think the thread can be marked as FIXED already.

[Nikel]

I have tried a pair of programs to clear the cached RAM, and this is simple and works, it is free.

https://www.wagnardsoft.com/forums/viewtopic.php?t=1256

[Dimitris]

Marking as resolved.