EXPERIMENTAL: Virtual Reality

How did you set it up? With my 1080ti I can barely get 30FPS on the gridmap at "low" settings.
Even after restarting the game to avoid the issues of the VRAM leak.

 

When I click the VR button in display options it gives me that warning that I ctrl+0 past, then nothing happens. Game doesn't display on my Quest 2. Have the Oculus app open, using a link cable, headset has Oculus link on, but the game won't come up on the headset.

 

You might need to open steamvr. I go throught virtual desktop and steamvr and it works fine.

tho oculus should have a openxr runtime if i remember correctly.

 

Hi, a few days ago I doubted if I should get a vr headset, but I don't think it is worth it when I can't play beamng on it. And then I saw this, but I am not sure if it will run on my laptop. Has anyone by any chance tested it on a rtx 3070 laptop with a ryzen 7 5800h?

 

Awesome with VR!

Is it possible in any way to lock view to horizon?

The settings for Driver camera do not seem to apply in VR.

Maybe in the driver lua file?

 

I tried going through Steam VR as well, but the library button in Steam VR wasn't working so I couldn't launch the game from there
Edit: did eventually get it to launch the game through steam vr but it made zero difference

 

Did you launch the game in Vulkan mode?

SteamVR should not be necessary with an Oculus headset.

 

Seems like people seem to be running fine, though I haven't had any luck to get playable framerates. Heck even getting it to load into a map from VR in Main Menu just doesn't seem to work, it just freezes and even after waiting 5 minutes it didn't do anything. I dropped the settings to the aforementioned ones but still no dice getting anything playable.
Specs:
Ryzen 7 3700x
RTX 2070 Super
32 GB 3200 MHz DDR4 RAM

Update:
Tried again with basically everything closed
Only observed 7,4/8 GB VRAM usage, nothing more.
And still unplayable...

 

I did launch in Vulkan, yes

 

I literally pushed all the graphics setting to lowest possible.

What happens if you load a map before going into VR?

 

I am noticing very low GPU utilization. Looking at task manager it seems like there is less than 1/3rd load on the GPU (Asking Graphics_1 on my 1080ti because that has normally been the more fitting measurement). Looking at my GPU temps this also seems to be true, as under heavy load it should be in the 60°C to 70°C range. Seems not to be a problem with the framebuffer, as only about 9GB of 11GB is utilized (Tho some system swapping is occurring, seemingly ~700MB, but that might just be some Windows-Stuff).
This nets me a total of 17FPS in East Coast at the low preset.

I don't know if I am starting the game wrong (Vulkan -> Go to map -> Connect to Virtual Desktop -> Start SteamVR -> Go into BeamNG VR), or if this is something else. I also just updatede the Graphics drivers.
CPU also seems underutilized, tho one thread is heavily utilized.

Here are some screenshots of the task manager:
GPU:


CPU:


I am a bit out of ideas, especially as other people with a 1080ti seem to have no issues.


EDIT:
Asking nvidia-smi it seems the GPU is definitively underutilized:

Code:

+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 537.34                 Driver Version: 537.34       CUDA Version: 12.2     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                     TCC/WDDM  | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA GeForce GTX 1080 Ti   WDDM  | 00000000:07:00.0  On |                  N/A |
| 34%   55C    P0             119W / 280W |   9044MiB / 11264MiB |     38%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+

 

I'm getting the issue where my vision is above the vehicle in Driver camera. I'm using Oculus Quest 2 with the Oculus OpenXR runtime, and i don't have any addons or custom things for positioning.
--- Post updated ---
If the "recenter" button located in Display > VR is supposed to do something, it doesn't in my experience. Haven't tried the input binding yet as my keyboard hasn't a Numpad

Update: I recenter using the keybind after I got in the Driver camera and it works good now!

 

Like everytime it froze and never loaded, now it seems to work but still crap performance...

 

For anyone using Quest2: Oculus's OpenXR runtime renders faster. Using SteamVR crushed performance in my case

 

I've never used SteamVR, always used Oculus runtime, so why...

 

Have you tried doing this in the following sequence?:
1. Launch Oculus
2. Launch BeamNG in Vulkan mode
3. Without activating VR, get into a map
4. Put on your headset and activate VR

I'm getting maybe 70 FPS in the Pure Grid (the most minimal map) on a Ryzen 5 and an RTX 2060.
Haven't tried normal maps yet, was trying to fix the camera problem

 

That is exactly what I've been doing. Except West Coast instead
--- Post updated ---

Ah, I guess part of the whole thing being experimental, I can run any other VR Game fine, with increased resolution, I even got AC and ETS 2 to work decently so I expected this to be fine.

 

Afaik WC is the map requiring the most beef, and even then it may not be optimized for rendering at 90fps on what I assume is a single render thread...

 

I took the warning about high hardware requirements as a challenge and tried this out my ancient machine that I daily for a laugh.
It's got a AMD Phenom II X6 1065T, a 4GB Radeon RX 570, and about 18 gigs of DDR3, a machine barely good enough for normal BeamNG.
Ran it to an Oculus Quest II through Virtual Desktop, and pushed Beam's settings all the way down.

Worked about as well as you would expect, but it did technically work! The game was a slow vomit comet, and I couldn't seem to get the headset controllers working.
Obviously I've got some upgrading to do before I can actually use this, but I'm super excited to see this get reimplemented into the game, Wonderful work!