Submit Feedback

Crashes since new update.

Lancelotepalote shared this bug ago

Submitted

System.InvalidOperationException: Nullable object must have a value.

at Keen.Game2.Client.WorldObjects.Tools.IntegrityToolUIComponent.UpdateUI(Entity target)

IntegrityToolUIComponent is the on-screen readout for your welder or grinder: the integrity bar and block info shown when you aim at something. The game expected the block you were aiming at to have a value, found nothing, and didn’t handle it, so it crashed instantly. Both times it happened in the “Base done” save while you were holding a welder or grinder.

The game was unmodded (only Vanilla and Engine were loaded), and memory and disk were fine. The 11:37 crash happened about 40 seconds after the game removed a Gladius wreck and spawned a new outpost. The likely trigger is aiming your tool at a block or debris piece that was being removed or wasn’t fully loaded yet. That fits a block whose data is missing.

Crash 3 (19 Oct, 12:38) was a different bug, in an older game version (2.4). It happened while the game was shutting down: closing the colonization map / terminal screen gave a camera error (Camera EOB not matching). The game has been updated since then, so that one may already be fixed.

What you can do:

Until Keen fixes it, when you’re near wrecks or encounters that are spawning or despawning, don’t hold the welder or grinder up and scan across blocks. Put the tool away and take it out again once things have loaded.
If it always crashes on one particular block or grid, grinding it down or avoiding it should stop the crashes.
Report it on the Keen support site or Discord (the error line above is enough). Your last crash report didn’t reach Keen because their upload server returned an error. The full report is in %APPDATA%\SpaceEngineers2\Temp\CrashReports if you want to attach it.
Your autosaves are intact, so you haven’t lost progress beyond the last autosave.

I have the same bug

Replies (1)

Lancelotepalote ●

crashed as well a few times here:

What happened (17:00:51, save “Base done - Copy”):

At 17:00:50 you opened the terminal on a reactor. The log shows Reactor250_ClientComposition.
Less than a second later, the game tried to load the images for that screen. One of them (probably an item or block icon) had no file, and the game reported GUIAsset <undefined> is not valid. Expected a valid GUIAsset with a non-empty Id.
The render thread then failed to load it (Failed to allocate … ResourcePinEntity_UIResourcePinningManager) and the game crashed.

The game is unmodded, so the missing icon is a bug in Space Engineers 2 itself. The likely suspects are something inside that reactor’s inventory (a fuel or other item with no icon) or the reactor’s own terminal panel. You had about 10 GB of 11.5 GB of video memory in use, which is high but not the cause; the error is about the missing image, not a lack of memory.

What to try:

Don’t open that reactor directly for now. If you need its settings, open a different block’s terminal on the same grid and switch to the reactor from there. If that screen also shows its inventory, it may crash too.
Empty the reactor using conveyors or another container, so whatever odd item is in it moves out. If the crash goes away, that item was the problem.
Verify the game files in Steam (right-click Space Engineers 2 → Properties → Installed Files → Verify integrity). It’s quick, and it rules out a damaged icon file on your side. DONE
If it keeps happening with every reactor, report it to Keen with the error line from step 2. The crash report is CrashReport_261020_165712_052_7524.vrg-crash in %APPDATA%\SpaceEngineers2\Temp\CrashReports.

Reply URL