VR Discussions, Questions & Feedback

This is exactly the point. My GPU floats around 50-60% usage racing daylight. Quest ang GPU have to compress, decompress, etc. The tiny ms my CPU/GPU uses to render just 3 more frames is nothing If we look at the big picture, but is great to get rid of microstutters and keep everything fluid.

 

I use render ahead 3 and it cures micro stutters and lap times are unaffected, I don't feel any latency issues.

 

On my NVidia control panel, the default setting for max pre-rendered frames in VR is 1 and the application specific setting uses this global default setting (instead of "decided by application").

So I wonder, does changing the pre-rendered frames setting within AMS2 actually do anything (or those two are different things?)... Unless you change the value in the control panel too?

I didn't notice any difference in latency / feeling when I changed the value to 3 in game (can't say for sure did it smoothen things out either).

 

You need to change in NVidia Control Panel to aplication controlled or the desired frames ahead.

 

My laptimes are unaffected too, but I believe it's because I'm not good to latency matters anyway.

 

As long as you're running a decent frame rate the overall latency loop of input to eyeballs and back again for 3 frames is nothing. If you've got enough CPU/GPU overhead you won't even notice. TBH with the general inconsistency in VR it's very difficult to tell what tweaks make the difference just try one thing at a time and restart your PC between changes.

 

Has anyone been experiencing temporary loss of headset tracking while in the car since 1.6?

Just about every race that I've done with LFM and the CASS discord (so all online if that data point matters), my headset loses tracking at least once, tonight twice, where my VR view submarines down to the driver's feet and stays there for about 1 second and sometimes more. It has reset itself before but more often than not I have to recenter VR with the keybind.

I found out tonight that a fellow CASSonian has also been experiencing this, he is using the OpenComposite runtime while I'm native SteamVR, we have different headsets, we're not getting this loss of tracking in any other sims that we play, I have never had this happen in AMS2 before 1.6... so the only common denominator we came up with is the game itself. But admittedly, I'm too ignorant to how these things work technically so I may very well be missing something.

 

Hey all,

I received some complains about the pitstops from people who race in VR.
Meself race with a screen and I've got multiple buttons to use, so for me it isn't a big deal.
Setting up the strategies seems to work but execute them is the PITA.

Is there a way, some guideline or some button(s) to map and make life somewhat easier for VR people?
All Ideas and sharing experience is welcome.
Is it possible to map a strategy to a button instead of navigate trough the menu during driving?
Can the pitsystem be automated?
Example, the pitcrew sees what you need, fresh set of front tires, a splash of fuel and rear aero has to be fixed.
And they just do what needs to be done.

 

I use VoiceAttack, steep learning curve for me but well worth it. There is or was a voice pack you can get that confirmed your various requests.

 

Looking for sage advice on an issue with VR. I am using a meta quest 3 and pretty much have it cranked all the way up (120Hz etc), I'm also using an official link cable and my card is RTX4070ti. 32 gig of RAM. I really enjoy the karting in Automobilista 2 and graphics wise in VR it's almost there, it's sharp, good textures, great frame rate, but...when I look left and right the game throws up horrible noise filled fan shaped artefacts, coming upwards from the track which then stretch forward. They disappear when I face front again. This also happens across my vision at various points on the track, usually a bump etc. Does anyone know what is causing this? Does it only happen in karts? And is there a way to fix it?

 

Thanks, i'll try the camera settings

 

This is ASW working. I set graphics to never use ASW in open wheelers because of these crazy artifacts in really fast moving things.

 

When you test, I find the most crazy thing: setting NVidia driver to render ZERO frames ahead solves microstutters too.

 

I thought 1 was the lowest setting?

 

I do plan to, just finding keep thinking of more stuff to tweak (currently seeing if disabling hyperthreading does anything). Will probably come after the noise from the new ac game has died so it gets across to the more people

 

Interesting. So how do I disable it?

 

Ingame and in NVIDIA driver VR settings. But if you set in NVIDIA driver Low Latency settings to ULTRA, no frames in buffer. I believe it's overide VR settings.

 

You've probably seen this, but this guy already did the homework.

TLDR: If Intel chip, possible/probable benefits. If AMD chip, leave on default.

 

Tested disable SMT in my Ryzen 7 5800X. Like it, less FPS drops.

Set Low Latency Mode in NVIDIA Control Panel to ULTRA and VR pre rendered frames to aplication controlled.

In graphicsconfigoculusdx11 config file, set this:

<prop name="FrameLatency" framelatency="0" />

I believe I get rid of any pre rendered frame in VR, and with SMT off, stable FPS, best experience I had in this game.

 

I forgot to say that these settings I liked to race in daylight, no rain, because is really nice in open wheelers look around with the less latency possible. More demanding scenarios and ASW working I have the usual little sutters sometimes, and I go back to 3 frames ahead rendering. People with more powerful CPUs and GPUs can test more.

EDIT: with SMT off in BIOS, I can run with just 1 frame rendered ahead and zero stutters. My CPU usage goes high as 60-70% and GPU over 90%! I Never saw these numbers with SMT on. Much more fluid.