EXPERIMENTAL: Virtual Reality

Automatic VR Startup (OpenXR + Vulkan)

I created a small AutoHotkey script that lets BeamNG start directly in VR – completely without SteamVR.
It automatically opens the Mixed Reality Portal, launches BeamNG in Vulkan mode, and then activates VR.

How to use it:

1. Install AutoHotkey v2.
   
   
2. Extract the attached ZIP file.
   
   
3. Run BeamNG_VR_Start.ahk – administrator rights are not required.
   

⚙️ Note about the file extension:
Make sure the file really ends with .ahk and not .txt.
Windows often hides known file extensions, so BeamNG_VR_Start.ahk might silently become BeamNG_VR_Start.ahk.txt,
which will prevent the script from running.

To fix this:

• Open File Explorer → View → Show → File name extensions
  
  
• Then rename the file to BeamNG_VR_Start.ahk.
  

The attached script can be easily adjusted if needed – for example, to change the wait times or file paths depending on your setup.

For BeamMP (multiplayer):
If you’re using the BeamMP launcher, simply replace the Run line in the script with:


Run "D:\BeamMP-Launcher\BeamMP-Launcher.exe" -- -gfx vk

Thanks to the BeamNG dev team for the quick responses.

Have fun testing and driving! ️

 

Really fun game! The kids *really* wanted a VR driving sim where they can drive around cities with traffic... and BeamNG is amazing for that!

When fussing with the VR graphics settings, I noticed that some of the foliage (billboards?) were culling differently per eye.
As in, on my left eye I could see a clump of green bushes. On my right eye I could see the central bush and some smaller brown bushes.
I could rotate my head/move in & out to get the missing green bushes to appear on the right eye, or get them to vanish on the left eye.

I assume this is because each eye has a separate camera, each with their own draw distance/culling distance.
I wanted to point it out because it can be really nauseating & most players won't be able to spot what's causing it. Especially as it only seems to happen at the culling distance boundary.

I can submit a support ticket if this is new (I searched but couldn't find any posts about it) but I've seem that the shadows being different per eye is a known bug, so I thought I'd hold off & check.
If this is caused/fixed by the same thing, I'll avoid adding more tickets to the queue

Or even better if it's a known config thing and not a game bug

 

Sorry to go around in circles with this but I have since noticed that the work around I posted doesn’t fix the right eye stutter in external views, only internal views. I didn’t notice initially because vr is obviously mostly 1st person.
it may even be a separate bug because it is a very slightly different type of stutter - this one feels more like the game is confused about which way the headset is facing, not so much a frame timing related stutter.
So I feel like I have a combination of a frame timing issue, and metas OpenXR not liking Beam.
I’ve found after a fair bit of testing the most reliable way for me to play (not 100% but good enough to be enjoyable) is:

1. Turn off ‘game mode’ on the TV - this turns off g-sync, VRR etc
2. Set SteamVR as the default OpenXR runtime (initially this makes things way worse until step 3)
3. Force ASW to ON in the oculus debug tool

I still get some of the more funny stuff like shadows being rendered differently in the left and right eye, and the sun being in a different position in each eye, but these are nothing compared to the stutter and the game is still playable with these bugs.

 

Hello, so im having an issue where my VR Controllers are found and tracked but i cant interact with anything in the car or outside of the car. Is there any fix for this? Thanks in Advance!

 

hi, um i have a strange issue, when the graphics settings are set on lowest the game freezes whenever i activate the vr mode, what ive tried:
no mods installed, so mods are not causing the issue.
ive tried on safe mode vulkan lowest settings and it works
ive tried to delete the whole appdata/local folder, but the problem remains.
verified files through steam and beam launcher but still the problem remains.

 

I'm having this exact same issue but I'll try and give some more details.

I'm using the latest stable build on Steam and I'm using the Quest 2 headset and controllers. I'm also using a Logitech G920 steering wheel as my main controller and I also have a Microsoft Xbox 360 wired controller plugged in.

When I move the Quest controllers towards the interactable zones they turn green but no button on either controller will actually interact with anything. I've tried going in to the steam settings to bind new buttons to the controller but it has not done anything toward solving the issue. I've tried on multiple cars and the issue remains.

** Update Ok i managed to get it working. I got it working by choosing the top preset made for the controllers through steam and it now works with my quest controllers but not with the standard pre made confirguration which is odd. I'm just glad it's working.

 

Do anyone have the current state of Linux and VR? Proton-GE 8-26 crash if i try to start the Game https://github.com/GloriousEggroll/proton-ge-custom/pull/106

 

It works with the native Linux version and Monado. Never got SteamVR working with this game.