#[SPZ2-5864] [1.0.0-ALPHA5-RC1] Loading saves is very slow compared to 0.1.1
13 messages ยท Page 1 of 1 (latest)
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 25 reports awaiting team review. Due to the high volume, it may take a little longer for us to get to yours.
โฐ Our team is off on weekends, so it may take a bit longer for us to review your report. Thank you for your patience!
๐ 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/
Loading time is extremely slow with ~450k buildings
Done โข Priority: Highest โข Fix: 4 - Early Access โข Game: 0.0.0-alpha22.4 โข Resolution: Done
Loading time for savefiles with approximately 450,000 structures is extremely slow, taking around 4-5 minutes to complete. The performance issue was suspected to be caused by quadratic scaling in the loading algorithm. This significantly impacts players with large factories, making the game difficult to access. The issue has been verified and fixed, with loading time improved by roughly 40% through linear scaling optimization.
Big savefiles have very long loading times and cause the game to freeze if it's minimized while loading
To Do โข Priority: Medium โข Fix: 1.0 Release [1.0.0] โข Game: 0.1.1
Large savegames with over 500,000 structures experience very long loading times in shapez 2. When the game is minimized during loading in borderless mode, it appears to freeze and may show a "stopped working" error message, though it will eventually load if given enough time. The loading widget stops spinning during longer loads, making players think the game has crashed. Testing showed that loading times have increased in newer builds, with borderless mode taking significantly longer when fo...
๐ฌ Threads: [0.1.1][Windows] Freezes when quitting
Savegame serialization is extremely slow
Done โข Priority: Critical โข Fix: 1.0 Bugfixes before Feature Freeze โข Resolution: Done
Savegame serialization is extremely slow when there are more than 100,000 structures placed in the game. The serialization process takes over 1 second to complete with this many buildings. The issue was tested across multiple game versions including 0.0.9, 0.1.1, and 1.0.0-alpha1, with version 0.0.9 showing the best performance. Testing was requested to gather more data on the exact serialization times with large numbers of buildings to assess the severity of the performance degradation.
Autosaves impacts gameplay when they happen at higher structure counts
Done โข Priority: Medium โข Fix: None โข Game: 1.0.0-dev โข Resolution: Won't Fix
Autosaves cause noticeable gameplay pauses when they occur at higher structure counts. The issue is triggered every 5 minutes during autosave with high structure and space platform counts, demonstrated with a savegame containing 616K structures. Each autosave creates an obvious pause that interrupts smooth gameplay. Players expect to play smoothly even when autosaves occur. The issue was closed as won't fix, with the suggestion to increase autosave interval time.
Save and following "Quit to Desktop"/"Back to Menue" always shows "Quit without saving"
Done โข Priority: Medium โข Fix: Dimension Update [0.1.0] โข Resolution: Done
After saving a Savegame in shapez 2 with 1.34 million Structures, the user no longer has enough time to quit the game without triggering the "Quit without saving?" dialog. The save process takes between 8.5 and 9.5 seconds, but the timer that checks if the player saved recently was set to only 10 seconds instead of the intended 10 minutes. This affects large Savegames on Linux with Steam Cloud disabled. The issue was fixed by increasing the timer from 10 seconds to 120 seconds (2 minutes), th...
๐ฌ Threads: Save and following "Quit to Desktop"/"Ba
Optimize Performance of First Time ShapeOperation Execution
To Do โข Priority: Low โข Fix: 1.0 Release [1.0.0]
When loading the main menu or loading a Savegame, the first execution of ShapeOperation creates megabytes of avoidable garbage over the first minute. This is one of the primary reasons why FPS takes a long time to stabilize after loading. The performance issue affects the initial gameplay experience by causing frame rate instability until the garbage collection settles.
Over 2 hours now.
Woot! 3.11 hours!
GameSessionOrchestrator:Init_3_1_ExistingSavegame took 11198.128s.
Alpha3: 1,475,923 buildings 1,838 platforms: 3 minutes 10 seconds
๐ซ 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-5864 for reference. If you want to provide further information, just comment on this thread.
[SPZ2-5864] [1.0.0-ALPHA5-RC1] Loading saves is very slow compared to 0.1.1