KnightHawk75
Posts: 1450
Joined: 11/15/2018 Status: offline
|
FWIW - I too ran this under build 1147.35, ran for about 5hr, first ~2hr(about 1.5 hour in game) letting the scene play itself, then I kinda went to town destroying stuff from both sides for a couple hours, and adding a couple things as well. start: 0.9-1.2gb end: 1.3-1.6gb Did nothing much really other then press play and click close+resume on messages, and make sure the warhorse strikers didn't rtb before firing at ships for the first ~1 - 1.5hr in game. Then played mostly at 2x for 2-3 more hours in game. I did not move around the map much loading map data and only had bmng+borders enabled, internet blocked. Logs showed 2 exceptions during the first ~hour, one (the last one) I know was during an autosave attempt during the tail end of first hour of barely touching anything: quote:
11/14/2021 5:38:16 AM -- B1147.35 -- Object reference not set to an instance of an object. Exception: Object reference not set to an instance of an object. Stack Trace: at Command_Core.Aircraft_AirOps.(Boolean& , ActiveUnit& , Boolean , List`1 , String& ) Call Stack & Error details: Error at 200293, Object reference not set to an instance of an object. 11/14/2021 6:12:57 AM -- B1147.35 -- Collection was modified; enumeration operation may not execute. Exception: Collection was modified; enumeration operation may not execute. Stack Trace: at System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource) at System.Collections.Generic.List`1.Enumerator.MoveNextRare() at System.Collections.Generic.List`1.Enumerator.MoveNext() at Command_Core.Scenario.(XmlWriter ) Call Stack & Error details: Error at 101022, No out of memory exceptions though. This one popped sometime late in the blowing stuff up phase when I was about done. quote:
11/14/2021 8:37:06 AM -- B1147.35 -- Object reference not set to an instance of an object. Exception: Object reference not set to an instance of an object. Stack Trace: at Command_Core.ActiveUnit_DockingOps.() at Command.UnitStatus_WPF.(Scenario , Side , Unit ) at Command.UnitStatus_WPF.(Scenario , Side , Unit ) at Command.RightColumnWPF.(Scenario , Side , Unit ) Call Stack & Error details: Error at 999999, I don't what that was from whatever it was I didn't notice when it happened, perhaps a gui hicup. Anyway when I ended memory was around 1.3gig, peak memory during the whole session never broke 1.65gb. quote:
I also found that the saving a scenario will probably not save the "radar" detection/guidance state of missiles. Definitely add that like Dimitris said to a new thread, could be a nice find and explain some oddities on reloading saves.
|