VR Discussions, Questions & Feedback

i think this is a new bug. happened to me too

 

its very annoying in multi as it accompanies a stutter, just click on the above

 

Have you noticed a drop in performance with patch 1.6.3.1, especially in the rain?
I did the LMF LMP2 race in the rain before the patch and no problems to report at constant 90fps. Last night the same race, I was at 60 fps. No parameters were affected however.

 

Its pretty much Hockenheim as a track. Since it was released I had very bad performance on this track, especially going into the night. Hasn't improved ever since.
Sebring, Road Atlanta and some other tracks are running so much better under those circumstances for me. Another system-heavy example that easily tanks performance is Kansai (Suzuka), if it hasn't changed recently.

 

Could this be caused by overloaded servers?

 

I tried a dry run again. So it's my CPU that is overloaded. Amazing I didn't have any of these problems before.

 

Just curious guys; have any of you micro stutter in VR?
Read a lot about it when I got my headset (just plane WMR, Lenovo Explorer) and it seemed a thing of Nvidia.
Just a handful of times per lap, sometimes more, just a small stutter even if the VGA runs it perfectly.

Back then I learned I had to use a specific driver and always did. About a month ago, I tried a newer one/the newest: stutter back! So, that is not solved by Nvidia......

I read nothing about it in the topic: are you all just using that same driver or don't you have that problem?
As I was thinking, and the bunch of posts on the internet I read, everyone had it......

This goes for all games btw, not just AMS or even racing games for that matter.

 

Too high bitrates can cause those cracks and pops with Quest headsets.

Edit. Can confirm that happens also on Reverb g2...

 

I have updated today to the newest Nvidia Driver and got those micro stutters in my Quest 3. So I will go back to 560.94 tomorrow. This version worked better for me. Still trying to find the best settings, because I also got less FPS since 1.6.

Had 3 online races today with heavy stutters from time to time. Headroom was more than 50% CPU and 20% GPU, so I think this was a connection issue.

 

Seeing something weird on straights where the grass is being "thrown up" just before you pass that section of track. Anyone else? I'm seeing this at Interlagos 1993 don't know about other tracks.

Also, I see the lollipop guys are still out on the main straight. lolz

Performance is worse that prior to the update. Anyone gotten this back to where they had it and likes it with a similar rig open to share their settings: RTX4070, an i5 10400f and 16gb of ram using Link cable and Quest 3. . . . . Quest link app settings, debug tool, nvidia control panel/drivers, and in-game? I feel like I'm chasing smoke.

 

I will have an update to my vr guide for the quest 3 out today so maube take a look and see if anything there will help

 

Have you disabled HAGS(Enable Hardware Accelerated GPU Scheduling) from the Windows settings? HAGS can cause stutters in VR.

 

I have installed the Latest nvidia drivers, it runs butter smooth. Steady 90fps.

 

Thanks for the responses guys.
It seems the stutter problem is not there for everyone; that's nice, (for you! )

@mikesch250
I didn't try all the drivers back then, but for me it was 516.59, read that somewhere and it worked for me. Good to know another version works too, now those older drivers are getting harder to come by.
What you say about the headroom: I was looking for answers back then and tested a lot: it seemed to me, that the stutter was even more with more headroom; weird, right?

@ulotrix
Indeed I have that shut off, yes.
Did try it On for a moment, again, "back in the day" but it didn't seem to do anything.

Fact: the stutter problem I had was on my old pc ánd on my new system. Everything completely new, even used another wall socket, same.
Different VGA (but: Nvidia) same.......

 

Thanks. I will drop bitrate, I’m currently running it at 960. Quick noob question but what does this setting do? Does this have performance impact? and what would a good setting be?

thanks

 

It basically impacts the image quality. Since quest headsets doesnt support native image through displayport, PC has to encode the image and Quest decodes it. Bitrate is the amount of sent data. Higher bitrate is better quality, but can induce more latency and also these sound pops and cracks. When i had Quest 3 i used bitrate of 750mpbs. I found that to be the sweetspot.

In this case the audio pops are happening also on my reverb g2 which doesnt rely on streaming. That makes me believe that the issue in this case is the game, but obviously it doesnt hurt to try lower bitrates.

 

One final thing…….I have most settings on high and I am generally happy with my lot but only one thing still not quite right and that is that when I am behind a car (I predominantly race GT3) they don’t seem to have a good connection between tyre and track. As I said I have shadows at high and most other settings at high. This is just a visual thing but it was definitely better before

Any advice appreciated
Thanks

 

Thanks for your reply. I will try 750

Thanks again

 

talking about stutters...
I have focused my Gaming on desktop since v1.6 came update to tune the FFB on my wheel.

Today I have played for the 1st time in VR, for convenience, I have done my testing on a wireless Q2.
I will run the same with a link cable later then on my PSVR2 but the experience is now really bad compared to prior update.
I am getting stutters in any weather or daytime conditions.I do monitor performance via the FPSVR tool and what I have noticed is that the CPU frametimes that were in the 3 to 4ms range, and butter smooth gaming experience, are now doubled and I see the "orange" spikes on the graph continuously.

I am running a 4080S and 5800X3D so high level HW, on NVIDIA 566.14 drivers.

I have not changed any settings in the Meta app (max resolution possible, 120Hz) and also same parameters in ODT

all my graphics settings in Game remain the same (High) and I am using SMAA ULTRA

any advice appreciated because this is unplayable right now