These checks follow Chris Cote's pinned launch-troubleshooting thread , edited September 18. They are developer advice, not a guaranteed cure or a claim that we reproduced your failure.
Try the branch that matches your device
Windows: restart, then test the executable
Restart the device, open the game's installation directory, and try
game.exedirectly. Note whether a window appears or an error becomes visible. The developer also recommends current graphics drivers.Windows: check for a leftover runtime process
The developer names
nw.jsin Task Manager. Close the game first. Only end a leftover process you can identify as this game; if its owner is unclear, use a restart instead of terminating unrelated applications.Proton: compare the named compatibility versions
The pinned post suggests Proton 9.0-4 or 10.0-4 for launch problems. Record your current selection, test one alternative, and keep the result. This is startup advice, not a measured stutter fix.
If the game opens and the remaining problem is frame pacing, continue with the in-game Steam Deck display settings. If it crashes during storage, dialogue, fog, or another action, use the dated symptom index.
Before replacing files or clearing user data
Make a separate backup of the game's save folder first. A failed launch alone does not identify a corrupt save. Keep the original installation and any backup distinguishable, and record each attempted change.
The developer's thread also discusses older Patreon saves, AppData, Citrix conflicts and replacement NW.js files. Those cases are not interchangeable. Replacing the runtime can get the game to launch but stops Steam achievements working, so try it last.
Still no window? Send a useful report
Return to the pinned thread with your operating system, GPU, installed build, any Proton version, whether direct launch behaved differently, and the exact current error. List the checks already tried. Do not upload private account details or an entire personal folder.
A debug log containing the developer's C:\Users\Chris path is not itself proof of your current failure: the developer explains that bundled development logs can contain historical paths. Use the error produced by your own launch attempt.