Huge performance drop when switching from Rift S to Quest 3

[DST]

I recently got a Quest 3 and tried yesterday for the first time DCS via link cable and was truly shocked about the stuttery mess DCS became, before I had a Rift S and buttersmooth performance all over the place, really didn't expect it to be THAT bad. Even with DLSS enabled and graphic details on low-middle I have stutters when flying low in helicopter on and empty map. Supersampling via Oculus Tray Tool is 1.0, ASW on, and PD in DCS also 1.0

I don't use "Open XR Toolkit", as I it never seemed necessary because performance was very good lately with Rift S, is this maybe recommended now? 

Has someone here maybe had similar problems when changing from Rift S to Quest 3? 

I can also say that I have installed the "Oculus Game Optimizer" on the Quest 3, is it possible that this thing interferes with the performance when the headset is linked to the PC, as it forces the headset to a higher resolution and framerate? 

My specs:

RTX 3080

Ryzen 78003XD

64 GB DDR5

Any suggestions would be appreciated, the fact that lowering graphic details or Supersampling via OTT below even 1.0 doesn't kill the stutters seem to indicate a more general problem here.

Thanks in advance 

[Maddaawg]

For troubleshooting, use the VR preset. Save your current settings to one of the 3 custom spots so you can come back. The Rift S has much less resolution, so your pushing more pixels. Set your refresh rate to 72hz too.

My GPU is a step up from yours but my CPU is several steps below yours. I however use VD and find it to work better than Meta and the USB cable or WiFi link.

I've had to lower my settings as compared to the G2 I had. I really think DP connections are best and my next HMD will have one.

[BIGNEWY]

55 minutes ago, DST said:

I recently got a Quest 3 and tried yesterday for the first time DCS via link cable and was truly shocked about the stuttery mess DCS became, before I had a Rift S and buttersmooth performance all over the place, really didn't expect it to be THAT bad. Even with DLSS enabled and graphic details on low-middle I have stutters when flying low in helicopter on and empty map. Supersampling via Oculus Tray Tool is 1.0, ASW on, and PD in DCS also 1.0

I don't use "Open XR Toolkit", as I it never seemed necessary because performance was very good lately with Rift S, is this maybe recommended now? 

Has someone here maybe had similar problems when changing from Rift S to Quest 3? 

I can also say that I have installed the "Oculus Game Optimizer" on the Quest 3, is it possible that this thing interferes with the performance when the headset is linked to the PC, as it forces the headset to a higher resolution and framerate? 

My specs:

RTX 3080

Ryzen 78003XD

64 GB DDR5

Any suggestions would be appreciated, the fact that lowering graphic details or Supersampling via OTT below even 1.0 doesn't kill the stutters seem to indicate a more general problem here.

Thanks in advance 

Its worth remembering there is a difference in resolution so I would expect some drop in performance if you kept the DCS settings the same. 

• 2.47x higher resolution
  Quest 3 4416 x 2064 px vs Rift S 2560 x 1440 px
  
  you may need to tweak your settings a little to find the sweet spot again. 

[DST]

Thank you.

Yes I know about the higher resolution, but what would be the most obvious thing to do in this case? I already tried to lower Supersampling in Oculus Tray Tool below 1.0, it looked far worse this way than with the Rift S and I still had stutters all over the place.

Also the guy in this video below here has far higher graphics settings and pixel density than I have, and claims to have the needed 72 fps all the time, even in multiplayer. Ok he has the 3080ti, but is this really such a big gap? 

I really feel like there something totally off besides graphics settings, and I'm not able to pinpoint to it.

38 minutes ago, Maddaawg said:

For troubleshooting, use the VR preset. Save your current settings to one of the 3 custom spots so you can come back. The Rift S has much less resolution, so your pushing more pixels. Set your refresh rate to 72hz too.

My GPU is a step up from yours but my CPU is several steps below yours. I however use VD and find it to work better than Meta and the USB cable or WiFi link.

I've had to lower my settings as compared to the G2 I had. I really think DP connections are best and my next HMD will have one.

Thanks for suggestions.

What is VD? 

[BIGNEWY]

Can you attach your dcs log, we can take a closer look at your options, maybe suggest some tweaks

thank you 

[DST]

Yes I will try to do this.

I just looked into my "logs" folder under "user, saved games, dcs, etc.", and there like 100 files in it, which one is the correct one?

[DST]

There is only 1 file in logs folder, that is created today, is this the correct one?

dcs.log.old

There is also this text file from today, sorry for confusion, but I´m really not sure which one is the right one

dcs.log

Okay seems to be the second one

Edited November 12, 2024 by DST

[BIGNEWY]

Thank you 

the old log is just the previous log from the most recent dcs.log, both are fine. 

Your settings seem pretty good, only thing I would disable is civil traffic.

It maybe worth deleting your metashader2 and fxo folders in saved games DCS and allowing DCS to create new ones when it restarts. 

 

[DST]

Yes thanks, I always delete metashaders and fxo folders regularly. Also also lowered graphic settings to the very minimum and there are still lots of stutters compared to the silky smooth experience i had with the Rift S. Guess I have to live with it or get a new graphics card. 

[Qcumber]

6 minutes ago, DST said:

Yes thanks, I always delete metashaders and fxo folders regularly. Also also lowered graphic settings to the very minimum and there are still lots of stutters compared to the silky smooth experience i had with the Rift S. Guess I have to live with it or get a new graphics card. 

I have both the rift s and Quest Pro. I previously owned a Pico 4 which has the same resolution to a Q3. You should be able to run a Q3 OK on a 3080 but with compromises. I can suggest some starter settings if that would help. 

[Lange_666]

Also give OpenXR toolkit a try, just set the Turbo Mode to ON and see if you get any less stuttering.

[DST]

12 minutes ago, Qcumber said:

I have both the rift s and Quest Pro. I previously owned a Pico 4 which has the same resolution to a Q3. You should be able to run a Q3 OK on a 3080 but with compromises. I can suggest some starter settings if that would help. 

Yes thank you suggestions are always welcome. But as previously mentioned, I already tinkered around with graphics settings in DCS, nothing seems to have an effect at all, even with lowest setting it´s still not as smooth as with Rift S.

[DST]

8 minutes ago, Lange_666 said:

Also give OpenXR toolkit a try, just set the Turbo Mode to ON and see if you get any less stuttering.

I will try this, I guess I have to use the "Start with OPEN XR" option on steam to get this working? I just downloaded and installed the program (never used this before), so this program runs in the background and how exactly do I start this "Turbo Mode"?

[Phantom711]

@DST

Wait…what? Are you running via SteamVR the whole time?

Cut the crap! Just use QuestLink, set this as your OpenXR runtime and start DCS.

[DST]

4 minutes ago, Phantom711 said:

@DST

Wait…what? Are you running via SteamVR the whole time?

Cut the crap! Just use QuestLink, set this as your OpenXR runtime and start DCS.

No, I'm running this with via steam but not with Steam VR. Only with Meta Link app running. I have the two options "start with oculus vr" & "start with OpenXR" when doubleclick DCS in steam library. With both options I see no difference in performance. I disabled the DCS launcher.

[Phantom711]

@DST

To be honest, I have no idea how the Steam version of DCS behaves exactly. In any case use I recommend you use the „start with OpenXR“ option.

As for the openxr toolkit. You can start the exe and change the keybinds to operate it. Instead of the F1-F4 keys I changed it to the arrows. Just for convenience. 
Once you are in the game, just press CTRL+down and the toolkit window appears and you can change settings. Some might need you to restart the game though.

[Qcumber]

44 minutes ago, DST said:

Yes thank you suggestions are always welcome. But as previously mentioned, I already tinkered around with graphics settings in DCS, nothing seems to have an effect at all, even with lowest setting it´s still not as smooth as with Rift S.

I would start by making sure you have optimal settings with meta link. Inactivate any open XR layers or mods. The meta link app defaults to x1 resolution which is not the full native resolution of the headset for some reason. Set the slider to 1.5 and see how the resolution looks. From that baseline you can start to adjust for performance. With your setup you will probably need to settle for 72 Hz with reprojection most of the time at moderate DCS settings. 

The next thing to try is Quad View Foveated Rendering. Try this at default fixed foveated settings and see how it looks. Leave turbo mode enabled as this might help smooth things out. 

Are you using default meta settings? If so then next thing to try is to use Open XR toolkit to adjust the bitrate. I can manage up to 960 Mbps but some people have problems this high so try about 500. You can also reduce the rendered FOV to about 0.92x0.92 which saves a bit of performance. 

Can you post a screen shot with the DCS with the FPS/frame time overlay so we can see what it looks like when you get stutters. 

Edited November 12, 2024 by Qcumber

[DST]

9 minutes ago, Qcumber said:

I would start by making sure you have optimal settings with meta link. Inactivate any open XR layers or mods. The meta link app defaults to x1 resolution which is not the full native resolution of the headset for some reason. Set the slider to 1.5 and see how the resolution looks. From that baseline you can start to adjust for performance. With your setup you will probably need to settle for 72 Hz with reprojection most of the time at moderate DCS settings. 

The next thing to try is Quad View Foveated Rendering. Try this at default fixed foveated settings and see how it looks. Leave turbo mode enabled as this might help smooth things out. 

Are you using default meta settings? If so then next thing to try is to use Open XR toolkit to adjust the bitrate. I can manage up to 960 Mbps but some people have problems this high so try about 500. You can also reduce the rendered FOV to about 0.92x0.92 which saves a bit of performance. 

Can you post a screen shot with the DCS with the FPS/frame time overlay so we can see what it looks like when you get stutters. 

 

Thank you for suggestions I will try and figure this out. 

What do mean with "quad view foveated rendering"? The Quest 3 does not have any eye tracking features I think? 

[Ala12Rv-Tundra]

cable settings bandwith?

[Qcumber]

7 minutes ago, DST said:

Thank you for suggestions I will try and figure this out. 

What do mean with "quad view foveated rendering"? The Quest 3 does not have any eye tracking features I think? 

QVFR also works in fixed foveated mode. This means that peripheral vision is reduced. This can be set so it is less noticeable but gives you a significant performance boost. It offsets some processing from GPU to CPU. As you have a lot of CPU room it could make a big difference. 

1 minute ago, Ala12Rv-Tundra said:

cable settings bandwith?

Yes. Everything above assumes you (op) are using a decent cable which meets the meta link minimum requirements. 

[Lange_666]

2 hours ago, DST said:

I will try this, I guess I have to use the "Start with OPEN XR" option on steam to get this working? I just downloaded and installed the program (never used this before), so this program runs in the background and how exactly do I start this "Turbo Mode"?

If you run in OpenXR and have OpenXR Toolkit installed you can bring the Toolkit settings menu up when you are in DCS VR through the keyboard combo you can set if you open the program on your desktop.
null
In this case it's CTRL+ALT+Down Arrow to bring the menu up in VR. Then use the arrow keys to go through the menu.
You'll find Turbo mode on the first page.

[Maddaawg]

6 hours ago, Qcumber said:

Set the slider to 1.5 and see how the resolution looks. From that baseline you can start to adjust for performance. With your setup you will probably need to settle for 72 Hz

The Quest 3 is 1.3 PD at 72Hz with slider to the far right.

10 hours ago, DST said:

What is VD?

Virtual Desktop, a WiFi only way to run without using the Meta app.

7 hours ago, DST said:

I'm running this with via steam but not with Steam VR. Only with Meta Link app running.

Personally, I would ditch Steam and run DCS natively. You can move any mod licenses one way though to ED.

[Lange_666]

9 hours ago, Maddaawg said:

Virtual Desktop, a WiFi only way to run without using the Meta app.

VD can be used fine with a link cable.

[Qcumber]

41 minutes ago, Lange_666 said:

VD can be used fine with a link cable.

That is not officially supported by VD. 

[Lange_666]

But it does work so why not using it?