


Poor manifest file pathing borks the VR experience
- /home/$(whoami)/.local/share/Steam/logs/vrserver.txt
- /home/$(whoami)/.local/share/Steam/config/steamapps.manifest
What Works
There's only a Windows version for the VR app, yet there's a linux port for the standalone non-VR version. The app is able to load fine in Desktop mode under Proton 6 (do NOT use version 9 or higher). It can be played in the basic desktop mode like the standalone app sold separately, and use a mouse or a controller with Steam Input mouse bindings to interact with the menus, then keyboard or set up controller in options.
What's Broken
For note, I'm using a Valve Index headset and controllers.
The headset can see the game fine in both Desktop Theater and the intended VR mode. The controllers do not work in game at all but work fine in SteamVR menus and any other game I test.
There's a lingering issue where the input manifest file can never be found, even if both Steam VR and the game are installed on the same storage device. It's due to some dependency I cannot identify on the Steam VR backend that is constantly updating the manifest path to something unsolveable (suspiciously always ending with a space at the end of the path). It's impossible to adjust Steam VR input bindings because Steam VR can never find the intended manifest path.
Because the manifest file can never be found, the tracking laser used in the main menu is never mapped to anything, and the developer never allows the headset itself or an external controller to select menus in case the controller mappings fail. Therefore, I can't start the game in VR mode at all. I need to use the Desktop variant and use VR Theater if I want to use my VR headset.
What can be done
The game owes a significant rework on embracing modern OpenXR practices or even a dedicated Linux port for VR, but because the overwhelming majority of customers are using Meta Quest headsets, development is focused on 3rd party wrapper tools that convert AIO Meta headsets and controllers into Steam VR legacy profiles instead of utilizing the fundamental OpenXR specification. I don't expect most modern lighthouse headsets or controllers to be supported by this app anytime soon.
Runs and opens roms from drive Z:

(SteamVR beta 1.7.2) File browser not working.