[1900.23] Object reference not set to an instance of an object.
Posted: Sun Oct 18, 2026 1:41 pm
When trying to load a savegame that loads fine on the latest non-steam beta.
What's your Strategy?
https://forums.matrixgames.com:443/
Code: Select all
!!!WARNING!!! EXCEPTION FUSE REACHED (x20 exceptions) FOR : -- Bv1.10 - Build 1900.23 -- Referencia a objeto no establecida como instancia de un objeto. -- Scen : -- DB : 2fe4bc37289e9a7cafe2c36bc2e80627d3c1b8f7 -- Exception: Referencia a objeto no establecida como instancia de un objeto.
Stack Trace: en Collections.Pooled.PooledList`1.Add(T item)
en Command_Core.Scenario.TrdMAvE9op3(Object , DictionaryChangedEventArgs`2 )
Call Stack & Error details:
Error at 200568: Referencia a objeto no establecida como instancia de un objeto.!Load assembly: CMORTMP, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null from E:\Games\Command Modern Operations\CMORTMP.dll
!Load assembly: PlayFabClient, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null from E:\Games\Command Modern Operations\PlayFabClient.dll
Well, I think you found it
mikerohan wrote: Sun Oct 18, 2026 7:48 pm Haven't found what software could be interfering![]()
Seems very strange that something like this can prevent loading a save file though. But software is software, so I have checked the log and...
That could be pointing to CMORTMP.dll and/or PlayFabClient.dll... They seem related to Multiplayer.Code: Select all
!!!WARNING!!! EXCEPTION FUSE REACHED (x20 exceptions) FOR : -- Bv1.10 - Build 1900.23 -- Referencia a objeto no establecida como instancia de un objeto. -- Scen : -- DB : 2fe4bc37289e9a7cafe2c36bc2e80627d3c1b8f7 -- Exception: Referencia a objeto no establecida como instancia de un objeto. Stack Trace: en Collections.Pooled.PooledList`1.Add(T item) en Command_Core.Scenario.TrdMAvE9op3(Object , DictionaryChangedEventArgs`2 ) Call Stack & Error details: Error at 200568: Referencia a objeto no establecida como instancia de un objeto.!Load assembly: CMORTMP, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null from E:\Games\Command Modern Operations\CMORTMP.dll !Load assembly: PlayFabClient, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null from E:\Games\Command Modern Operations\PlayFabClient.dll
I'm not on multiplayer today so I did a final test: Renamed CMORTMP.dll and voilà. The save is up and running and no exceptions in the log. I have been playing for an hour now with no issues.
I do not know if this gives some kind of hint or not, but at least I get to play![]()
Hi,blu3s wrote: Tue Oct 20, 2026 5:48 pmmikerohan wrote: Sun Oct 18, 2026 7:48 pm Haven't found what software could be interfering![]()
Seems very strange that something like this can prevent loading a save file though. But software is software, so I have checked the log and...
That could be pointing to CMORTMP.dll and/or PlayFabClient.dll... They seem related to Multiplayer.Code: Select all
!!!WARNING!!! EXCEPTION FUSE REACHED (x20 exceptions) FOR : -- Bv1.10 - Build 1900.23 -- Referencia a objeto no establecida como instancia de un objeto. -- Scen : -- DB : 2fe4bc37289e9a7cafe2c36bc2e80627d3c1b8f7 -- Exception: Referencia a objeto no establecida como instancia de un objeto. Stack Trace: en Collections.Pooled.PooledList`1.Add(T item) en Command_Core.Scenario.TrdMAvE9op3(Object , DictionaryChangedEventArgs`2 ) Call Stack & Error details: Error at 200568: Referencia a objeto no establecida como instancia de un objeto.!Load assembly: CMORTMP, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null from E:\Games\Command Modern Operations\CMORTMP.dll !Load assembly: PlayFabClient, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null from E:\Games\Command Modern Operations\PlayFabClient.dll
I'm not on multiplayer today so I did a final test: Renamed CMORTMP.dll and voilà. The save is up and running and no exceptions in the log. I have been playing for an hour now with no issues.
I do not know if this gives some kind of hint or not, but at least I get to play![]()
That DLL shouldn't be related at all but it's definetely strange, can you confirm that with the renamed CMORTMP.dll you no longer has the issue and if you get back to the original name the issue is again present?