[BUG] Input / Action Bindings: vrserver sniper runtime does not mount all steam storage paths

[Spacefish]

When running a VR Game with OpenVR, which is installed in a Steam Library Path not in your home directory / steam default install location. I get the below errors in vrserver.txt

Fri Mar 21 2025 00:47:19.579153 [Error] - [Input] Error loading action manifest.
	App key: steam.app.667970
	Error: #ActionManifestError_FileNotFound
	Param: 
	Path: /data2/SteamLibrary/steamapps/common/VTOL VR/VTOLVR_Data/StreamingAssets/SteamVR/actions.json

Fri Mar 21 2025 00:54:45.315581 [Info] - AppInfoManager.ProcessConnected END
Fri Mar 21 2025 00:54:45.315593 [Info] - We don't yet have an input context. This should be okay, but noted.
Fri Mar 21 2025 00:54:45.316202 [Error] - [Input] Error loading action manifest.
	App key: steam.app.438100
	Error: #ActionManifestError_FileNotFound
	Param: 
	Path: /data/SteamLibrary/steamapps/common/VRChat/VRChat_Data/StreamingAssets/SteamVR/actions.json
Fri Mar 21 2025 00:54:45.316216 [Error] - [Input] LoadActionManifest failed. Could not find action manifest for app '431789: wine64-preloader' with key 'steam.app.438100'

if i look at the vrserver process, it seems to chroot in a sniper steam runtime steamrt sniper 3.0.20250306.120299
in the chroot i see in /proc/424791/root (424791 = vrserver) my home directory exists, however the /data and /data2 is not bind-mounted into that sniper runtime!

That´s why vrserver can´t load files like /data/SteamLibrary/steamapps/common/VRChat/VRChat_Data/StreamingAssets/SteamVR/actions.json as /data is missing!

Suggested fix: bind-mount ALL steam library data directories into the steam runtime pressure vessel, not only the one where the launched app (in this case steamVR) lives.

[kisak-valve]

Hello @Spacefish, this reads like ValveSoftware/steam-runtime#393. Similar to that issue report, you could try adding STEAM_COMPAT_MOUNTS=/path/to/unexpected/folder %command% to SteamVR's launch options as a workaround.

[Spacefish]

Hello @Spacefish, this reads like ValveSoftware/steam-runtime#393. Similar to that issue report, you could try adding STEAM_COMPAT_MOUNTS=/path/to/unexpected/folder %command% to SteamVR's launch options as a workaround.

Thanks for pointing me to that, that works and helps me a lot i added /data and /data2 to STEAM_COMPAT_MOUNTS

i tried sooo many things and i am happy that i finally found the root cause.. I did like 3-5 proton builds from source, with different game names and engine names in XrInit as i thought the issue might be that steam input does not detect the game, as the binding ui showed "wineopenxr test instance" as the game name all the time.. :(

IMHO it would be cool to at least add all configured Steam Library folders automatically to the pressure vessel,
as this problem will re-surface every time some game talks to any service / component running in a pressure vessel where the service tries to access a file in the games directory and the game was moved to another "steam library folder" by the user.

Maybe even only add it to appids which offer such services (like steamvr). Maybe by adding an environment variable via the steam app manifest to the part that set´s up the pressure vessel?

Probably more complicated that i think right now, as i don´t know the nuts and bolts inside the steamclient which setup up the pressure vesel / steam runtime.