EXPERIMENTAL: Virtual Reality

Hi ,

same here. i had no issue before even if i had better performance dite virtual desktop

 

Unsure if it's related to the update, but removing all PointLights reduces frame time spikes *a lot* in maps where they're used.

For an example the Automation test track.
1. Look at the dam from a distance, observe as frame time gets spiky as hell
2. Press F11 and remove point_light folder
3. Enjoy steady frames

Personally I have automated this removal with a script so I don't have to deal with tinkering.

 

After 5 minutes the game crashes

 

I'm also getting those crashes since 0.33. Before that it ran fine. Crashing only in VR.

Did test with and without mods, clean install, low and high graphics settings.. no luck. Over on reddit someone had a little success when messing with his force feedback settings, he lowered the refresh rate or something like that, have yet to try that out.

Relevant hardware on my setup: nvidia 4060, amd 5800x, 64g ddr4 ram, quest 2 with link cable, and if reddit is right, t300rs steering wheel.

But while testing i noticed that i can play west coast on highest graphics settings without major stuttering, which was definitely not possible before 0.33 update.. soo at least something to look forward to, once devs fix the issiue.

 

I agree, the performance has increased significantly, but unfortunately it crashes after a few minutes.

Btw an option like VRSS would be useful, I hope they will add such an option in the next update.

 

Reddit link:

https://www.reddit.com/r/BeamNG/comments/1fkcvqs/033_stability_issue/

Anyway, got no further today, tested with newest nvidia drivers, no difference. But while driving mod cars it the game runs for not more than two minutes, while i can get about 15-20 minutes when i drive vanilla cars. Without unistalling the mods.

 

hi,
Yes same for me. I had very bad performance on west coast and now it is a lot better.

 

Looking at CPU & GPU frame times when it crashes, I seem to be getting spikes in CPU use every 3 seconds and one of those spikes always precedes a crash. It also seems that after a game freeze CPU use goes permanently through the roof some times. Crash seems to be heavily CPU related.

 

Alright i think i found a workaround for being able to play. I guess everyone having problems is using meta headsets, and openXR as standard, as mentioned in beamng documentation about vr. But after i've read the last few pages in this thread, i thougt about using steamVR as standard openXR runtime.

And for my unfortunately short testing, it actually worked! I set SteamVR as standard, which can be done in SteamVR - Settings - OpenXR - SteamVR as OpenXR runtime.

I tried throwing everything at the game which crashed it instantly before, like every mod i had, cars, maps, trailer towing, collisions and so on. I changed to multiple maps, changed graphics setting, and it still would not crash. I only had time for about 40 minutes of testing, but in that time it did not crash once. So please, try it out and report back in this thread, i guess it's kinda important to know for the devs if the runtime is actually the problem.

But being not the native runtime for my headset, it runs a lot worse. I'm running much lower graphics settings, and still maxing out my Vram, and getting framedrops. So pretty much like it ran before the update Have fun trying the "fix"

 

Hi
I’ m on the quest 3 i tried the workaround it but it did not worked.
I have set steamvr as the openxr standard and launched the game while i was in vr.
I have to say that it crashed a Little bit later than with the Meta openxr but it crashed.
--- Post updated ---

i have not tried to lower the lighting option.
Il will try that.

 

i'm on pico 4 + virtual desktop and i tried to lower the lighting option to the lowest and somehow it worked for me ,i tried with steamVR and VDXR ,no more crashes but i lost at least 20 to 30 fps from 0.32
in 0.32 i had 90 solid fps on johnson valley and little maps and 72 solid fps on bigger maps,Now it's struggle to reach 72fps
i have rtx 4080 and I9 14900k

 

Putting the lighting to lowest also stopped the crash for me - I drove about 45 mins before deciding to try one notch higher on the lighting (low) and crashed almost immediately. The game does look bad on lowest mode though so hopefully this can be fixed soon! Thanks!

 

I also did a little more testing, and my "fix" did not work a second time, at least not for extended periods of time.

But changing the lighting to lowest solved it also for me, but it just looks really bad. I hope it will get fixed eventually.

 

Is there any way to achieve the same thing as OXR toolkit Turbo Mode without OXR toolkit? I feel BeamNG, being CPU bound usually, would benefit greatly from this.

 

The crash is gone for me with the last hotfix
Ans the bad performance on west coast is Back
--- Post updated ---
But

But really happy that i can play again