[SPZ2-5907] [1.0.0-ALPHA5-RC2] PSOD loading save. | Shapez 2 | Page 1

crystal notch Mar 11, 2026, 8:30 PM

#

53GB RAM used.

warm hearthBOT Mar 11, 2026, 8:30 PM

#

Thank you for reporting this bug! Our team will review your report soon.
Feel free to add more details in follow-up messages — we're also scanning for duplicate reports automatically now.
📨 There are currently 22 reports awaiting team review. Due to the high volume, it may take a little longer for us to get to yours.

📋 Log files help us investigate issues. You can find yours here:
• Windows: %USERPROFILE%\AppData\LocalLow\tobspr Games\shapez 2\Player.log

💾 Savegame files (.spz2) are very helpful if relevant to the issue!
Export via Main Menu → Play → click the download icon on the relevant savegame.
You can also find them here:
• Windows: %USERPROFILE%/AppData/LocalLow/tobspr Games/shapez 2/

crystal notch Mar 11, 2026, 8:30 PM

#

📎 backup-v2-2026-3-11--16-21-37--2305963.spz2

warm hearthBOT Mar 11, 2026, 8:30 PM

#

crystal notch

💾 Test2

⚠️ Cheats Used — results may differ from normal gameplay

Version

1.0.0-alpha5-rc2

Scenario

Classic - Regular

Seed

0

Research

100%

Buildings

1,775,616

Completed

Yes

crystal notch Mar 11, 2026, 8:31 PM

#

📎 Player.log

warm hearthBOT Mar 11, 2026, 8:31 PM

#

crystal notch

📋 Log File Analysis

Log Analysis (Player.log):

System.Exception: Menu savegame version 1129 is below minimum supported version (1130), thrown in BackgroundSavegameOptionsFactory.PrepareExistingMenuSavegame (occurred multiple times).
OutOfMemoryException: Out of memory when setting list capacity in SimulationCluster.Init, called from SimulationGraph.CreateCluster (occurred multiple times).
AggregateException: Rethrown wrapper around the OutOfMemoryException, surfaced in GameSessionOrchestrator.FinalizeLogicUpdate during Task.Wait (occurred multiple times).
D3D11 Error: Failed to create RenderTexture at 2560 x 1440 (formats 27 and 19, aa 1) with error code 0x887a0005.
SymGetSymFromAddr64 Error: SymGetSymFromAddr64 failed with message "Attempt to access invalid address" at address 00007FF93D859D6C.

#

1. [SPZ2-3578] — 👀 62% similar

Specific Savegame does not Load: Fatal Error
Done • Priority: Highest • Fix: Version 0.0.9 • Game: 0.0.8-rc2 • Resolution: Done

A specific savegame fails to load and causes a fatal error. The savegame contains approximately 2000 structures and may have been corrupted due to a previous master branch issue. When left on the menu screen, the player log file grew to over 9 GB. Another larger savegame with 200,000 structures loads without problems, indicating the issue is specific to this corrupted save. The bug was caused by a version mismatch when the savegame was created between two parallel feature merges.

#

2. [SPZ2-4960] — 👀 60% similar

Unable to load Operator Level 184 save
Done • Priority: Highest • Fix: None • Game: 0.1.1 • Resolution: Won't Fix

User cannot load their Operator Level 184 Savegame. After importing and clicking play, the game remains on a continuous loading screen indefinitely. The issue occurred after the user attempted to upgrade their Operator Level, experienced a crash, and upon reopening found their Research Credits and Speed Multiplier in an incorrect state. The save became incompatible and cannot be loaded. The user reports having many Trains in the save.
💬 Threads: [0.1.1] Possible issue with with researc

#

3. [SPZ2-3053] — 👀 58% similar

Fatal Error: Savegame does not load (from Friday)
Done • Priority: Highest • Fix: 4 - Early Access • Game: 0.0.0-alpha23.1 • Resolution: Done

Savegame files from Friday with 100% completion fail to load with fatal errors. The issue occurs when trying to load these saves, with errors indicating the menu Savegame is below the minimum supported version (1032 vs 1082) and null reference exceptions in FluidPortSystem. Savegame files at 5% completion with 100 Structures load without issues. The problem may be related to Mods, though all old Mods and Savegame files were removed from the drive. The issue has been verified as fixed after a ...

#

4. [SPZ2-3697] — 👀 55% similar

[0.0.9 RC4 crash loading RC3 save]
Done • Priority: High • Fix: Version 0.0.9 • Game: 0.0.0-alpha23.2 • Resolution: Done

A slightly edited savegame that worked in version 0.0.8, RC1, and RC3 crashes when loading in RC4. The save belongs to a high-level player (Operator Level 753) and would crash in RC2 but worked fine in RC3. The issue has been fixed, though FastBeltPathLane sanity checks still fail when loading the savegame in Editor or Debug Build mode.

#

5. [SPZ2-2405] — 👀 55% similar

Fatal Error when Loading a savegame on the same build
Done • Priority: High • Fix: 4 - Early Access • Resolution: Done

Fatal Error occurs when loading a Savegame on the same build version. The issue manifests in two ways: first, the menu background Savegame fails to load because its version (1032) is below the minimum supported (1051); second, backup Savegames fail with a "Bad division: Cannot safely divide 400 by 150" error in BeltLanePresets. This error prevents the Game from initializing entirely. The issue occurred twice on Savegames without using cheats and has been marked as fixed.

#

6. [SPZ2-3649] — 👀 53% similar

Savegames Failed to Read
Done • Priority: Highest • Fix: Version 0.0.9 • Resolution: Done

The game was unable to read any Savegame / Save / Save File / Save Game files in shapez 2 / Shapez 2 / shapez2 / the game. This issue prevented players from loading any of their saved progress or data. The bug was initially not reproducible by the development team, but after the affected player provided a rough reproduction scenario, the issue was identified and fixed. The bug has been verified as resolved.

#

1. [SPZ2-2732] — 👀 55% similar

Laptop Crashed on zoom out during tutorial
Done • Priority: Medium • Fix: 4 - Early Access • Resolution: Won't Fix

The game crashes with a Unity error when zooming out to Space View during Certification on a low-end laptop. The crash occurs inconsistently after placing the first two Milestone shapes. Log analysis reveals a memory access violation error in UnityPlayer, along with Menu Savegame version mismatches and Blueprint deserialization failures. The issue is caused by the laptop running out of VRAM during the transition to Space View. This DirectX-related problem affects low-end devices and may impro...

#

2. [SPZ2-2702] — 👀 50% similar

Crash when changing resolution
Done • Priority: Medium • Fix: 4 - Early Access • Resolution: Won't Fix

The game crashes when changing the resolution setting in the Graphics menu. The player navigates to Settings then Graphics, selects a different resolution, and the crash occurs. The Player.log shows a D3D12 profiler error related to GPU timing and memory address resolution failures. There are also errors about the menu Savegame being below the minimum supported version. This is identified as a DirectX 12 issue that cannot be fixed by the developers.

#

3. [SPZ2-2585] — 👀 45% similar

lowend Laptop does not launch on DX12 (crash)
Done • Priority: High • Fix: 4 - Early Access • Resolution: Done

shapez 2 fails to launch on low-end laptops when using Direct X 12, immediately crashing with a driver internal error (DXGIERRORDRIVERINTERNALERROR) during or after the first frame. The crash appears to be a panic in the DX12 driver within Unity and cannot be fixed without a Unity engine update. Direct X 11 and Vulkan work as alternatives, though DX11 occasionally crashes when returning to the main menu or in Space View. Players can use launch options to force Vulkan or DX11 as a workaround.

#

4. [SPZ2-3053] — 👀 42% similar

Fatal Error: Savegame does not load (from Friday)
Done • Priority: Highest • Fix: 4 - Early Access • Game: 0.0.0-alpha23.1 • Resolution: Done

Savegame files from Friday with 100% completion fail to load with fatal errors. The issue occurs when trying to load these saves, with errors indicating the menu Savegame is below the minimum supported version (1032 vs 1082) and null reference exceptions in FluidPortSystem. Savegame files at 5% completion with 100 Structures load without issues. The problem may be related to Mods, though all old Mods and Savegame files were removed from the drive. The issue has been verified as fixed after a ...

#

5. [SPZ2-4759] — 👀 40% similar

Crash reported by user after new update
Done • Priority: Medium • Fix: None • Resolution: Cannot Reproduce

A player experiences repeated game crashes after updating to version 0.1.0. The crashes occur within minutes of starting a new Normal difficulty save, typically after completing one or two milestones. Log analysis reveals a SerializationJsonException when reading a blueprint file and NullReferenceException errors during deserialization. The issue appears to be caused by incompatibility between save files from version 0.0.8 and 0.1.0. The problem was resolved when the player deleted the old sa...

#

6. [SPZ2-2405] — 👀 38% similar

Fatal Error when Loading a savegame on the same build
Done • Priority: High • Fix: 4 - Early Access • Resolution: Done

Fatal Error occurs when loading a Savegame on the same build version. The issue manifests in two ways: first, the menu background Savegame fails to load because its version (1032) is below the minimum supported (1051); second, backup Savegames fail with a "Bad division: Cannot safely divide 400 by 150" error in BeltLanePresets. This error prevents the Game from initializing entirely. The issue occurred twice on Savegames without using cheats and has been marked as fixed.

knotty mulch Mar 13, 2026, 12:03 AM

#

crystal notch 53GB RAM used.

53GB you mean?

crystal notch Mar 13, 2026, 12:03 AM

#

Yeah. Typo.

knotty mulch Mar 13, 2026, 12:04 AM

#

Woohoo! Watch that go UP!

#

crystal notch Mar 13, 2026, 12:04 AM

#

🎈

knotty mulch Mar 13, 2026, 12:04 AM

#

Sky is not the limit in this case

crystal notch Mar 13, 2026, 12:05 AM

#

Don't have 128GB of RAM? 😜

knotty mulch Mar 13, 2026, 12:06 AM

#

I was encouraged to go to 64GB when I was planning this PC build with the store, but I said 32GB was enough

#

Which in most cases is correct

#

Even though my ram maximized it didn't complain about ram issues in the log file.

#

Maybe I quit too soon?

crystal notch Mar 13, 2026, 12:08 AM

#

It will just use virtual memory so it will just be a little slower.

knotty mulch Mar 13, 2026, 12:10 AM

#

crystal notch It will just use virtual memory so it will just be a little slower.

Do have a smaller save to indicate what is going on here?
Or a blueprint? The game is non responsive.

#

Or is it a bunch of wires not connected to anything?

#

Wait...its now responding

#

1,775,616 wires that aren't connected to anything? How did you figure this problem out? 😉

#

Holding at Maximum RAM1

crystal notch Mar 13, 2026, 12:14 AM

#

It's a test save that just crashed on me. This save is actually the less complex save. The multiplier one is where they're all connected. So I wanted to test to see what a similar amount of less connected ones will do.

knotty mulch Mar 13, 2026, 12:14 AM

#

Deleting some of them recovered ram but then it reclimbed up.

#

2 hours so far loading on the other one....

knotty mulch Mar 13, 2026, 12:16 AM

#

crystal notch It's a test save that just crashed on me. This save is actually the less comp...

It was a good test

crystal notch Mar 13, 2026, 12:17 AM

#

I think I crated a new save, put those wires in there, saved and went back to main menu and then loaded it again. Maybe it didn't like that?

#

The editing on this one wasn't too slow (compared to the mult save).

knotty mulch Mar 13, 2026, 12:18 AM

#

For this bug report? The memory started climbing probably from the moment the save was loaded.

crystal notch Mar 13, 2026, 12:18 AM

#

Ah. I only noticed after it crashed.

knotty mulch Mar 13, 2026, 12:19 AM

#

It just recovered quite a lot of ram, and is now slowly on the climb

#

Thats with less plaforms

knotty mulch Mar 13, 2026, 12:24 AM

#

crystal notch Ah. I only noticed after it crashed.

I recommend doing a ram check using something like memtest86. Even though my ram went to maximum, I got no allocation errors or a crash.

#

Unless this undo I just did can make it do the same thing.

#

49144.02ms player action 😉

#

887K and still happening:

#

And then flattened out.

warm hearthBOT Mar 13, 2026, 1:54 AM

#

🎫 Many thanks for reporting this issue! We have created an internal ticket for further investigation and will keep you updated. The internal ticket ID is SPZ2-5907 for reference. If you want to provide further information, just comment on this thread.

#[SPZ2-5907] [1.0.0-ALPHA5-RC2] PSOD loading save.