Resonite

Resonite #

While the game engine runs natively on Linux, the renderer runs through Proton. The current recommended Proton variant is Proton-GE. It can be installed through ProtonUp. It also solves the issue with rendering Resonite’s logo on startup.

xrizer should now provide a close-to-flawless VR experience on most controllers and when using hand tracking, but may cause issues when using controllers while hand tracking is enabled.

A November 2025 update replaced SDL with ResoFlow, a customized version of the SoundFlow audio engine, and no more Linux-specific audio issues are expected.

Common issues #

  1. Forgetting to enable Proton or using a bugged Proton version:

    Open Steam Library -> Right-click Resonite -> Properties -> Compatibility -> Check Force (…) and choose a (different) Proton variant.

    Note: you need to to restart Steam after installing an unofficial Proton variant.

  2. Using standalone SteamVR:

    SteamVR is known to be unstable. If you have a standalone headset, use WiVRn and uninstall SteamVR. In all other cases, use Monado or its wrapper/GUI Envision.

  3. Using OpenComposite:

    Please double-check if WiVRn/Envision is set to use xrizer, not OpenComposite. Crash explained below.

  4. Using Flatpak or standalone WiVRn without the required launch arguments:

    Make sure you’ve also rebooted your system after installing WiVRn, to see those options.

  5. Incorrect launch options format.

  6. Unstable overclocks.

    Resonite (or .NET) is particularly sensitive to unstable RAM overclocks, which may crash it at random intervals. Use memtest86 to test your RAM, and consider testing your CPU and GPU as well.

Mirrors look cross-eyed #

When playing Resonite under Monado or WiVRn, the 3D effect of mirrors may appear way off, as if looking through them feels like your eyes are crossed. This only affects headsets with canted displays (e.g. Valve Index, Pimax).

To solve this, prepend OXR_PARALLEL_VIEWS=1 to Resonite’s launch options.

Performance #

In August 2025, Resonite updated to run FrooxEngine as a native Linux process, with the renderer being run through Proton.

Resonite is typically GPU-bottlenecked. Lowering the resolution may help. This can be easily done by prepending OXR_VIEWPORT_SCALE_PERCENTAGE=75 to Resonite’s launch options. Experiment with different values to find your preferred balance between performance and quality.

FlipVR controller support with Monado #

Currently there is an experimental Monado branch that works with Shiftall FlipVR controllers. Instructions can be found here. At the time of writing, this branch is the only way to use FlipVR controllers with Resonite, as they are not supported even through SteamVR on Windows.

Mods #

Resonite has a thriving modding community with an abundance of mods that offer greater user experience, optimizations and new features.

Currently there are 3 mod loaders:

A more detailed comparison table between modloaders is available here.

Stuck on the loading screen #

Consider using a different mod loader and reporting the problem.

Clipboard #

As of the Splittening release, Resonite only supports copying/pasting text, and does not work at all in Flatpak Steam with Wayland, issue #5321.

The mod ResoniteLinuxClipboard provides full clipboard functionality, however:

  • It only works on Wayland.
  • If you’re using MonkeyLoader or BepisLoader, the .so file needs a different path: place it directly in the rml_mods folder with the .dll.

Crashes #

CachyOS’s native Proton has been known to be unstable in Resonite, causing frequent, but not instant crashes, while CachyOS’s SLR Proton (the one available on ProtonUp) is comparable to GE.

Renderer issues #

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.

There’s an unreported bug with avatar meshes (skinned mesh renderers) glitching out in VR mode on AMD GPUs.

Crash on launching only in VR mode #

Currently, OpenComposite is known to crash Resonite when used in VR, so attempting to use OpenComposite for Resonite is not recommended.

Symptoms:

  • Crashes only in VR mode, where after several seconds a black window appears and closes briefly, 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.

To prevent this issue, use xrizer instead of OpenComposite.

See Issue #5152 for more information.

Crash on launching in desktop & VR mode #

Proton data can get corrupted, which will result in consistent crashes on launch.

The symptoms are:

  • Crashes 2 seconds from launch in desktop mode (and in VR)
  • 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.

Navigate to compatdata in the folder 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 Steam launch options.

Hanging on launch, but not loading #

Symptoms:

  • Steam is showing Resonite is running while it isn’t starting.
  • Resonite starts launching and stops immediately.

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

  • 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 or report and wait for a hotfix

Controls #

Inputs stuck after switching to desktop #

Resonite allows a VR player to take a break and switch to desktop mode by pressing the F8 key.

Because controller hot-swapping is not yet implemented in Monado & OpenComposite, turning off a controller will freeze its state, including buttons pressed and analog stick input. Resonite will continue processing VR inputs even after switching to desktop.

The end result is that desktop controls can act strangely. For example, if you were holding the grab sensor as you turned off the VR controller, picking up items or inspector windows stops working with the mouse.

Controller buttons or hand tracking not working #

There’s an issue that prevents Resonite from switching between hand tracking and controllers.

It happens when you have hand tracking enabled in the headset (even if it’s disabled in WiVRn, for example) and launch Resonite while the controllers are in stand-by mode.

To prevent this, disable hand tracking completely. Alternatively, always hold controllers while starting Resonite, but this isn’t guaranteed to fix hand tracking, and will cause you trouble every time you forget to hold your controllers when starting Resonite (if you’re experiencing this issue).

Video players #

A November 2025 update fixed yt-dlp not updating for Linux users, which eliminated most issues.

Videos keep glitching #

The Unity Native playback engine can have this issue on some systems.

Play the video in a different player that’s already set to use libVLC.

To fix your existing player:

  1. Open an Inspector on the video player you’re using in Resonite.
  2. Find the VideoTextureProvider component (normally under a slot with Video in its name, in the first or second hierarchy level under its root).
  3. If it’s using Unity Native, press Use libVLC Playback Engine.

YouTube videos don’t load #

  1. Download an older nightly yt-dlp_linux.

    In the worst-case scenario, download the latest stable.

    Alternatively, restart Resonite to let it auto-update.

  2. Move it to ~/.local/share/Steam/steamapps/common/Resonite/RuntimeData/ and overwrite the yt-dlp_linux file that was already there.

    To check the version, run yt-dlp --version in the same path.

  3. Mark it as executable with chmod +x ~/.local/share/Steam/steamapps/common/Resonite/RuntimeData/yt-dlp.

    This fixes a Permission denied error you’d otherwise see in the Resonite log.

If that didn’t solve it, try switching cookie settings in Resonite’s dashboard menu:
Settings>Network>Video Streaming Services>Use Cookies From Browser (start with NONE).

Note: yt-dlp auto-updates once per Resonite startup, so if you change it and restart, you’ll lose your changes.

Steam launch options #

  • If you’re using environment variables and/or wrapper scripts, use one, and only one %command%.
  • Make sure the arguments match the following order. Breaking this order can prevent Resonite from starting:
    SOME_ENV_VARS=1 some-wrappers %command% -SomeCommandLineOptions