EXPERIMENTAL: Virtual Reality

Hello everyone! I really need your help rn. Trying to play with my Meta Quest 2. VR mode is working, frame rate is good but game on my VR is Shaking so much. On monitor its all good, not shaking. But when i put quest 2 on my eyes its very shaky.

3060 12gb
32gb ram
Ryzen 7 5700X

 

Install https://github.com/mbucchia/OpenXR-Vk-D3D12 (that bypasses SteamVR and saves a lot of vram) and use OpenXR toolkit. 90fps with my G2 at 100% resolution on a I9 9900 + 2080S. I don't have any audio issues but you can simply switch the audio output in windows to the hmd I think?

 

Ah yes, perfect VRAM utilisation

Does anyone know how to get sound to play to the headset? It's selected in windows, works in other games, but BeamNG refuses to use it. Even youtube uses the headset.

 

Loving the new VR!! running it on a 6DOF motion rig and its really great. Just one issue- I have a Pimax 8kx and i suppose since it is so wide, i see the 2d UI overlay very far apart in each eye. the car/world render fine, but each eye sees a ghost image of the 2d elements. i have to close one eye to use them, and they are in the way while driving

 

I see a lot of people with powerfull PC having 6-7 fps on Vulcan render... That's kinda weird for me because my spec are:

i5 6400
GTX 1050ti 4GB
8GB DDR4

On vulcan render I have like 70fps but draw distance is bad... With same graphics settings on regular renderer I have normal draw distance.
VR... There's real weirdness starts... 21fps... Pretty stable 21fps with GTX 1050ti and Oculus Rift (CV1). Not 2, not 1. 21 fps. Sometimes it jumps to 45fps or drops to like 10fps and less. Depends of place.
My friend who use RTX 2060 and Quest 2 had like 5fps. I don't understand that to be honest.

 

Your headset resolution is probably low enough to not lag out your 1050ti too much

 

Honestly it's interesting that most folks move to lock to horizon instead of just turning off head movement...
Unless you're in a motion rig or something, your wheel and shifter positions are static, generally you want those to be in the same spot in game as they are IRL.

Inner ear stuff is just one of many VR types of sickness

 

You suppose to click on PImax parallel projection setting in Pimax device settings. But this click will cost for you some performance. At current time i'm using without it, with one eye, but playable.

 

So somehow, I managed to get 70fps at full resolution on the G2, and it was absolutely incredible. Thanks devs. Even the audio worked. I have no idea why it just started working but I guess my hours of tinkering worked. I have to say, BeamNG VR is like an Alfa Romeo. It's "that roller coaster of pain, disappointment and agony and the brief moment, when everything works."
Here are my settings if anyone's interested. Using WMR OpenXR runtime, without SteamVR on the Reverb G2

(Edit: game just crashed)

 

I hide the UI elements completely. ALT-U if I remember right.

 

Try covering the inside sensor with the headset off your face, I had something similar happening trying to run maps that needed more VRAM than I have (looking at you west coast lol), on the screen it ran fine, but the moment it started rendering in VR as well (activated by that sensor) it used too much VRAM and it would drop to around 8 FPS, which seems to make the camera glitch around really bad.

And make sure you have graphics quality on lowest, you can up it as you tune your settings to what your PC can handle.
You really shouldn't have lag though if your settings are low, as you have 4 more GB of VRAM than I do and my game runs fine.

 

My brother is also having the same issue as Niel. He uses an AMD Ryzen 7 3700x, RTX 2070 Super, Windows 11, Valve Index Headset. In fact he has the same specs as my PC except he is using Windows 11 and I'm using 10. On my brother's PC, every time he begins to drive for about 10-30 seconds it has a hard freeze, and sometimes the game will actually still be running in the background. The renderer crashed I guess, but not the game itself it seems.

On my Windows 10 machine (same specs) I don't experience this freeze the same way. I do get the freeze on occasion (with the game still running in the background), but it seems to happen at random rather than happening after I start driving.

This is happening on hotfix 0.30.5.

 

specs-(win 10 pro OS)ryzen 5800x3d cpu, msi x570 mobo, XFX 7900xtx 24gb gpu, 32gb 3200mhz ram quad channel,1600w psu,2x2tb m.2 nvme.. running at my global cap of 79fps for my rift S( i dont change it for the quest 2)

framerate is hit or miss, used only vulkan so far with VR as i didnt think/know it worked on the normal renderer.. rift S and quest 2.. vanilla maps with light mods along with traffic work fine online(beamMP) without much lag with graphic settings mostly at normal or high. --- have to redo my settings for every server(depending on mods and people online at the time) which really makes me wish they had graphic presets i could save to swap if i get stutter.

offline you can run a bunch of badly optimized mods+ traffic without any real issues.

best thing you can do is turn off screen mirroring in display- really takes a load off the system, but downside is unless you have something inline to capture what you see in your headset you have no way to record.. only way is to have the game show a single eye render or using a program like oculusmirror but there goes your performance boost..

 

BIG UPDATE FOR CRASHES!

I've just found out for those people who experience crashes after 5 or so mins of driving and end up getting the HANG error after exiting the game, TURN LIGHTING to lowest setting. I have not had a single crash ever since setting lighting to lowest.

But make sure LOWEST is selected, not Low.

Hopefully this might help the Devs figure out what's causing the game to hang with the lighting graphics options.

 

I used OpenXR, but at 100% resolution, low/medium settings, I only get about 55fps in most maps, and slightly higher in West Coast. How did you not run into any VRAM issues? It always uses 11gb+ for me.

 

I'm suprised anyway. I guess it's more like CPU bottleneck than GPU here.

Lock to horizon reduces VR sickness and it feels more natural because if u going uphill in real car, heat naturally wants to be "locked to horizon".
Having IRL rig parts in different positions that in the game isn't a problem because muslce memory kicks in ;p It's even hard to have that in same spot with some headsets because world scale can be different and slider to adjust world scale in VR is really rare.

 

i tested it out. and i can confirm
--- Post updated ---

normaly it freezed after 2 mins. with the lighting on lowest i can play for hours and no freeze