EXPERIMENTAL: Virtual Reality

Just wanted to let everyone know my current experience with the experimental VR Mode.

First i launched BeamNG with the Vulkan Renderer while my HTC Vive was already connected. I launched the East Coast USA Map, and pressed Control + NumPad0 to activate the VR Mode. My FPS was terrible (1 FPS), i was quite sad because i thought my PC couldn't handle it (PC Specs below). Then i googled and stumbled across this thread, the solution that worked for me was from the user HeebieJeebie:

I tried what they have done, launched Beam, go into VR mode, and then connected my VR Headset. It worked! Normally i always get above 60+ FPS in the East Coast USA map, but with VR Mode it's quite stable at 45 FPS which totally works for me!

My specs:
CPU: AMD Ryzen 5 2600
GPU: ASUS Geforce RTX 2060 6gb
RAM: 2x8gb Corsair Vengeance LPX 3200mhz

My current graphics settings (Still experimenting with the settings):
Mesh Quality: Normal
Texture Quality: Low
Lighting Quality: Lowest
Shadows Visibility: None
Shader Quality: Low
Post Processing Quality: Lowest
Anisotropic Filtering: x8
Anti-Aliasing enabled mode: FXAA
Everything else is disabled for now

And lastly i just wanted to say THANK YOU to the BeamNG Devs that they finally implemented a VR Mode! I always wanted to experience what it would be like to play BeamNG in VR! Now we all can! And without additional software! Thanks guys! You rock!

 

so ive tried a couple different ways to get on vr mode but it doesnt seem too work and im kinda confused because when i start it, it laggs a lot but dosent start

(Edit) I got it to work

 

probably ran out of vram

 

After some messing arround and a few 0x000001 and C05 errors, I could start on my Reverb G2. The definitive step to do was disabling OPENXR API LAYERS on SteamVR Settings App
View attachment 1063471


After disabling them it went through

with 13600KF and 4070Ti got it running decently at normal graphics preset no traffic, and couldn't go higher because VRAM was already missing. If I turned traffic on then it was unplayable.

Thanks for the devs to add this key feature to me. Seems i'm going to spend more time in BeamNG

 

If you have the issue where your camera hovers above the car I found putting it in full screen and then resetting your camera (ctrl+num5) should fix it.

Hope this helps.

 

I can't get it to work at all. SteamVR simply crashes whenever I enable it.
I have my OpenXR runtime as SteamVR as setting it to Oculus doesn't do anything.
I use an Oculus Quest 2 over Airlink.
The problem is, if I open the game before SteamVR, everything (sensors etc.) work exept the feed to the oculus (either stuck in the oculus menu or a static 2D image)
If I open SteamVR first, and then open BeamNG, the feed works but SteamVR crashes as soon as I toggle VR.


and you can see the sensors working but not the feed on the oculus as shown here -> https://cdn.discordapp.com/attachments/722784852214153266/1154225929678237706/20230920_212046.mp4

Also even when the feed isn't working, the GPU is actually doing something since the VRAM usage and core usage (plus fans) are going high:


Any idea what would cause this ?

 

Pretty sure OpenXR toolkit is the problem. I was using it for foveated rendering in MSFS and looks like it automatically applied itself to BeamNG. I don't have time to check right now but everything should start working once you uncheck BeamNG from the toolkit settings.

 

I noticed in known issues, ffb for logitech is broken because of ghub (shocker...) Is this only the case when using VR or is it still broken when playing regularly as well? Ive been experiencing this bug quite often and its truly saddening because i havent even been able to experience this great game on this nearly worthless $1500 investment of a direct drive wheel

Thanks in advance Devs, you guys are truly so great for the amount of effort and work you pump into this game without ONCE attempting to charge us for what should be your usual updates disguised as "DLC Season passes". Thank you for not allowing greed and money to taint your guys' motives.

 

beamng devs...

THANK YOU FOR VR SUPPORT, HOLY F$@* YOU SAW HOW BAD VORPX WAS RIGHT??????

ok now that youre nearing Assetto Corsa in terms of vr support.... can you implement the best hand tracking support on the market? can you make it work if i cover my steering wheel with a single color paint so its easy to detect my hands and use a steering wheel at the same time and track virtual arms and hands?? PRETTY PLEASE???

yes, i know hand tracking sounds like a hard thing to implement but trust me us driving sim enthusiasts want this so bad... it truly is a killer app

 

i cant even figure out how to use it

 

launch game in Vulkan>load a map>go to display settings>scroll down to vr>activate it>use ctrl+numpad 5 to recenter view

 

For me with a 4090 and an Oculus Quest 2 with VirtualDesktop it's running pretty good, testing with a wheel, not sure about hand controllers but they didn't seem to work when I tested. However, first person view in the cockpit is constantly jumping around. Overall nice first version for something so beta.

 

Having the same issues, but relative cam is an excellent workaround

Problems I have run into:
The scale of the world seems off. everything seems like 80% scale (there is no way a cupholder is that small)
the UI is hard to use in VR mode/ it is intrusive
water is weird visually
The camera tied to the first person is locked and very nauseating doing anything offroad related, a free cam that is not tied to the role of the car may help, or a semi-free cam that uses a body head dampening to make it more natural.
Sounds in the cockpit are inconsistent with inside/outside noises
game crashes upon closing the game
no controller support? (interactive parts very hard to use)
graphical anomalies when tabbing to other vehicles.

I am using a rift s, with a 7900 xt, and a 5900x. (some of these issues could be driver-related)
Performance was surprisingly good, near standard performance.

I have been waiting for VR support since it was removed, I wasn't expecting it this early (considering all of the backend to get VR running) but it is awesome. Devs, Thank you so much!

I linked the settings I am using as the .json file

 

Im running 4090 with 5800X3D on Vive Pro 2. I'm experiencing a crash in every map. It will play fine for about 5 minutes, but then everything freezes and I have to ALT CTRL DEL. Anybody else having this issue of crashing after a few mins of playing just fine?

This is what my log says:
|E|engine::GFXVkDevice::submit::<lambda_84643ad2a8b54bd61d3e601c8a40076a>:perator
()| Failed to submit to transfer queue [ErrorDeviceLost]
()| No gpu markers
()| Failed to submit to graphics queue [ErrorDeviceLost]
()| GPU Markers: end [{ TopOfPipe }]
()| GPU Markers: end [{ BottomOfPipe }]

 

I'm also getting the same issue. It's almost like the perspective of the camera changes depending on where you are trying to recenter it from.

I've tried holding down the recentering button but it just seems to snap 5 or so degrees too far either way.

 

I don't have a numpad and so I cannot center my view with ctrl+numpad5, the button to center view doesn't work, and there is no option to rebind it. With the quest 2 my camera when in cockpit view is set about 1 or 2 meters above the car and the game does not interact with steamvr and ovr advanced settings, so I cannot offset the camera where it should be in the drivers seat. Driving around in orbital view is fine I guess but I would like to use first person view.

 

Still cannot get the VR mode to work after trying everything that seems even remotely relevant to my case in this thread. I have my Quest 2 hooked up and it works fine with other VR games, I'm launching BeamNG in Vulkan and loading into a map, but then when I try to turn on the VR mode nothing happens. No error message, no ramping up of the computer's fans, no feedback of any kind. It's like the VR mode just chooses not to start even after having tried starting it with both the buttons in display settings and with the ctrl + numpad 0 shortcut. Very disappointing.

 

I will just chime in with the same issue - even when holding the recenter binding the middle is somehow "skipped" and image wants to stay either to the left or the right of it, unless you adjust your height enough to overcome it. I use Oculus Rift CV1 with two trackers.

Also, can we "Lock to horizon" in any way in VR? Or at least make it less fixed to the car pitch?

It gets so bumpy in the desert lmao. I have tried using the Driver cam settings but to no effect.

 

You can actually remap the buttons but the naming was (to me) unexpected. If you search for "Headset" in the control settings you will find them.

I am incredibly excited for this as I love BeamNG but my current wheel setup is only usable with VR so I only played with controller these past few months, Unfortunately it keeps crashing for me and I haven't figured out why yet as it seems inconsistent. I can get it to crash randomly on the small grid map but I've also been able to play the Italy Garage Delivery with heavy traffic where it only crashed in the middle of my second run. Besides this the HUD/UI is horrendous because you can only see it with your right eye which creates a confusing experience. I would recommend looking at the Assetto Corsa VR HUD implementation the creator of CSP has added. (Settings > Custom Shader Patch > Mode Tweaks: VR > Custom VR HUD Renedering)

Honestly still very happy with the results as just adding this feature gives me hope for a future filled with BeamNG VR and that gets me very hyped. Thanks a lot devs!

My setup:
7800X3D, 4070TI (12GB), 32GB DDR5 at 6000mhz, Valve Index