Most Slay the Spire 2 crashes on PC are not a hardware problem. They are the game picking a renderer your system does not handle well, and there is a launch flag that overrides it.
Try this before anything else.
The fix that works most often
- Open Steam and go to your Library.
- Right-click Slay the Spire 2 and choose Properties.
- Find Launch Options.
- Paste this exactly:
--rendering-driver opengl3- Close the window and launch the game.
If the game still closes on startup, replace it with --rendering-driver vulkan. Use one or the other. Both at once can produce a worse failure than the original crash.
What the error message is really saying
The common crash shows a line like this:
Your video card drivers seem not to support the required Direct3D 12 versionThat reads like a dead GPU. It usually is not. The message means the game failed to initialise its default rendering path — Vulkan on many builds — and reported it through the Direct3D check.
Players on integrated graphics, older laptops and certain AMD cards hit it most. Forcing OpenGL sidesteps the path that fails.
Fix order that saves time
Change one thing, launch, then decide. Applying four fixes at once tells you nothing about which one worked.
| Step | Action | Fixes |
|---|---|---|
| 1 | Launch option --rendering-driver opengl3 | Instant close, black screen |
| 2 | Verify integrity of game files | Corrupted shader or cache |
| 3 | Update GPU driver, or clean install it | Driver conflict |
| 4 | Disable Steam Overlay | Overlay-triggered crash |
| 5 | Add -windowed to the launch options | Resolution and fullscreen conflicts |
| 6 | Delete shader cache in the game’s core folder, then verify | Stale shader compile |
| 7 | Install Visual C++ Redistributable, both x86 and x64 | Silent runtime crash |
| 8 | Reinstall the game cleanly | Everything above failed |
Step 7 matters more than it looks. A missing or corrupted Visual C++ runtime closes the game with no error at all, which is why some crashes have no message to search for.
Match the symptom, not the fix list
Different crashes have different causes, and treating them as one problem wastes hours.
| What you see | Likely cause | Start with |
|---|---|---|
| Closes within seconds, no window | Renderer initialisation | Launch option |
| Black screen but you hear audio | Rendering output, not a crash | -windowed, then driver |
| Loads, then freezes mid-run | Shader compilation or driver | Verify files, delete shader cache |
| Only co-op fails | Network or firewall | Firewall rules, wired connection |
| Crashing on a multi-monitor setup | Window and display handling | --single-window |
The black-screen-with-audio case is the one people misdiagnose. If you can hear the music, the game is running and only the picture is missing. That is a display problem, not a crash.
Do not do these
Do not stack launch options. One renderer flag at a time, and remove the previous one before testing the next.
Do not reinstall first. It is the slowest option and rarely the actual fix.
Do not update drivers blindly. If the crash started right after a driver update, rolling back one version is more likely to help than pushing forward.
Do not delete random files in the game folder. Only the shader cache is documented as safe to clear, and verification restores it.
When a patch is the real answer
Slay the Spire 2 is still receiving fixes, and some crashes are build-specific rather than machine-specific. If every step above fails, check the patch notes for a hotfix before you take your PC apart.
If the game runs but the frame rate is poor, that is a settings problem rather than a crash. The beginner guide covers the early settings that matter, and common mistakes covers the run-level errors that cost more than any crash.