Crashing & Not Loading #
Resonite’s renderer is known to randomly crash suddenly - this is currently tracked at Issue #5325.
There is also a known memory leak when running the renderer on Linux - however, it is uncertain currently whether this is an issue with Proton or there is something else at play - see Issue #5246.
During VR gameplay, the renderer may cause a full GPU Reset if you have an AMD graphics card that is heavily loaded. Check dmesg if this occurs.
CachyOS’s native Proton has been unstable in Resonite (as of December 2025), causing frequent, but not instant crashes, while CachyOS’s SLR Proton (the one available on ProtonUp-Qt) is comparable to GE.
Occasional crashing can happen for many reasons, including mods, but Resonite (or .NET) is particularly sensitive to unstable RAM overclocks, which may crash it at random intervals where other apps wouldn’t crash. Use memtest86 to test your RAM, and consider testing your CPU and GPU as well.
Crash on launching only in VR #
Resonite crashes when OpenComposite is used in VR.
Symptoms:
- A black window appears and closes briefly after launching in VR mode, then Resonite stops within approximately 30 seconds.
- The normal log file shows a renderer crash:
RendererProcess has exited. Shutting down. There’s a Player.log file.
Solution:
Use xrizer, as OpenComposite is unsupported and considered legacy.
See Issue #5152 for more information.
Crashing on launch in desktop mode & VR #
Proton data can get corrupted, which will result in consistent crashes on launch.
Symptoms:
- Resonite stops 2 seconds from launch.
- No log files (no main log, no Player.log, no crash log, no proton log with PROTON_LOG=1, only the bootstrapper log).
- Error windows show up if you’re using certain mod loaders.
Solution:
Navigate to compatdata in the directory above Resonite’s folder (by default .local/share/Steam/steamapps/compatdata/) and delete the 2519830 folder; it will regenerate on the next launch. Then verify the integrity of Resonite files in Steam (right-click Resonite and go to Properties>Installed Files>Verify).
It may be enough to just verify file integrity in some cases.
This can also happen because of incorrect launch arguments.
Not launching at all #
First, check the issue above (crashing on launch).
Symptoms:
- Steam shows Resonite is running while it isn’t starting.
- Resonite starts launching and stops immediately.
- There aren’t any log files.
Possible causes:
-
Not having a default audio device selected.
- Select an audio device in your volume panel.
-
Improperly configured mod loaders and plugins.
- Try starting without Steam launch options and then re-add them one by one. This is commonly caused by misconfigured MonkeyLoader.
-
Stuck background process, most likely
dotnet.- From easier to more extreme solutions:
- Press STOP in the Steam library and try again.
- Close/terminate the process that caused it, such as Steam
- Relog your user
- Reboot your system
- From easier to more extreme solutions:
-
Borked launch arguments
Crash after loading #
On some systems, X11, Proton or wine updates can cause race conditions, crashing Resonite shortly after launch.
Symptoms:
- Freezes immediately upon loading Local Home or any other world on each startup.
- Crashes approximately 1 to 2 minutes after successfully loading.
- Everything freezes in both desktop mode and VR, but you can still hear sounds, including the voices of other users.
- Regular logs cut off (this symptom is not specific to this issue).
Solutions:
- Switch Proton to another variant, such as Proton-GE or Proton-CachyOS.
- Switch from X11 (if you’re using it) to Wayland. Follow your distro’s instructions.
- Revert package updates (using snapshots is highly recommended) or wait for a hotfix.
Stuck on the loading screen #
Possible causes:
- A mod loader is incompatible with a new Resonite update.
- A driver crashed and didn’t recover.
Make sure your mod loaders are updated and properly installed. If that didn’t help, restart your system.
Crash while playing #
Refer to the first section.