CPU Bottlenecking in MT and VR - possible Solution - worked for me!

[flyingcyrus]

2 hours ago, Leafcutter1008 said:

this is a very good explanation. So this means that every frps above 45 is useless in MR?

Actually, when activate MR, the engine spits up 45 fps at a constant pace, so you never see additional frames (unless your rig can achieve 90fps with MR on auto mode), so useless is not the appropriate term here. Think of it this way : the frames above 45fps (slightly above, cause computing the predicted frames take time) that the computer does not need to render are a power reservoir which can be used for other things like IA, weather etc.  

[flyingcyrus]

2 hours ago, Leafcutter1008 said:

There is a function in the Toolkit that allows you to lock the framerate either to 30 or to 45 I think. Could it be the clue to use this function?

MR does it automatically. Half the native headseat (i.e. 45fps for a 90Hz helmet) of 1/3 if it can't achieve half. Be aware that at 30fps, MR has to compute 2 predicted frames before displaying the next rendered frame. Smoothness is still here but at a price of some artefacts, especially during fast aircraft and/or head moves.

[Baldrick33]

Using the default OpenXR WMR runtime with my Reverb G1 I get the core 1 maxed out and stutters with motion reprojection on. Switching to rather OpenXR SteamVR runtime my overall CPU utilisation goes up and core 1 isn’t maxed but the others are at or near 100% and the stutters are gone.

Edited March 14, 2023 by Baldrick33

[YoYo]

1 hour ago, Glide said:

So, MR unlocked worked like a charm in the f-16 and I did not notice any rotor wobble in the ah-64 as I was struggling to get it airborne (something up with my controllers, I think).  This is because with my settings I can maintain 60fps in VR, so very low probability of bad prediction frames.

Another easy test, enable the OpenXR toolkit FPS counter.  With MR disabled, panning the headset back and forth, you will see double vision in the letters.  With MR enabled, it's perfect.

And jumping FPS :-).

[flyingcyrus]

14 hours ago, Baldrick33 said:

Using the default OpenXR WMR runtime with my Reverb G1 I get the core 1 maxed out and stutters with motion reprojection on. Switching to rather OpenXR SteamVR runtime my overall CPU utilisation goes up and core 1 isn’t maxed but the others are at or near 100% and the stutters are gone.

 

I noticed the same boost, even on MSFS ! I can now achieve a steaby 45 (90 reprojected) on sceneries where I struggle to get 30. Let's hope Microsoft is aware of this and keen to fix the issue, but according to their recent statements about VR, I 'm not optimistic :-/

[gwizdek]

VR is different story for everyone. WIth all the variables in place (PC hardware / HMD, personal preferences), it's next to impossible to recomend anything specific.

My guidelines (I have HP G2)

General:

- set Pixel Density to 1.0 and use SteamVR / OpenXR Tools for Windows Mixed Reality to set resolution (just to have one often forgotten variable less)

- opened OpenXR Toolkit overlay will lower your framerates. Set what you want and close it.

 

If you want image sharpness:

- dont use any MR

- use OpenXR

- use OpenXR Toolkit, enable CAS and set sharpness to 100%

- if you can handle slight flicker, you can use 60Hz HMD mode if your FPS are consistently above 60 (for smoothness). The flicker is less visible in dark enviroments, so adjust gamma or use OpenXR Toolkit filters/postprocessing

- if your FPS is in range of 45-60, use some software to cap FPS to constant 45FPS (I mean half refresh rate of your HMD). I recomend using Guru3D RTSS Rivatuner Statistics Server for it. This will reduce variable choppiness. Don't use OpenXR Toolkit FPS cap setting for it.

(in two above cases, any FPS headroom you have, you can use for better graphics settings in game)

- if you can't see max FOV your HMD can provide (head shape/ glasses), use OpenXR Toolkit FOV setting to reduce FOV as it will act like another supersampler (it will squeze pixels to your reduced FOV increasing sharpness)

 

 

 

Edited March 15, 2023 by gwizdek

[YoYo]

21 minutes ago, gwizdek said:

- if you can handle slight flicker, you can use 60Hz HMD mode if your FPS are consistently above 60 (for smoothness). The flicker is less visible in dark enviroments, so adjust gamma or use OpenXR Toolkit filters/postprocessing

Unfortunately, this is the basic problem for me. Rather, there is nothing to touch the gamma, it will be too dark. 60Hz works very nice and would be the Holy Grail, but unfortunately the flickering is too visible for me.

I hope they will fix StemVR + OpenVR soon , because for me it gives better visual effects (with Reshade) than OpenXR (with mbucchia's Toolkit) with the same performance.

[marbessi]

In my experience Motion Reprojection has helped a lot in smoothing frames but let your visor work at full refresh speed, in my case HP Reverb g2, was a lot better in dogfighting since you can avoid the "ghosting image" of fast object crossing your line of sight. It's not easy to achieve this in DCS and depends a lot on your hardware but also which kind of missions or modules you fly a lot. You have to trade your performance with quality. I think actually we have much more space to deal thanks to MT and more will come with  this tech refinements and Vulkan. In general is a very personal feel but if you can match full visor refresh speed with accetable graphic then you got the point.

Just in case my hardware is Ryzen 5 5600X, 3080, 32 gb RAM, HP Reverb G2.

[Marco Schaap]

21 hours ago, Leafcutter1008 said:

btw. in 2D I get fluent 180+ fps in MT....no stuttering at all, smooth as butter...

so it can´t be my computer or am I wrong...

You could be wrong. Comparing 2D to VR is not linear. 

[gorzasty]

In my case (MT version) there is very strange thing with stuttering. I set my settings in DCS to have much above 60fps. Turn 60Hz in my Reverb G2 (I hate reprojection) and what can I see in many missions? Stuttering like hell. But that is funny - OpenXR toolkit shows me that my render frametimes are below 10ms and CPU frametimes  - 3ms. Moreover OpenXR and DCS tool show steady 60fps, but stuttering is horrible - like 20fps. 

Good example is freeflight (instant action) MI-8 mission on Caucasus. Right after start statters start. 

Of course I did every repair and tried everything what I have found on this forum. It is still the same. 

 

Regular open beta is OK, but fps are lower and MP is not playable on larger servers due to the high frametimes - much above 15ms.  

 

[Baldrick33]

17 minutes ago, gorzasty said:

Of course I did every repair and tried everything what I have found on this forum. It is still the same. 

 

You may have said this already but have you tried SteamVR as the OpenXR runtime?

[gorzasty]

1 hour ago, Baldrick33 said:

You may have said this already but have you tried SteamVR as the OpenXR runtime?

Yes, SteamVR and OpenXR.

But... I have found the problem in my case! 

Solution for my problem was to disable a V-Sync. After that all the stuttering has gone.   

 

[ChariotOfFLAME]

On 3/14/2023 at 10:24 AM, BIGNEWY said:

No worries, it does not suit everyone for sure and will depend on your hardware. I have never liked using motion smoothing, but I always tweak my settings to get 45fps minimum in VR and now getting much higher.

I'm just curious what settings you are running these days!