Azure
Published
- When playing a modded install of Beat Saber (version 1.39.1), some custom sabers wouldn't render at all or have missing trails
- Some special characters might display as "?"
Would sometimes freeze and/or crash on exit
Tested with ALVR and a Quest 2. SteamVR launch options set to ~/.local/share/Steam/steamapps/common/SteamVR/bin/vrmonitor.sh %command%. Using GNOME 48.1 under Wayland.
Some UI icons show up as ?
Modded 1.39.1 install crashes/hangs on exit.
SteamVR 2.10.4 causes the game to crash on launch. Reverting to SteamVR 2.9.6 via the previous branch or playing on an older version of Beat Saber by using BSManager or going into Properties > Betas > Beta Participation and selecting legacy1.29.1 fixes the issue.
The custom sabers issue on my previous report can be fixed by enabling multi-pass rendering mode under Settings > Mod Settings > Asset Bundles. Tested with ALVR v20.13.0 and a Quest 2. SteamVR 2.9.6 with launch options set to ~/.local/share/Steam/steamapps/common/SteamVR/bin/vrmonitor.sh %command%. GNOME 48.1 under Wayland.
Some UI icons (e.g. likes/dislikes on BetterSongSearch) appear as ?
Tested using ALVR 20.13.0 and SteamVR 2.12.1 with GNOME 48.1 under Wayland. SteamVR launch options set to ~/.local/share/Steam/steamapps/common/SteamVR/bin/vrmonitor.sh %command%. Mostly played modded Beat Saber 1.39.1 but the latest version without mods works just fine as well. Game no longer freezes/crashes on exit.
LD_PRELOAD="" gamemoderun gamescope -f -W 1920 -H 1080 -w 1440 -h 1080 -r 60.0 -S stretch --force-grab-cursor --adaptive-sync --immediate-flips -- %command% -sdlaudiodriver pipewire -high -novid
Loses audio when some games are also running at the same time (e.g. Balatro).
Trying to play on a stretched resolution without gamescope caused a lot of windowing issues and input inaccuracy. Native resolution works fine.
Using gamescope to make the game run in a stretched resolution causes a bit of input latency. Playable, but not ideal.
FPS randomly go from ~170 to 50 for around a minute seemingly without explanation. Some maps (e.g. Grail) won't even go over 40 FPS. Happens with and without gamescope.
Tested on GNOME 48.1 under Wayland.
Blurry/out of focus cutscenes, can be fixed by lowering the Post FX setting under Graphics
No anti-cheat support, you'll get kicked by BattlEye within seconds
It's fine as long as you don't want to play online.
Native Linux build does not support Windows saves so you'll need to start from scratch or use Proton
SteamVR crashed during the initial Eli's call when using the native Linux build
Native Linux build did not work very well compared to the Windows build under Proton
SteamDeck=1 gamemoderun %command% -PSOCompileMode=1
Tested under Hyprland 0.49.0-1, didn't try to play without tweaks
Switching to another virtual desktop on GNOME would ocassionally cause the game to exit fullscreen. Toggling fullscreen off and on again under Graphics Options fixes it.
Had to force Proton in order to launch the game.
I had a weird issue where the game wouldn't launch in VR mode. It never happened again after I removed the VRChat folder (438100) under compatdata and restarted Steam. No idea what caused it.
- Tested both on desktop and VR mode. VR mode tested with a Quest 2 + ALVR, SteamVR launch options set to
~/.local/share/Steam/steamapps/common/SteamVR/bin/vrmonitor.sh %command%. Using GNOME 48.1 under Wayland. - Video playback seems to work fine.
- I also symlinked this folder to more easily access the pictures I take in-game:
ln -s ~/.local/share/Steam/steamapps/compatdata/438100/pfx/drive_c/users/steamuser/Pictures/VRChat ~/Pictures/VRChat
