From b844360efa2eea47b865342d50eabd96a684e4f4 Mon Sep 17 00:00:00 2001 From: Krzeszny Date: Tue, 21 Oct 2025 13:28:19 +0000 Subject: [PATCH] Shooting the troubles away --- content/docs/resonite/_index.md | 40 ++++++++++++++++++++++++++++++++- 1 file changed, 39 insertions(+), 1 deletion(-) diff --git a/content/docs/resonite/_index.md b/content/docs/resonite/_index.md index cbcf7ac..1d10a69 100644 --- a/content/docs/resonite/_index.md +++ b/content/docs/resonite/_index.md @@ -41,7 +41,27 @@ The game will default to the PipeWire API if it can, falling back to the PulseAu ### Glitchy audio -The most straightforward way to fix a glitchy microphone is to use SDL's ALSA driver with `SDL_AUDIO_DRIVER=alsa %command%` as the launch argument on Steam. +The most straightforward way to fix a glitchy microphone is to force the use of **SDL's ALSA driver** for Resonite's audio: +1. Set the launch argument: +Add the following to Resonite's Launch Options: +````SDL_AUDIO_DRIVER=alsa %command%```` +**Note:** If you already have `%command%` in your launch arguments, simply add `SDL_AUDIO_DRIVER=alsa` **before** it. +2. Configure PipeWire for ALSA: +For most users, switching to ALSA **will break all audio** in Resonite unless you configure your audio server, PipeWire, to support your hardware's sample rates. +If this happens: + 1. Locate the directory or create it if it doesn't exist: + ```$HOME/.config/pipewire/pipewire.conf.d/``` + (Remember: The ~/.config folder is often hidden in file browsers) + 2. Create the file `01-sample-rates.conf` in that folder. The full path should be + ```$HOME/.config/pipewire/pipewire.conf.d/01-sample-rates.conf``` + 3. Paste the following content into the file to define supported sample rates, and save it: + ``` + context.properties = { + default.clock.allowed-rates = [ 44100 48000 88200 96000 ] + default.clock.rate = 48000 + } + + ``` If that doesn't work, you can try forcing the other drivers by specifying `pipewire` or `pulseaudio` instead of `alsa` in the above launch arguments. @@ -60,6 +80,10 @@ Do note that for the Audio Stream feature of Resonite, you'll need to select a d The PipeWire driver is not supported by Steam Flatpak OOtB, see [this issue](https://github.com/Yellow-Dog-Man/Resonite-Issues/issues/5261#issuecomment-3228033460) if you need to use the PipeWire driver on Resonite in Steam Flatpak. +### There is mic audio after a crash + +If you're using WiVRn, close and reopen it (this will crash Resonite). + ## FlipVR controller support with Monado Currently there is an experimental Monado branch that works with Shiftall FlipVR controllers. Instructions can be found [here](/docs/fossvr/monado/flipvr/). 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. @@ -115,6 +139,20 @@ It may be enough to just verify file integrity in some cases. On GE-Proton9-10 (for example), loading into a world with e.g. a YouTube video or live stream can crash the game. Try using the latest GE-Proton-RTSP release. +### Crash after loading + +Although this is rare, some proton updates can start crashing Resonite repetitively. + +Symptoms: +- Crashes approximately 1 minute after successfully loading Resonite +- Everything freezes in both desktop mode and VR, but you can still hear sounds, including the voices of other users + +If this happens, just switch Proton to another version in the compatibility options. + +### No launch and no crash + +Choose the correct default audio devices in your volume panel. This is likely caused by SDL. + ## Controls busted after switching to desktop Resonite allows a VR player to take a break and switch to desktop mode by pressing the F8 key.