VR - MT very poor Performance and stutters

[T-Pap]

Have spent 2+ hours running tests back and forth between normal and MT mode.

MT mode provides no performance boost . 

Excessive micro stuttering , very slow loading speeds between menus pre-game and load into game starts with most terrain , textures and lighting loading in steps.

On average based on oculus performance tray and Nvidia Performance tool , MT runs at 4-6fps less than normal mode without accounting for the constatnt micro stutters. 

System specs

CPU : i5 - 9600k (6core) running @ 4200Mhz 
32GB RAM @ 3200Mhz
GPU : Asus RTX 2060 Super 8GB
Dedicared M2 drive for DCS
VR : Oculus CV1 and Oculus Quest 1 - Set to default settings , NO supersampling etc .

Thanks


 

[Flappie]

This thread might pique your interest:

Another possible issue is an "eco" power plan assigned to your "bin-mt/DCS.exe" program. Ensure Windows runs it with a normal or high performance power plan.

[fab.13]

Hello,

Be careful that MT Version now use OpenXR API for Occulus headset ( command line flag not working anymore in MT version )

So comparison is very confusing with the forced introduction of OpenXR


Question : What API are you using in ST version ?
( shortcut command flag or DCS log say that )


 

Edited March 13, 2023 by fab.13

[Voodooflies]

23 hours ago, T-Pap said:

Have spent 2+ hours running tests back and forth between normal and MT mode.

MT mode provides no performance boost . 

Excessive micro stuttering , very slow loading speeds between menus pre-game and load into game starts with most terrain , textures and lighting loading in steps.

On average based on oculus performance tray and Nvidia Performance tool , MT runs at 4-6fps less than normal mode without accounting for the constatnt micro stutters. 

System specs

CPU : i5 - 9600k (6core) running @ 4200Mhz 
32GB RAM @ 3200Mhz
GPU : Asus RTX 2060 Super 8GB
Dedicared M2 drive for DCS
VR : Oculus CV1 and Oculus Quest 1 - Set to default settings , NO supersampling etc .

Thanks


 

Exact same issue, worst performance on VR here, which became from playable to unplayable. 

I run an Oculus Rift S on an RTX 2080Ti.

[T-Pap]

On 3/13/2023 at 2:03 AM, Flappie said:

This thread might pique your interest:

Another possible issue is an "eco" power plan assigned to your "bin-mt/DCS.exe" program. Ensure Windows runs it with a normal or high performance power plan.

Thanks , I always have DCS on performance and high priority .Also ran a repair as i saw in another post etc but the issue remains. I believe it might have something to do with oculus headsets though as i have noticed the majority of people not seeing any improvement use oculus.

11 hours ago, Voodooflies said:

Exact same issue, worst performance on VR here, which became from playable to unplayable. 

I run an Oculus Rift S on an RTX 2080Ti.

Yeah im on oculus aswell , both Quest 1 and CV1(Which should show even a basic improvement being lower spec)

14 hours ago, fab.13 said:

Hello,

Be careful that MT Version now use OpenXR API for Occulus headset ( command line flag not working anymore in MT version )

So comparison is very confusing with the forced introduction of OpenXR


Question : What API are you using in ST version ?
( shortcut command flag or DCS log say that )


 

 

Oculus runs by default OpenXR as API . Also tried running via Skatezillas launcher where you can switch the API but the performance issue remains. 

[backspace340]

Try reducing pixel density - I noticed that I could reduce the PD to 0.6 in DCS VR settings on OpenXR and suffer no loss of visual fidelity. I think OpenXR was pushing a lot more pixels than I had before in SteamVR (when I had PD for both at 1.0), and if the same is true on Oculus that could explain the drop in performance.

Edited March 14, 2023 by backspace340

[T-Pap]

22 hours ago, backspace340 said:

Try reducing pixel density - I noticed that I could reduce the PD to 0.6 in DCS VR settings on OpenXR and suffer no loss of visual fidelity. I think OpenXR was pushing a lot more pixels than I had before in SteamVR (when I had PD for both at 1.0), and if the same is true on Oculus that could explain the drop in performance.

 

I use standalone.
Reducing pixel density would be completely pointless considering multithreading is to enhance performance .
MT does not affect visually , it is not a graphical enhancement. Its point is to allow the same settings you already have to peform at a higher fps and therefor allow settings to go higher without loss of fps from your original fps , not the opposite , needing to reduce pixel density

[backspace340]

2 hours ago, T-Pap said:

I use standalone.
Reducing pixel density would be completely pointless considering multithreading is to enhance performance .
MT does not affect visually , it is not a graphical enhancement. Its point is to allow the same settings you already have to peform at a higher fps and therefor allow settings to go higher without loss of fps from your original fps , not the opposite , needing to reduce pixel density

The MT exe is forcing everyone onto OpenXR, even if you were previously using SteamVR (which works with standalone) or on Oculus's OpenVR equivalent. Switching to OpenXR from OpenVR (SteamVR) changed the default settings for what resolution to send to the headset for me - to get the exact same visuals on OpenXR that I was getting in OpenVR, I had to drop the PD to 0.6. I switched to OpenXR on the previous patch, but on a side by side comparison with OpenVR I had 60fps and OpenXR I had 30fps, until I reduced the pixel density to equalise the resolution between the two. So it's possible what you're seeing is entirely unrelated to the MT change, but caused by the forced switch to OpenXR (it might not be, but I had a performance issue from the switch to OpenXR that I've solved as I've explained).

[Voodooflies]

On my end, I did reset my Nvidia panel and Oculus Tray Tool settings and it fixed my issue.

I'm also using a PD of 1.0 in game and 1.3 on Oculus Tray Tool.

If that helps...