EXPERIMENTAL: Virtual Reality

Thank you @Calatinus for the info, cant wait to try it!

 

howe do i change where the "driver" is sitting, it seems like im driving from inside he drivers seat rather than up at the steering wheel?

 

Seeing some parallax (?) issues in the shadows in v0.35.3.
Note the shadow position on the steering wheel. I promise that's left/right eye. Monado's debug gui doesn't make it easy to do side-by-side eye views so I had to gimp it.
View attachment 1220843

 

Thats an issue since atleast 0.34 which isnt specific to linux/monado. Happens on my Windows machine too. I hope it gets resolved with 0.36.

 

It seems VR still broken in 0.35. It crashes when switching to VR mode from the menu still. I'm using Virtual Desktop with it's own OpenXR. Does anyone have this working sucessfully?

 

Nah, VR should start up just fine in Beamng 0.35 with VDXR. Tried it out just now on my system. Didnt crash for me once.

Check out the wiki: https://documentation.beamng.com/support/vr
Maybe you find your problem/a solution there.

Also providing a bit more info would help to... help you. So far we only know you use Virtual Desktop and thats pretty much it.

 

Appreciate the reply, thank you. Good to know it's working with VDXR for somebody, thanks for checking. I am using Windows 11, nVidia RTX3090 with latest nVidia drivers, Quest 3 and latest Version of VD streamer. I've gone through that wiki, and also through the troubleshooting steps sent to me by support, but still having the same issue.

 

Following up, I tried to send this as a PM but y'know, it wouldn't.


Run WMR and SteamVR. You'll see in WMR that it it will have issues with some titles and it will have a 'Fix it' Button. Press it. That will force WMR to act as the OpenXR Environment. That will (or should) allow BeamNG to launch in VR for you. SteamVR CANNOT act as the OpenXR Environment for any class of WMR headset. it's just not compatible. WMR does not have a compatibility layer for that. You can affirm it'll work if you check the Steam VR Settings under OpenXR, if it says Windows Mixed Reality, it's set correctly. If it says Set SteamVR as OpenXR Runtime, it will NOT launch.

 

Hmm, i see. You pretty much went through the entire way of best practice.

Idk what the support suggested you to do, sorry if i tell you the same things. But i can think of a few things:

-The latest Nvidia drivers have a lot of problems from what i've seen and read. Maybe reverting to an older version could help. Its a bit annoying but manegable. Gamernexus just released a video on the topic(not vr specific tbf):
But at 21 minute mark they have a segment how to do a clean driver install. I'm on AMD but i reverted to an older driver version just last week because the current one has so many issues on my system.

-You could maybe check out the official VD Discord: https://discord.com/invite/8FaVdGVv

-I had an issue a few months back where the GUI rendering completly broke in Beamng VR. I resolved it by just deleting the User Data folder. When starting the game click on "manage userfolders" and then "open userfolders". Either rename the "0.35" folder(so you can revert back if you have otherwise important settings, saves, etc) or just delete anything in it besides the mod folder(if you have any). Lets you start with a clean slate. Sometimes settings just get borked over time.

-Maybe there just is a conflict with Steamvr and VD? Rightclick on Beamng in the steamlibrary -> properties -> installed files -> click on "browse" beside the blue "53gb on XY drive". Now exit steam. As in shut off the programm so it doesnt run in the background. Now start beamng via the Beamng.drive.exe in the folder that just opened before hand. With that the game will run without any steam interferece. Depending on the outcome you atleast know if steam is or isnt a problem in this case.

-Oh and just in case: You dont have AV1 encoding enabled in the VD streaming app, right? I believe the 3090 only has AV1 DEcoding but not ENcoding.

 

This is awesome, thank you. There are some things here I haven't tried yet. I will try and report back. Many thanks!

UPDATE: Tried each of these one-by-one, but still the same problem. May I ask what version of the nVidia driver you are on so I can try downgrading to the same version? Thanks.

 

Aaww, man.

I have an AMD 6900XT so i personally cant help you with a good driver version for nvidia. But i think a driver version before the release of the 5000 series should be better, so before january 30th? Otherwise consult the VD Discord, atleast for AMD cards they have recommended driver versions if you happen to have issues.

At last, but this is just shooting in the dark: I've seen more than once in vr adjacent forums, discords, subreddits, etc the recommendation to turn of hw accelerated gpu scheduling in windows: https://www.tenforums.com/tutorials...-accelerated-gpu-scheduling-windows-10-a.html
But idk i think this was more about fixing inconsistent frametimes.

Otherwise i can only think of reinstalling VD? Downgrading to an older VD version sadly isnt possible in a legal way. IDK if it even would help but cant really help you with that here anyway. :x

 

Can you try the Studio Driver 572.16 (not the Gaming one)? Seems I do not have any issue with it :?

 

Thanks for the suggestion. I tried this using the clean install option, but exactly the same result.

 

Sorry, one more question for you. Did you change to VR mode in the menu or did you do it part way through a drive? Wonder if that makes a difference.

 

my oqulus quest 3 oes not want to work with beamng. my camera is inverted, when i look up it looks down, when i look left it looks right. can i please get help, since i bought it and i cant return it.

 

Doesnt make a difference for me at the moment. I wildly switched between VR and Flat when i tested VD on my rig for you a few days ago. Both in the menu and 'ín game' and it just worked. It made a difference for me in the first two releases of Beamng with VR support 1 1/2 years ago where you really needed to manage your VRAM because of a memory leak that could happen. But that seems to be resolved long ago. Back then the game outright crashed sometimes when switching to VR.

Hard to tell what the issue is on your end. You could try if Beamng VR works with the other methods like Oculus Link, ALVR and Steam Link.

My experience is based on a Pico 4 though. Pico Connect (equivalent to the official Meta Software) and the Pico 4 version of VD both work in Beamng VR without crashes. Pico Connect relies on SteamVR and is a lot worse when it comes to the 1% lows specifically in Beamng. I suspect a CPU bottleneck with that combination but i havent tested it out because i havent shelled out the few bucks for fpsvr yet. VD with VDXR seems to be far more consistent. But i'd trade inconsitency against outright crashes in your case.

 

Sup guys!
I have 4060ti, ryzen 7 7700, Quest 3...
Airlink or Link does not matter. When I start vr mode - its 2-4fps and not improving. Steam VR graphics are red...
Tried with any quality preset, nothing helps.
I am a step away from breaking my pc rn
Please Help.

 

It works for me. Try deleting cache, reinstalling the game, and updating your drivers. If all of this doesn’t work, then come and complain.
--- Post updated ---

Is steamVR your openXR runtime?
--- Post updated ---

set your openXR runtime to the meta app. Better performance.

Usually this can be fixed with trial and error, restart the pc and beamNG over and over if nothing works

 

With my setup I am able to achieve 120 fps on a Pimax Crystal headset at 70% resolution as long as I don't look near the center of the map. When I do, however, my framerate dips to around 30-40 fps. Most graphics are on high, but I kept my textures on medium and my mesh detail on low.

Interestingly, when I go into the world editor and disable visibility of the vegetation, my framerate stays at a locked 120 fps. It looks to me that vegetation has one of the biggest performance hits in VR.

I'm not an expert in computer graphics, but the issue here is probably because there is no stereo instancing being utilized when rendering vegetation (and neither for static meshes). The CPU effectively has to send the vegetation render pass to the GPU per-eye which seems to be a large hit in CPU performance. Vegetation is already pretty heavy on performance in flat mode, but doubling it is killing framerates in VR. Would be nice to see some optimizations in future updates.

Any thoughts on this @Leeloo ?

 

Wanted to come share my experience so far with VR, it's been really good! Initially tried on a 5700XT and that was rough. Just enough performance to check it out but not really enjoy it. Now running a 6800XT and it's pretty decent experience. Solo it's pretty good, multiplayer is good up to maybe 6 cars on West Coast, and maybe 8 on East Coast before I start dipping to the 20's- low 30's and things start to get unpleasant but have played with up to 14 cars and was still stable just down to 20-24fps. Stability has been really great as well, have had one buggy incident that I ended up reinstalling my gpu driver because it did something funky after the game crashed, but outside of that maybe 2 crashes in ~30hrs of multiplayer way better then I was expecting.

My only current gripes:

Resolution / Anti Aliasing: Everything looks so jagged and looks like it's rendering far below what should be native res. I pushed the game to 150% render res and it still looked far far worse then every other VR game at native res, AA settings made a minimal difference but did hurt performance so left off.
Pop in: It feels like the LOD distance is about 20ft in front of the car and is very obvious and distracting, some fire hydrants don't render at all until about 20ft away from them. There's a mod that drastically improves this without too big a performance impact but for multiplayer which I do 90% of it's forced off.
Performance: This is more of a I wish it had better performance but I'm typically hitting nearly unplayable framerates in multiplayer past 8 cars and realize it's a CPU limitation and that there's probably nothing to be done there as the game has already seen incredible optimization over the years.
Occasional frame stutter bug: Every so often launching VR there will be a weird constant frame stutter, where it's like 5 smooth frmaes then 2 skipped frames giving it this strage stuttery feeling, last time it happened I found relaunching just VR, not the whole game was able to fix it.

Ultimately came here more to give a positive shootout to the current state of VR and thank the devs for listening to the community and adding it. I've had Beam since 2014 and it's kind of just sat the last few years as I ran out of ideas to do in it but with the addition of VR I hopped back in, found some online cops and robbers servers and have had the most fun I've ever had in Beam, excited to see future updates with it.

My Settings:

VR Res: 100% in game, 136% in Steam VR
Mesh: Ultra
Texture: High
Lighting: Low
Shadow res: Normal
Shadow Vis: Partial
Shader Quality: Low
AF: x4
AA: off

All special effects off except Detailed mirrors (1024, 0.3, 400m)

My specs

CPU: R5 5600
GPU: 6800XT 16gb VRAM
RAM: 32gb 3800mhz
Headset: Valve Index