#[SPZ2-5984] [1.0.0-closed-beta] Changing Graphic Settings above low crashes the game
16 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 21 reports awaiting team review. Due to the high volume, it may take a little longer for us to get to yours.
πΎ 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/
Log Analysis (Player.log):
System.Exception: A background savegame failed to load inBackgroundSavegameOptionsFactory.PrepareExistingMenuSavegamebecause the menu savegame version 1129 is below the minimum supported version 1130.
Laptop experiences a game crash on certification tutorial.
QA β’ Priority: Medium β’ Fix: None β’ Game: 1.0.0-alpha5-rc2
shapez 2 crashes randomly during the Certification phase, freezing and displaying a crash error before becoming unresponsive. The crashes occur at random intervals while performing various in-game actions and progressing through the tutorial. Log analysis reveals two distinct errors: a failed savegame load due to an unsupported version below the minimum, and an InvalidOperationException ("Sequence contains no elements") thrown during an achievement update when leveling up a research upgrade. ...
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.
Error when changing Preset in Graphics
Done β’ Priority: Medium β’ Fix: 4 - Early Access β’ Resolution: Won't Fix
Error occurs when changing the Preset in Graphics settings to Minimum. After launching the game and loading any Savegame, navigating to Settings then Graphics and changing the Preset triggers multiple errors in the dev console. The errors include a failure to load the background Savegame due to version incompatibility, a NullReferenceException when applying the graphics preset related to PrefabReference instantiation, and a D3D12 profiler error about GPU timing without stable power state.
Exception when applying display settings in game
Done β’ Priority: Highest β’ Fix: 1.0 Release [1.0.0] β’ Game: 1.0.0 β’ Resolution: Done
When changing display resolution or graphics settings during gameplay or after loading a save game in shapez 2, the game throws a NullReferenceException and displays a black screen. This prevents players from applying the resolution changes. The issue does not occur on the initial main menu before starting any game, but appears once a game has been started and persists even after returning to the main menu. The problem is temporary as changes are not confirmed and the screen reverts to the pr...
Cannot apply display settings
Done β’ Priority: Medium β’ Fix: None β’ Resolution: Done
The Operator cannot apply Graphics settings changes for resolution or window mode in shapez 2. When the player launches the game, goes to Settings, and attempts to change any resolution or window mode setting, clicking apply or returning to menu fails - the Operator cannot return to menu or change the settings. The issue occurs because display settings can only be set during preload from settings.json, not during active gameplay. The expected behavior is that the Operator should be able to ch...
Changing Color modes and graphic settings causes fatal glitch
Done β’ Priority: High β’ Fix: 4 - Early Access β’ Resolution: Won't Fix
Toggling through color selections caused a slight FPS drop. Switching Graphics settings from high to minimum worked smoothly, but returning to high settings caused severe screen glitching and flickering with green artifacts. This appears to be a driver issue related to GPU running out of VRAM rather than a game bug. The issue results in a fatal glitch that makes the game unplayable until settings are adjusted or the game is restarted.
Looks like the game is having problems with the 6600XT when running vulkan.
I have a RX6600 on another system and it is having similar issues.
Can you try to run it on directx11 (default) and see if the problem persists?
it now worksπ i chose the highest setting aswell and i can run the game
β Thank you for providing further information, our team will have a look again!
Glad I could help. It's still a bug with it causing crashes with vulkan
i am also happy to help!
Its appreciated π