Dusk Apple Silicon Shader-Cache Crash — Fix Guide (#826)
Dusk v1.0.1 still crashes on some M-series Macs with a Metal/WebGPU 'RmlUi Gradient Pipeline' shader-compile failure. Backend-cycling workaround + status of issue #826.
Status as of 2026-05-13: Open on the Dusklight tracker. Labeled by the team as “Known shader cache crash on macOS currently.”
This is the second Apple Silicon crash to surface around launch. The first (#779 / #805) was closed in v1.0.1. If your Mac quit Dusklight on launch and you’re still on v1.0.0, the first thing to do is update.
Symptom
On launch, Dusklight quits unexpectedly. Crash log includes a reference to RmlUi Gradient Pipeline and a Metal or WebGPU shader-compile failure. Affects some — not all — M-series Macs.
Cause (per project labels)
Shader-cache compile path for the UI library RmlUi fails during pipeline construction on certain Metal/WebGPU driver builds. Treated by the team as a distinct bug from the v1.0.0 launch crash.
Workarounds
- Update to v1.0.1. If you were on v1.0.0, this alone may fix you — you might have been hitting #779/#805, which is closed.
- Cycle the graphics backend: open
Settings → Prelaunch → Graphics Backend, restart Dusklight after each change. Try in order:- Metal
- Vulkan (uses MoltenVK on macOS)
- OpenGL
- Clear the shader cache if Dusk got far enough to write one: delete the contents of
~/Library/Application Support/TwilitRealm/Dusk/and relaunch (you’ll lose settings but not saves if you back upUSA/Card A/orEUR/Card A/first).
If none of these work, file a comment on #826 with your Mac model, macOS version, and crash log.
Related
- #779 / #805 — original Apple Silicon launch crash (closed in v1.0.1)
- macOS install guide
- Graphics backends explained
- All known issues
Last updated 2026-05-14. Watch issue #826 for fix progress.