Troubleshooting
WebGPU Not Available
Section titled “WebGPU Not Available”Symptom: Renderer fails to initialize or shows a blank canvas.
Solutions:
- Ensure you’re running on a GPU with WebGPU support
- Update your GPU drivers to the latest version
- On Linux, ensure proper Vulkan drivers are installed:
Terminal window # Debian/Ubuntusudo apt install mesa-vulkan-drivers vulkan-tools# Fedorasudo dnf install mesa-vulkan-drivers vulkan-tools# Archsudo pacman -S vulkan-driver vulkan-tools - Verify Vulkan is working:
Terminal window vulkaninfo
Sim Worker Crash
Section titled “Sim Worker Crash”Symptom: Error banner appears, simulation freezes.
Solutions:
The sim worker supervisor automatically restarts once from a checkpoint. If a second crash occurs in a short window, the render loop halts with a fatal error.
- Check the console output for the crash reason
- Try running in debug mode for more verbose logging:
Terminal window cd <game-directory> && draft dev --verbose - If the crash is reproducible, use MCP
checkpointtools to save state before the crash point
Native Audio Module Not Loading
Section titled “Native Audio Module Not Loading”Symptom: Audio doesn’t play, console shows FFI errors.
Solutions:
- The Kira backend (
KiraAudioBackend/AudioKiraLibinlibraries/audio-kira) loads thelibdowndraft_audiocdylib over FFI; setAUDIO_NATIVE_PATHto point at a specific build. - Build the cdylib with
cargo build -p downdraft-audio(crate underpackages/engine/libraries/audio-kira/native).
Build Fails
Section titled “Build Fails”Symptom: draft release --stage=build (formerly draft build) fails.
Solutions:
- Ensure all dependencies are installed:
Terminal window bun install - Clear the build cache:
Terminal window rm -rf dist out - Try building with verbose logging:
Terminal window draft release --stage=build --mode=prod --out=dist --verbose
High CPU Usage in Dev Mode
Section titled “High CPU Usage in Dev Mode”Symptom: CPU usage is high even when the game is idle.
Solutions:
This is expected in dev mode due to telemetry, hot reload, and DevTools overhead. Use prod mode for performance testing:
draft release --stage=build --mode=prod --out=distFrame Rate Issues on Multi-Monitor Linux (X11)
Section titled “Frame Rate Issues on Multi-Monitor Linux (X11)”Symptom: Game runs too fast on multi-monitor X11 setups.
Solutions:
This is a known X11 issue where the render loop is driven at the fastest monitor’s refresh rate. Use the frame rate limiter:
renderer.setFrameRateLimit(60); // or your monitor's refresh rateBlank Screen / White Screen
Section titled “Blank Screen / White Screen”Symptom: The native window opens but shows a blank or black screen.
Solutions:
- Check the terminal output and the devtools overlay console for errors
- Ensure WebGPU is available (see above)
- Try running in dev mode to see detailed error messages
- Check that the correct game is being loaded — run
draft devfrom inside the game directory (the game is inferred from the current directory)