Hunting for the stutter-free VR experience.

[Panzerlang]

Ha, there's a new BIOS for my mobo. Currently on F13, F15 available. Doing that now (if the auto thing works but knowing Gigabyte my BIOS is about to light up like a halloween sparkler).

[Panzerlang]

BIOS done. That was suspiciously easy; used to be you needed a USB stick and a box of Black Magic.

[Special K]

No, these settings are all Windows. Do NOT disable any cores, do NOT use Process Lasso anymore on Win11. The MT stuff is running quite well now without.

 

[Panzerlang]

Game Mode disables That was on, I've switched it off.
Hardware Accelerated GPU Scheduling disabled That was already off.

Roger that on Process Lasso. I'll look up Core Isolation and Core parking and get it done. Thanks SK.

 

[Panzerlang]

Core Isolation was already off, I've just done the registry edit to unpark the cores.

 

[Special K]

Looking at your dcs.log there is a bit more to do:

- Turn off SSLR.
- Turn off SSAO.
- Disable civil traffic.

These are expensive things. Delete Saved Games\DCS\fxo and metashaders2 also.
And increase your pagefile. You want at least 32, better 48+ GB on your fastest drive. Only one pagefile please.

[Moxica]

I sure hope there are some obvious errors in these, because I'm at an end here..

DxDiag.txt dcs.log

[gonvise]

40 minutes ago, Special K said:

Looking at your dcs.log there is a bit more to do:

- Turn off SSLR.
- Turn off SSAO.
- Disable civil traffic.

These are expensive things. Delete Saved Games\DCS\fxo and metashaders2 also.
And increase your pagefile. You want at least 32, better 48+ GB on your fastest drive. Only one pagefile please.

Is pagefile needed with 64GB of RAM and SSD?

[Panzerlang]

45 minutes ago, Special K said:

Looking at your dcs.log there is a bit more to do:

- Turn off SSLR.
- Turn off SSAO.
- Disable civil traffic.

These are expensive things. Delete Saved Games\DCS\fxo and metashaders2 also.
And increase your pagefile. You want at least 32, better 48+ GB on your fastest drive. Only one pagefile please.

I'll do that next. Had murders getting quadviews to work again, Pimax Play didn't like giving up those goodies. However, the difference now is huge. There is still the occasional 'step' but no more micro stutters or jerks. I define stutters/jerks as a fast or slow machine-gun hesitation of the graphics. What I have now are revolver shots.

FPS readout:

No FPS cap, smooth graphics and barely drops from 90 and the message says "CPU Bound (Rendering thread)", all in yellow text (previously was red).
FPS capped to 75, stuttery mess and message says "CPU Bound (FPS Limit)", all in yellow text.

I can now more intuitively sense that the dips below 90fps account for the steps in the graphics. But boy, what an improvement! Thank you SK.

DxDiag.txt dcs.log

[BIGNEWY]

Good to hear you have improvement. Dont forget to do your pagefile, change your pagefile to at least 32768 MB (initial size).

Also have you considered lowering the refresh rate in pimax crystal to 72hz? I recently reduced mine and it was an improvement for me, not trying to chase the 90hz higher target. 

 

[gonvise]

17 minutes ago, BIGNEWY said:

Good to hear you have improvement. Dont forget to do your pagefile, change your pagefile to at least 32768 MB (initial size).

Also have you considered lowering the refresh rate in pimax crystal to 72hz? I recently reduced mine and it was an improvement for me, not trying to chase the 90hz higher target. 

 

Is pagefile needed with 64GB of RAM and SSD? what size?

[Panzerlang]

9 minutes ago, BIGNEWY said:

Good to hear you have improvement. Dont forget to do your pagefile, change your pagefile to at least 32768 MB (initial size).

Also have you considered lowering the refresh rate in pimax crystal to 72hz? I recently reduced mine and it was an improvement for me, not trying to chase the 90hz higher target. 

 

Thanks Newy. No, I've tried 72hz and it makes the image 'vibrate' furiously.

I turned off SSLR, SSAO and Civ Traffic, no difference that I could see.

However, regarding the FPS counter. When entering space above large amounts of trees the FPS bottom window shows a lot of spikes that correspond to stuttering and the message flashes up "CPU Bound (main thread)" in red.

It's now clear that certain scenes hit my hardware, push the FPS below 90 and create timing spikes. But the occurrence of this is now rare and it's only on the deck. Over the city I use for testing the buildings are almost perfectly smooth.

I'll do the pagefile next (tomorrow, it's gone half past midnight here) but I regard this as solved with an apology to ED, it's clearly the demands of a highly sophisticated virtual world on hardware that's one 5090 away from making the full nut.

[Special K]

vor 1 Minute schrieb gonvise:

Is pagefile needed with 64GB of RAM and SSD? what size?

You always need a pagefile, but you can keep it on system managed with that setup.

vor 1 Minute schrieb Panzerlang:

Thanks Newy. No, I've tried 72hz and it makes the image 'vibrate' furiously.

I turned off SSLR, SSAO and Civ Traffic, no difference that I could see.

However, regarding the FPS counter. When entering space above large amounts of trees the FPS bottom window shows a lot of spikes that correspond to stuttering and the message flashes up "CPU Bound (main thread)" in red.

It's now clear that certain scenes hit my hardware, push the FPS below 90 and create timing spikes. But the occurrence of this is now rare and it's only on the deck. Over the city I use for testing the buildings are almost perfectly smooth.

I'll do the pagefile next (tomorrow, it's gone half past midnight here) but I regard this as solved with an apology to ED, it's clearly the demands of a highly sophisticated virtual world on hardware that's one 5090 away from making the full nut.

I use the smoothing with my Pimax, and have quite good results with it. The lags and jitter come for me, if I try to achieve some FPS that my GPU can't handle.

[Panzerlang]

Just now, Special K said:

You always need a pagefile, but you can keep it on system managed with that setup.

Jolly good, I have both. Well, I did have 64GB of RAM but I took out two sticks so I could get XMP working. I have x2 32GB Kingston Fury inbound though.

[Special K]

vor 18 Minuten schrieb Panzerlang:

Jolly good, I have both. Well, I did have 64GB of RAM but I took out two sticks so I could get XMP working. I have x2 32GB Kingston Fury inbound though.

64 GB is always better than XMP. XMP does not give you much, some single digit FPS maybe, unless your system is completely unbalanced.

[BIGNEWY]

regarding 72hz, try capping your fps to 72 also, it can help in some cases for smoothing things out. 

[Moxica]

16 minutes ago, BIGNEWY said:

regarding 72hz, try capping your fps to 72 also, it can help in some cases for smoothing things out. 

Closest I could get was 70 FPS.. Is it possible to set it at 72?

Edited December 10, 2024 by Moxica

[unclesneep]

I tried lowering my pimax to 72hz..but for some reason it just seems ..off.. put it back to 90hz, but limit frames to 75 in dcs..seems to work well with my i9 14900 64gb ram and 3080.  Thank God for quadviews..without it game would be unplayable

[Panzerlang]

6 hours ago, BIGNEWY said:

regarding 72hz, try capping your fps to 72 also, it can help in some cases for smoothing things out. 

Lol, Chat-GPT just suggested that too.

[Gryzor]

Just to inform, with the new V72 update for Quest 3, random microstutterings or "lag spikes" have been practically eliminated. Now it runs completely smoothly when using Virtual Desktop (H264+ at 500mbs). Let's hope it stays this way and Meta doesn't mess it up again.... Has anyone else experienced the same with latest V72?

[Panzerlang]

9 hours ago, BIGNEWY said:

regarding 72hz, try capping your fps to 72 also, it can help in some cases for smoothing things out. 

I set 72hz in the headset, FPS slider overides a LUA file setting of 72fps so the closest I can get in DCS is 70fps. My eyes did eventually mostly accommodate to the 72hz (not perfect) but no real difference with 90hz (with fps slider cap at 70fps or 300fps). But the game now runs 95% smooth as silk on the deck. Above 1000m (guestimate and varies slightly) it's 100% smooth. I'm plenty happy with that.

[gonvise]

Also, disable Hardware Accelerated GPU Scheduling in Windows settings. It increases input latency and stutter, especially on mid to high end systems when using VR. For me it has been a substantial change in terms of stuttering.

[j9murphy]

3 hours ago, gonvise said:

Also, disable Hardware Accelerated GPU Scheduling in Windows settings. It increases input latency and stutter, especially on mid to high end systems when using VR. For me it has been a substantial change in terms of stuttering.

Are you using Windows 10 or 11?

[The_Nephilim]

13 hours ago, Gryzor said:

Just to inform, with the new V72 update for Quest 3, random microstutterings or "lag spikes" have been practically eliminated. Now it runs completely smoothly when using Virtual Desktop (H264+ at 500mbs). Let's hope it stays this way and Meta doesn't mess it up again.... Has anyone else experienced the same with latest V72?

to be honest I am afraid to try it.. does it work well with the link cable?

On 12/10/2024 at 9:05 AM, Special K said:

No, these settings are all Windows. Do NOT disable any cores, do NOT use Process Lasso anymore on Win11. The MT stuff is running quite well now without.

 

 

why not use Process Lasso, why would I use the ecores for DCS?? any benchmarks with and without PL?

[Gryzor]

37 minutes ago, The_Nephilim said:

to be honest I am afraid to try it.. does it work well with the link cable?

why not use Process Lasso, why would I use the ecores for DCS?? any benchmarks with and without PL?

I have better graphics quality and performance with VD. Much better than with cable. I don´t tested it.