EXPERIMENTAL: Virtual Reality

To recenter the VR headset, use Ctrl-Numpad5 (the binding can be fully customized, you can set it in your steering wheel buttons, etc).

If you have already centered the VR headset, and you dislike the current vehicle's position, then you can move the vehicle's seat by going into Options > Camera > Driver > Allow modification of seat adjustments. Then you can use the keys shown on screen to move the seat around for the current vehicle.

 

If BeamNG.drive is crashing to desktop, please provide a support ID number and I will try to find time to check the crash: https://supportid.beamng.com/

If it's not crashing to desktop, but merely refusing to activate VR, then it's possible that the upcoming v0.36 udate might fix the problem.

 

That's extremely weird, first report I see of such a problem on any headset (let alone on Quest 3).

Have you installed any 3rd party VR-related software? Some VR tools can "inject" themselves between your headset and the VR program, and tweak things - inverted rotations might be one such effect. If so, please fully disable, or better yet unisntall, any such software.

 

This is likely due to running out of VRAM. Your GPU should have enough VRAM for simplistic use cases, such as no traffic, in a simple map (avoid West Coast, Italy, etc, pick a small map instead), on normal resolution (no supersampling). Try that with Lowest graphics setting to confirm you get a normal framerate. If not, please try to avoid SteamVR (as that will "steal" a good chunk of VRAM for itself).

You can find more detailed tips about improving VR framerate here: https://documentation.beamng.com/support/vr/#framerate-is-too-low-what-can-i-do

 

There is no such command line arguments in BeamNG.drive - where did you read about that?

That aside, the error doesn't look familiar to me. A quick googling suggest that maybe ReShade can create this problem (if you have installed that), or possibly missing Visual C++ Redistributables, and other possible workarounds. Sorry I can't be of more help!

 

Yes, we're aware of the West Coast improvements taking a toll in system requirements. We're doing improvements to keep performance under control, which we'll be rolling out progressively in future updates. Hopefully that can help bring some of the lost performance back, without having to delete the improvements made to that map. Sorry about that!

 

Thanks for the reports. The issues are in our backlog, tho at the moment it's unclear when we'll have time to tackle them.

 

6GB will be on the very limit of usability for VR. It's likely you'll have performance problems running the more detailed maps, activating traffic, etc.

On very simple maps and with few vehicles, and low resolution/graphics detail, it can probably work to some extent. For a better experience, we recommend 8gb, or preferably 10+gb of VRAM.