OVRAS does not launch with Steam Linux runtime, now default in beta client

[peterfab9845]

Describe the bug
The Steam Beta Client update from 2024-10-17 changes the default runtime for native Linux games to 'Steam for Linux runtime 1.0 (scout)'. OVRAS does not launch with this runtime.

To Reproduce
Steps to reproduce the behavior:

1. Update to the latest Steam beta client (version 1729208001 as of this report).
2. Open Steam from the command line to see logs.
3. Launch OVRAS.
4. OVRAS fails to launch.

Expected behavior
OVRAS launches properly.

Screenshots
Steam log:

chdir "/mnt/scratch/peter/Steam/steamapps/common/OVR_AdvancedSettings"
Game Recording - would start recording game 1009850, but recording for this game is disabled
Adding process 42591 for gameID 1009850
dlopen(): error loading libfuse.so.2

AppImages require FUSE to run. 
You might still be able to extract the contents of this AppImage 
if you run it with the --appimage-extract option. 
See https://github.com/AppImage/AppImageKit/wiki/FUSE 
for more information
Uploaded AppInterfaceStats to Steam
Game Recording - game stopped [gameid=1009850]
Removing process 42591 for gameID 1009850

Software (please complete the following information):

• OS: Linux 6.11.3-arch1-1
• Advanced Settings Version: Not sure where to find this. Latest as of 2024-10-20

Hardware (please complete the following information):

• CPU: AMD Ryzen 7 7800X3D
• Graphics Card: Gigabyte RTX 3060 Ti
• HMD: Valve Index

Additional context

Steam Beta Branch:  Steam Beta Update
Steam Version:  1729208001
Steam Client Build Date:  Thu, Oct 17 19:14 UTC -08:00
Steam Web Build Date:  Thu, Oct 17 18:39 UTC -08:00
Steam API Version:  SteamClient021

SteamVR beta 2.8.5 (1727976561)

Steam beta client changelog with default runtime change:
https://store.steampowered.com/news/group/4397053?emclan=103582791433918461&emgid=4507632124224426488

WORKAROUND
Set OVRAS to use this custom "none" compatibility tool: https://github.com/Scrumplex/Steam-Play-None

[ykeara]

looking into this, I'm probably going to need to sit down and re-create it TBH, unfortunately from the back-end there doesn't seem to be an easy way to say hey don't move to the new stuff