Describe the bug
VR games run in regular 2D desktop mode.
Note: I am using a PSVR with SteamVR+OpenHMD driver.

To Reproduce
Steps to reproduce the behavior:

1. Correctly register the SteamVR+OpenHMD driver
2. Start Steam
3. Start SteamVR
4. Start (for instance) Elite Dangerous in VR mode
5. See the "next up" prompt in SteamVR in the PSVR headset
6. See Elite Dangerous launch on your main monitor (the "next up" prompt disappears in the VR headset)

Expected behavior
Elite Dangerous should start in the headset with the head tracking and the 3D rendering.

System Information (please complete the following information):

• Distribution: Manjaro
• SteamVR version: 1.16.8
• Steam client version: Feb 12 2021, at 23:22:26
• Opted into Steam client beta?: No
• Graphics driver version: Nvidia driver 460.39[run nvidia-settings or vulkaninfo | grep driverInfo:
• Gist for SteamVR System Information: here

Screenshots
Nope

Additional context
About the driver: Running vulkaninfo | grep driverInfo returned this:

ERROR: [Loader Message] Code 0 : /usr/lib32/libvulkan_intel.so: wrong ELF class: ELFCLASS32
ERROR: [Loader Message] Code 0 : /usr/lib32/libvulkan_radeon.so: wrong ELF class: ELFCLASS32
WARNING: lavapipe is not a conformant vulkan implementation, testing use only.
	driverInfo         = 460.39
	driverInfo                                           = 460.39
	driverInfo         = 460.39
	driverInfo                                           = 460.39
	driverInfo         = Mesa 20.3.4 (LLVM 11.0.1)

My VR setup is as follow: I only have the PSVR connected with no webcam to do the full head tracking, and no hand-held VR controllers. I rely on the OpenHMD driver to tell SteamVR that my head is never moving in space (head rotations are correctly tracked) and to add two virtual controllers.

Prior to creating this bug report, I raised the issue to the owner of the SteamVR-OpenHMD project and the driver should work well enough since SteamVR does the head tracking correctly.

While writing this Bug report, I have gone through the little list of VR compatible games I own and realised that now The Forest launches in VR correctly, I can not browse the menu as I currently emulate two dummy controllers so I can not point at the menu and select items in it on the welcome screen. This one game is the exception and it wasn't working that well a month ago.
Here are the behaviour of other games:

• SteamVR Home: Runs well, controllers are not moving as they are dummies, I can navigate the menus using a wired PS4 controller and gaze pointing. I can not walk or teleport (since I can not use the controllers).
• SteamVR tutorial: shows the "next up" prompt and never launched.
• Steam 360 Video Player: Launches in the headset, displays nothing, when trying to play "Lego Batman: The Batmersive Experience" I seem to open a second Steam 360 Video Player instance through wine. I've never watched any frame of that video, only black screens.
• InMind VR: Launches in 2D on my main monitor, the game can be played using the mouse to look around.
• Elite Dangerous: Launches in 2D on my main monitor and runs is if it wasn't started in VR mode.
• Tabletop Simulator: Shows a warning when starting: "Tabletop Simulator will launch into an environment in your VR HMD as well as on your desktop. Performance.....". Game launches in 2D on my main monitor and SteamVR never leaves the SteamVR Home.
• Google Earth VR: Crashes immediately with no error window, SteamVR shows "next up" prompt. Steam shows all these messages when started in a terminal.
• Blender 2.91.2 (Using XR_RUNTIME_JSON=~/.steam/steam/steamapps/common/SteamVR/steamxr_linux64.json blender so Blender can find the VR session to connect to): SteamVR shows the "next up" prompt but blender crashes with a segmentation fault.

As a sanity check, I have tried on Windows to run Elite Dangerous in VR and Blender in VR using the free version of the Trinus PSVR tool and both worked in VR correctly on the same hardware.

Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.