Horrible VR Stuttering (Quest 2)

[mcplane]

I have recently upgraded my PC so that I can run DCS world in VR. However, whenever I'm running the game, right as I spawn in I get horrible stutters in multiplayer specifically. Sometimes GPU usage touches 100% (See video) but the more unusual thing is the cpu usage usually hits 100. The video I took shows some of the glitchiness. It's pretty much unplayable. I've tried reinstalling the oculus app, done graphics driver updates, turned on and off dev mode, tried a new link cable, tried reducing graphics settings etc. The vr 'mirror' on my display never glitches like I see in the headset. 

 

As an update, I lowered settings so none of my resources were even near 100%, and the headset still struggles with stuttering. And I haven't found another game that does this. Normally I get okay performance in single player, with occasional glitches as shown in said video.

 

Specs: Quest 2/Win10/i7-9700K/RTX3070ti/64GB DDR4 Ram/1TB Nvme ssd/Oculus Link Cable (USB-C)

 

Stutter shown here:

 https://www.youtube.com/shorts/BpkFULgqiNo 

 

null

Edited August 12, 2022 by mcplane

[stormrider2]

Reduce your preload by half and try again.

Edited August 12, 2022 by stormrider2

[taikoJH]

Take look here. Maybe that helps

 

[mcplane]

11 hours ago, stormrider2 said:

Reduce your preload by half and try again.

 

Just gave this a try, no dice.

 

 

2 hours ago, taikoJH said:

Take look here. Maybe that helps

 

I wasn't able to find the right tab in win10. I have my drivers up to date, but there is no troubleshooting tab.

[stormrider2]

Have you tried repairing your DCS installation?

I used to play with a 1070ti that worked great, even in VR. I upgraded to a 3080 and soon after, during my first attempt, it stuttered a lot and I saw a lot of pixelization around the MSAA mask. I shut DCS off and did a full repair and yeah, it found some old files from some old mods that I didn't even remember having and immediately it was a completely different experience, worthy of a 3080.

Edited August 12, 2022 by stormrider2

[mcplane]

After lowering settings significantly, I still get issues. These are the resource percentages.

1 minute ago, stormrider2 said:

Have you tried repairing your DCS installation?

I used to play with a 1070ti that worked great, even in VR. I upgraded to a 3080 and soon after, during my first attempt, it stuttered a lot and I saw a lot of pixelization around the MSAA mask. I shut DCS off and did a full repair and yeah, it found some old files from some old mods that I didn't even remember having and immediately it was a completely different experience, worth of a 3080.

I'll give that a try 

Edited August 12, 2022 by mcplane

[stormrider2]

7 minutes ago, mcplane said:

Just gave this a try, no dice.

 

 

I wasn't able to find the right tab in win10. I have my drivers up to date, but there is no troubleshooting tab.

The HAGS in Win10 you will find in:

Start > Type in: Graphics settings > Switch Hardware-accelerated GPU scheduling to off.

Edited August 12, 2022 by stormrider2

[mcplane]

5 minutes ago, stormrider2 said:

The HAGS in Win10 you will find in:

Start > Type in: Graphics settings > Switch Hardware-accelerated GPU scheduling to off.

 

Ahh thank you. Upon looking at it, it was already turned off

[stormrider2]

14 minutes ago, mcplane said:

Ahh thank you. Upon looking at it, it was already turned off

What version of the Oculus software are you using? Some people reported stuttering with latest v43 or something.

 

Edited August 12, 2022 by stormrider2

[mcplane]

21 minutes ago, stormrider2 said:

What version of the Oculus software are you using? Some people reported stuttering with latest v43 or something.

 

 

I think it is v43 unfortunately. Sounds a lot like my issue too. I think my oculus updated before I upgraded my hardware, so I'm not sure how to roll back that update. 

 

EDIT: I lied. The app version is still 42.0.0xxxx

 

Edited August 12, 2022 by mcplane

[mcplane]

Repairs just finished, and I am still having the same issues. Very strange

[KoN]

It's the quest2 headset . 

Go into the app and set to ,72hz move slider recommend. 

Start DCS . See if glitch has gone . 

Move slider up to 1.2 . Test . 

[mcplane]

On 8/22/2022 at 7:30 PM, KoN said:

It's the quest2 headset . 

Go into the app and set to ,72hz move slider recommend. 

Start DCS . See if glitch has gone . 

Move slider up to 1.2 . Test . 

I'll give this a try. I've been on 72hz and the recommended resolution from the oculus app. Haven't tried the slider in DCS though.

[KoN]

17 hours ago, mcplane said:

I'll give this a try. I've been on 72hz and the recommended resolution from the oculus app. Haven't tried the slider in DCS though.

Also try OTT and set ASW @ 30hz . 

[Moxica]

I have a fairly similar rig. It runs like butter with higher graphic settings than the picture.
I don't use cable, just air link.
I use default/recommended frequency setting
I have made an exception in windows defender for all dcs folder
I do NOT use OTT
Sometimes George's response is put in line, causing stutter until he responds "target destroyed" way to late.
I sometimes get horrible stutters. I solve it by pressing esc, and alt tab to another window. Then repeat back to DCS, and the stutter is gone.
These seem to be triggered by some in-mission script, mods or AI trying to get into the single core beeing used. And there's a line.   
Alt-Tab has been a magic wand for me.
 

Edited August 29, 2022 by Moxica

[dutchili]

Stutters seem to be caused by delays in network operations, either 'to the internet' or between PC and headset.
For internet: check your ping to the server (in the multiplayer screen). Forget anything above 100 ms. Also, the more users on a server the more data that must be transferred. Above 10 users per server you will usually see worse performance

 

Between PC and headset: the oculus app can check the actual performance. Not every USB-C cable is a fast cable.

 

As for the game and Oculus settings:

- shadows on Low will help you

- water on low  will help you

- Clouds on Low will help you

- Ansitropic filtering: just turn it off

- On the VR tab: set Pixel density to 1.5 for your pc

- set resolution in the Oculus App to 0.8 for your pc
   Of course you want the highest possible resolution, but I've found that lowering this setting instead of increasing it, will give you better game performance and a smoother picture. Unfortunately the super scaling is done by the GPU and not one of your 'i have nothing to do' cpu cores.

- In Oculus Debug Tool i have set Link Sharpening to TRUE, to increase the crispyness of the picture.

 

This should give you 36 FPS @ 72hz as a minimum, which is good enough in VR, even in multiplayer.
(syria map: 20 fps on the ground, 36 above 5000 ft)

 

I do like the graphics more with PD set to 1.8 and Oculus Resolution set to 1.3, however, that will not work if there is any scripting going on or multiplayer gaming.

[DuRiN]

Hi there, @mcplane!

i have similar problem starting before summer. I have Valve Index and Quest 2 and a RTX 2080 SUPER with AMD 5600x and 32Gb of RAM. Both in single player and multiplayer and with Airlink and oculus lInk i can start a mission with very good fps values in my Quest 2 but after a while, the games have a sudden loss of fps from 45 to 14 or similar. Sometimes i can solve switiching to another window but sometimes i can not recover normal frames.

 

When this happens i go to task administrator in W10 and see that GPU load is at 100%...when it recovers itself, it gets under 100%. Then i go back to the game and 45 are back. I have tested all the solutions given in this thread (and a lot of more solutuons)...

 

With Index and the same environment i have solid fps and no sudden loss of frames so i have a main conclusion that is that it happens when the Quest 2 gets a temperature that makes the HMD get into a throttle state, lowering the performance and generating loss of frames.

No solution for you from my side but i will keep trying because Q2 are better in image quality than Index and more confortable with BoboVR strap (only sound is worst)

 

[mcplane]

On 8/29/2022 at 11:22 AM, DuRiN said:

Hi there, @mcplane!

i have similar problem starting before summer. I have Valve Index and Quest 2 and a RTX 2080 SUPER with AMD 5600x and 32Gb of RAM. Both in single player and multiplayer and with Airlink and oculus lInk i can start a mission with very good fps values in my Quest 2 but after a while, the games have a sudden loss of fps from 45 to 14 or similar. Sometimes i can solve switiching to another window but sometimes i can not recover normal frames.

 

When this happens i go to task administrator in W10 and see that GPU load is at 100%...when it recovers itself, it gets under 100%. Then i go back to the game and 45 are back. I have tested all the solutions given in this thread (and a lot of more solutuons)...

 

With Index and the same environment i have solid fps and no sudden loss of frames so i have a main conclusion that is that it happens when the Quest 2 gets a temperature that makes the HMD get into a throttle state, lowering the performance and generating loss of frames.

No solution for you from my side but i will keep trying because Q2 are better in image quality than Index and more confortable with BoboVR strap (only sound is worst)

 

Hey there. I'm sorry to hear you've also run into the same set of issues. My solution was to buy a new headset. The HP Reverb G2 has been amazing for the short time I've had it. And it just is so much clearer and crisper. It felt like putting on glasses for the first time! I'm sorry to say this was my only solution I found to the problem.

[Midair]

I have the exact same problem with my Quest 2 and link cable. I have set it to run at 90HZ and locked it to 30HZ on the OTT. I use the recommend resolution and no super sampling on OTT, I also have enable the sharpening on the OTT and the birate is set to 300. The image is crystal clear and the FPS are locked at a constant 30 fps but sometimes I have horrible stutters and the alt-tab solution help to be smooth again (not every time). The worse for me is when I fly on the Enigma server fast and low after 20 or 30 minutes the stuttering start. I test it on the Blue Flag Modern server and it remain smooth for 2 hours on my F16, it began to stutter when I land at Beslan but the Alt-Tab solved it. 

I really don't know where this problem come from and how to solve it.

[Dantagonistic]

On 8/29/2022 at 12:47 PM, Moxica said:

I have a fairly similar rig. It runs like butter with higher graphic settings than the picture.
I don't use cable, just air link.
I use default/recommended frequency setting
I have made an exception in windows defender for all dcs folder
I do NOT use OTT
Sometimes George's response is put in line, causing stutter until he responds "target destroyed" way to late.
I sometimes get horrible stutters. I solve it by pressing esc, and alt tab to another window. Then repeat back to DCS, and the stutter is gone.
These seem to be triggered by some in-mission script, mods or AI trying to get into the single core beeing used. And there's a line.   
Alt-Tab has been a magic wand for me.
 

 

Same issue for me including the alt-tab fix. I'm using a Rift S rather than the Quest though.

[Midair]

I manage to have a more stable experience. I set the Headset to 90HZ and put a maximum limit of 30 fps on the NVidia panel. I disabled the ASW via DebugTool and put the bitrate at 300. I'm now able to fly for hours on Blue Flag server without stuttering but on Enigma server it's less effective and I have a lot of stuttering near the frontline especially on the Caucasus scenario (I think it's a server or mission problem, to big for VR players).

Edited September 26, 2022 by Midair

[KoN]

Have any of you tried VRperfKit . add these files into game BIN folder and enjoy . Or use Openxr . 

[funkster]

DCS VR is pretty abysmal in terms of performance - You can throw all the hardware at it in the world ...even 4090s (see threads in this forum) ....but until the fabled MC and possibly Vulcan don't expect much.

Edited November 7, 2022 by funkster

[demolspeed]

Hi everybody!

I have a quest 2, and I have been experimeting the shuttering problem in cockpit.

The problem is "caused" by the ASW from Meta. ASW locks frame rate to the half of Hz and generates an extra frame so you just need to get 45 FPS for getting 90 FPS. ASW is activated when the system can't achive the Hz configurated for the quest, for example if you configure the quest for 90Hz and (in real time) your system can't get 90 FPS, the the driver activates ASW and locks frame rate to 45.

That is very good for the most of games, including race simulators. But... one of the problems with the ASW is with the traslation movements of the head. Rotating works good but traslating the head, can make shuttering, if you have an object near... and this object is the cockpit. We do need a perfect precision for manipuilating the aircraft systems.

So if your are flying a simulator you can enjoy with the view going fast and rotating the head without any problem, but when you down the look and try to manipulate the instruments, all the cockpit is awfully shuttering .

So we can conclude that ASW is not working with lateral head movements. And on the other hand, we have just a PERFORMANCE problem, that has been hided by ASW.

We can read FPS with MSI and can see that we get just 45 FPS this is because ASW is activated. If we deactivate it, with Oculus Tray Tool, for example, the we can see the REAL FPS. FPS must be around 70/80 I mean, bellow 90, this is ther reason because ASW was activated, and now we can configure our system to get the REAL desired FPS. 

Other systems, except Oculus and Vive hasn't any software of this kind, This is the reason why with Reberb2 we don't experiment this problems. If we deactivete ASW Quest2 operate exactly like other hardware.