EXPERIMENTAL: Virtual Reality

Would it be possible to attach a node to the vr controllers using a lua script?

 

Trying to get motion sickness at the Airport roundabout in Italy. 10/10

Updates from my side: got an RTX 4060 TI as I am still waiting for Intel to "support" VR on their side for the A770.

Solid 38 FPS with High preset + full mirrors.
The only thing that glitches is if I enable Between eyes mode for the Debug display only if I enable High Quality mirrors, I will get artifacts on the screen and ~10FPS drop, but this is acceptable as who would want to watch this anyway:


The workaround would be to actually use the Steam VR's VR view window, which does not impact performance.

I am very pleased by the result and smoothness, I will no longer play on a display - once you have experience this you cannot un-experience.

 

BeamNG.drive 0.32.5.0 0x00000001
Instant crash when enabling vr, Pico 4 with virtual desktop, I tried Pico´s own streaming assistant but couldn´t get that to even launch with beamng.
Graphics settings, everything on low & without vr it launches fine.

 

I also have the Pico 4, but i do not use Virtual Desktop, just Steam VR + Streaming Assistant. What GPU are you using?

 

6900xt, previously I had Reverb G2 and VR worked fine. I have to try the streaming assistant again, last time nothing happened when I tried to enable VR.

 

Managed to get it working with Pico Connect wireless mode, and seems I can keep Virtual Desktop installed, just need to change openxr to steamvr when playing Beam n.g. Thank you.

 

I'm just having an issue with it saying I have no VR connected I'm using Steam VR

I'm using an RX 6700XT
R7 5800X3D
Arch Linux
An Index

I tried Mondo other than being slightly more annoying it didn't change the result.

 

Specs in sig.

I'm getting a lot of screen tearing. It does not seem to matter if I enable V-Sync or if I alter the framerate cap. Not sure if a 2070 counts as an "older" GPU for purposes of the known issues, but if anyone has any suggestions, that would be appreciated.

EDIT: Forgot to mention, I have an Oculus Rift S.

 

Having vehicle mesh visibility below 100% seems to have a severe impact on performance when running VR. I believe a similar effect is in use when non-vehicle meshes (trees etc.) fade away, also resulting in poor performance.

Additionally lowering FOV in SteamVR settings actually has a negative effect on performance, because mesh visibility/some other things are tied to the FOV of your viewport (not sure what the terms are here).
--- Post updated ---
If anybody has managed to get FFR or FSR working in this game using external software, please share your findings.

 

Havey you tried playing around with some older mods which have the mesh composition a little bit more "unusual"? I'm noticing the same thing. You can try the Dacia 1310 mod for example.

 

VR mode worked fine last night, was racing with multiple AI on medium sized maps without anything besides minor slowdown, after 0.33 vr crashes after a few minutes, or on attempting to load content (time trial, scenario, etc). I'm running a completely fresh install and user folder, no mods installed, on extremely low graphics settings, lowered from what i played with last night without any crashes.

Using a Valve Index and SteamVR on Windows 10.

 

Looking at trees/foliage seems to *sometimes* introduce high frequency frame time spikes that show red on the SteamVR frame time graph. Couldn't pintpoint the exact cause but its rather game-breaking for me. GPU is 4080S paired with a 5800X3D so I don't think specs are the problem. Happens even with all settings on lowest.

 

I also started getting these crashes. I think something has gone wrong with VR in the 0.33 update.

 

I had a very good experience in VR with the 0.32, 90 or 72 smooth fps, i have pico 4 in ultra with virtual desktop with a 4080 and an i9 14900k, now with 0.33 I have crashes after 30 seconds in game
I hope the fix this issue because i can't play on screen anymore

 

Not completely sure if this bug was introduced in 0.33 or if it has something to do with Proton, but it seems like the game skips the launcher if SteamVR is already running.
This is intended as far as I know, but what probably isn't intended, is that it now seems to default to Direct3D instead of Vulkan, which of course is required for VR mode.

Small addition:
Seems like it might have been an issue with the Proton version I was using, I used GE Proton 8-26 at first and it seems to properly switch to Vulkan when I selected Proton 9.
Though it doesn't want to enter VR mode with Proton 9, it thinks for a couple of seconds when you hit the "Understood!" button and then just closes the popup.

 

Someone told me to add my two cents on 0.33's vr issue. Idk, I feel like it's a vram issue for me as my graphics settings were set really high wherever cpu usage wasn't affected (major cpu bottleneck on this laptop).

The crash only happens in VR, playing in desktop mode is perfectly fine save a stutter or two here and there.
Hell, even VR runs perfect until it randomly crashes. Any time this happens my PC nearly completely locks up until BeamNG's crash handler kicks in and closes the game. I don't get to see what the error actually is, so I legitimately cannot make a proper statement on the matter. Oh well.. I hope they find it and fix it.

 

Same here, VR runs perfectly with high/ultra settings with my RTX 4060TI before the 0.33 update.

However, after the 0.33 update, VR randomly crashes from 10 minutes of gameplay. I've done a clean reinstall, tried safe mode, updated GPU drivers, and it still crashes!

The error (0x00000001) provides no guidance on this issue, and I'm left quite dumbfounded after trying all solutions.

Although, when I verified the integrity of game files, there is always one missing file, even after the clean install. I wounder if this has anything to do with my VR issue.

 

Hi I am also getting crash in VR. It crashes just a few seconds after i start to drive.
I am using a Quest 3 with link cable.

 

I get the same error when verifying. According to the log i'm missing "VCRUNTIME140_1.dll". Tried reinstalling Microsoft Visual C++ 2015-2022 but didn't seem to do anything