EXPERIMENTAL: Virtual Reality

Hey stenyak, a while ago a patch was made to protonGE to get VR working, you requested that it be undone as an official fix would be implemented in 0.32. (it was never implemented)
Would appreciate if this was fixed for 0.37, useful links are below. Thanks in advance
https://www.beamng.com/threads/experimental-virtual-reality.94206/page-27#post-1674152
https://github.com/GloriousEggroll/proton-ge-custom/pull/109
https://github.com/GloriousEggroll/proton-ge-custom/pull/106

 

Thanks for the help. I reached out to the creator of OXRMC and he's happy to assist if you can provide a game key. PM on the way.

 

BuzzteeBear took a look at this issue and provide a solution to enable motion compensation. Open the OpenXR-MotionCompensation.ini file and find the overlay_enabled = 1 setting. Set that to 0 and you should no longer run into the crash when launching VR mode. You'll want to reenable that someday if you need to see the overlay but it's a solution for now.

 

Note that you can also just add the line 'overlay_enabled = 0' into the BeamNG-specific .ini file of oxrmc. That way it's only disabled for BeamNG and you can still use it in any other title

 

Would be really nice to see this implemented bc BeamNG in VR is very single core bottlenecked. Have to reduce render distance to low to increase GPU utilization on an RTX 4080 Super and Ryzen 9 7950X3D. We could potentially see some large performance gains with Single Pass Stereo and additional renderer CPU optimizations.

 

The supportId button doesnt exactly work under linux

 

After looking through the replies did not see mention of this when the shadows are not rendering as expected that started happening in v0.35.

The shadows appear to render as you'd expect in the left eye, but they change position as you move your head around in the right eye, here's a demonstration recording each eye. It's way more apparent in VR when you close one eye, but you can see it in the video.

 

- windows reinstall literally is what it took to get vr to enable again after this update... that hurt.

 

When I saw the performance updates to VR in the change log I got excited. But I was disappointed to see that VR performance is still very poor. I have an RTX 5090 and a Pimax Crystal Super. I have to cut the resolution by more than half to get it to run at an unstable 72 fps.
In comparison, Assetto Corsa Evo, one of the most poorly performing VR supported games to come out recently, run about 20% better and has graphics that look multiple generations ahead of BeamNG.

 

gridmap without traffic is recomended for vr users

 

I still got a huge dose of right eye stutter some time after changing all this.
Was messing about trying to get things back and I ended up changing to windowed mode, disabling vsync, and locking fps to 45 in game. right eye stutter disappeared after locking fps.
but then I tried to reproduce it by turning each option on one at a time and I couldn’t get the stutter to come back.
so it doesn’t seem to be one setting causing it. More of a bug that seems to get squashed by changing one or more video settings.

I’ll try again to reproduce it if it happens again.
Quest debug shows the game trying to output 60fps and a negative frame queue buffer so maybe vsync timing still being applied?

edit: found the stutter to only happen if the game window was the active window ie if I tabbed it into the background the stutter went away (but no sound).
In the NVidia app I disabled g-sync for BeamNG (set to fixed frame rate) and I think that got it. Both VR and the TV are running at 45fps steady now.

 

Question about VR/Vulkan startup with OpenXR:
I’m using VR with a Reverb G2 and launch BeamNG via Vulkan. From what I understand, OpenXR in BeamNG intentionally runs without SteamVR directly through the OpenXR runtime, which is the goal to avoid the extra layer.

At the moment, I have to start the game first, then manually open the Mixed Reality Portal, and finally enable VR inside the game. It works, but it’s not very comfortable.

Also, trying to attach the Vulkan launch parameter directly to the .exe doesn’t seem to have any effect. Is Vulkan automatically applied once OpenXR is active, or does the game use a different startup logic?

 

Thanks for the explanation!
I tried launching the .exe directly with the parameter, but the game still runs in DX11 unless I switch to Vulkan through the launcher.
Just to be sure, here’s the exact path and command I used:


D:\Steam\steamapps\common\BeamNG.drive\Bin64\BeamNG.drive.x64.exe -vulkan

Could it be that Steam’s launcher blocks or overrides the start arguments?
Is there any way to bypass that, just for testing purposes, to launch directly in Vulkan?