Start with the lowest-risk checks
- Install the latest build. Old Demo reports may refer to the April version rather than v1.0.46.
- Restart Steam and the computer. This clears a surprising number of stuck update and graphics-state problems.
- Verify installed files. In Steam, open the game's Properties, choose Installed Files, then Verify integrity of game files.
- Update the graphics driver. Use NVIDIA, AMD, or Intel's official package rather than a third-party driver site.
- Check free storage and memory. The official game needs 1 GB of storage and 8 GB RAM.
Crash or black screen at startup
Demo v1.0.46 provides multiple launch choices, including Vulkan and a compatibility/OpenGL-style option. If the default renderer opens to a black screen or exits, close the game completely and try the alternative offered by Steam. Change one variable at a time so you know which step matters.
Windowed mode can help when a fullscreen resolution fails. If you previously chose an aggressive UI scale or resolution, return to a conservative setting once the game opens.
Linux and Steam Deck
Update SteamOS or your Linux graphics stack, then test the current Proton version if the native path is unstable. Verify files after switching compatibility tools. SteamOS/Linux support is planned for the full game, but the Demo's depot history and community results do not guarantee identical release behavior.
Some players report longer stability with Steam Overlay disabled, but that is not a universal official fix. Treat it as a controlled test after file verification, driver updates, and renderer selection—not the first step.
Freezes or loading problems
Wait briefly before force-closing during a one-off shader or loading pause, but do not leave an unresponsive process indefinitely. Note memory use, renderer, and the last in-game action. Repeated freezes with the same steps are worth reporting through the official Steam discussions or support email.
Never download replacement executables, DLL bundles, unofficial “fix packs,” or other users' save files as a troubleshooting shortcut. They can introduce malware, corrupt progress, or make the original fault harder to diagnose.