EXPERIMENTAL: Virtual Reality

I just wanted to give VR another try but both with Monado and SteamVR I'm always running into the following error trying to activate VR via the settings:

24.93304|E|logIfError| Error in pfnCreateVulkanInstanceKHR: xrResultToString(-2) = "XR_ERROR_RUNTIME_FAILURE"

Any idea what's up here? Everything seems to be up-to-date and I cannot imagine what else to check
Thanks!

 

You mentioned Monado, so I'm guessing you run Linux?
How are you launching BeamNG? Do you use any environment variables on the launch command? What GPU do you have? Are you running up to date Monado?

For me personally, VR only works with Monado on Linux. I do get some error with SteamVR, but can't remember right now, what it was.

 

running the native linux build, no environment variables that I know of, radv, rx 6700xt, up to date monado - I had to recompile it just before use.
I had marginal luck with monado previously. It wasn't really usable because I had a still frame stuck in front of my face that moved with my headset, but at least I got some output. Now I can't even get that to work.

 

What headset do you use? Are you running and building Monado with Envision?

 

It's a valve index, not running through envision

 

@UltraBlack_ I would try with Envision to make sure that Monado has all the required environment variables in use.
I launch the game with the desktop icon that was created by running the shell script in BinLinux-folder
(BeamNG_install_desktop_file.sh)

I also edited the BeamNG desktop file so that it launches the game with environment variables SDL_VIDEODRIVER=x11 OXR_PARALLEL_VIEWS=1

 

Anyone know a fix? I've tried to run beam on Vulkan, With and without Oculus Air Link, I've tried opening the game with the "-vr" or the "-openxr" commands, and etc, but to no avail

 

Greetings.
West coast map is unplayable because of performance. It used to work before the recent 0.35 updates that changed meshes or loading or whatever the changes were. Other maps are still working fine but using Vulkan + VR West coast runs at a snails pace.

Quest 3
Ryzen 9900x RTX 5080
windows 11
Same issue on my old system. I had just bought a new PC. Old system used i7 8700k and RX 6900xt

 

I have been testing BeamNG in VR lately and I am really enjoying it. Performance is good enough to enjoy the game in VR. The detailed mirrors are essential for good immersion. I highly appreciate the efforts the devs have put in so far.

My system:
PSVR 2 with PC adapter
Ryzen 5700X3D 32GB RX 9070 XT
Windows 11 Vulkan renderer

However, there are quite a few graphical glitches breaking the immersion.

• First issue is a weird horizon issue in VR, I attached a screenshot what it looks like.
• Second issue is the shadows not rendering the same for the left and right eye. It also looks like LODs for both eyes are also not always the same
• Third issue is the world LOD updating way too close, this is is very obvious in VR. Is there any setting to increase the LOD distance?

 

I know this is old, but I wanted to test my hardware on a Linux Setup, run into the same problem, but applied this solution... and it is SUCCESSFUL!
Using Ubuntu 24.04.2 LTS and ALVR with Pico 4 with version 0.35.5 and SteamVR 2.10.4
Ryzen 7 5800X with RTX 4060 TI -> driver G06 (version 570)
I have used the Proton 3.0.4e tag with the applied patch to the openxr.c file like mentioned in the Github Gist then recompiled the Proton locally:

Luckly, the make utility automatically will add the local build of Proton in the ProtonUP-QT:


The experience is very consistent, similar or better than windows on High settings, Italy, with AI. It also works on Ultra, but is more sluggish and staying in the 20-25 FPS range:

I post here the local build in case anyone might have had a similar issue and wants to use this tweaked Proton build:

 

Before installing I wanted to ask you if my hardware is sufficient to run BeamNG in VR even with low settings:

i5-8300k 3.6GHz
Gigabyte Rtx 2060 6GB
32 GB DDR4 (16x2)

Thanks in advance!

 

I tried VR for the first time in a while on v0.35, and shadows now seem to render differently in each eye. If I close one eye at a time, I can see that the shadows in my vehicle are offset a few inches between each eye. Not only is this extremely nauseating (I had to play with shadows off), but I'd assume it also means shadows are twice the cost performance-wise as they should be. Is this a new issue, and is anyone else having it? Tested on Windows 11 with SteamVR v2.11.1 streamed to a Quest 3 with Steam Link.

EDIT: I should've done my due diligence by searching this thread before posting. I see this has been reported before. Hopefully, it gets resolved soon, as it makes playing with shadows in VR completely impossible.