Panzerlang

Just to clarify, the Pimax render setting and DCS Pixel Density setting are interchangeable. You can mix them together (don't know of any reason to do that though) but as already mentioned, I find the Pimax option gives a better image quality (text in the cockpit is clearer for the most visible example). Pimax at max, DCS at min.

The Res of Cockpit displays is wrong, it should be at 1040. I accidentally hit the Low button and missed setting that back.

Taking absolute GPU liberties. Ignore the resolution, I opened in 2D for greater ease of taking a screenie. The only setting that affects the VR stutter is having the view distance at Extreme. There's a huge free-flight area on the Caucasus map where you can see for miles. Panning the view around that causes lots of spikes but once everything has loaded it becomes smooth again. But the loading is ongoing, so it's all a bit spikey. On High the spiking goes away. This is on a 4090 and i9 13900k at 5.5ghz, 32GB RAM and clearly shows how the CPU is the limitation. There are zero GPU messages in the FPS window, it's just a yellow "CPU Bound, Rendering Thread". With View Distance on High my DCS runs 95% smooth, with the 5% being the occasional jerk. With a lesser GPU these liberties can't be taken but I have no idea where the threshold is at. Anyway, FWIW.

It didn't with the Pico4 until I'd messed around with Network settings. I persisted only because of the YT videos that clearly showed it should/could/would. Lol.

It's there.

If you have a very good GPU (a 4090 basically, lol) the issue with DCS is the CPU. Even the most powerful one finds it hard to keep up. The FPS counter in the game has shown only "CPU Bound" messages, mainly on the graphics rendering thread. Today I'll see what settings that involve the CPU can be dialled back and try it out.

What makes you think VD won't work on a cable connection? It worked fine that way with my Pico4. I don't know for sure but I strongly suspect Core Parking was the culprit.

If your current install isn't causing any problems I'd say stick with it. Windows is very robust now. You'll probably need to reactivate it with the new mobo.

What's DCS's Pixel Density set at? In my testing I found Pimax' render setting to give a superior image quality. So, Pimax at 2.0 (or 1.5/1.0, given your GPU) and DCS PD at 0.5. If that doesn't fix it you need to rule out graphics as a cause by going full potato in the graphics settings, everything to lowest possible. Then cross your fingers when you test it. Have you successfully run the PCL in any other VR games?

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.

Go from page 2 in this thread. Core Parking and Core Isolation, disable Process Lasso, huge improvement on my rig.

Are you using QV Companion? Maybe your focus edge is too sharp? Companion lets you set that in pixels.

Lol, Chat-GPT just suggested that too.

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.

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'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

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

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.

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

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).

Bluescreens? I had a few some months ago when I was trying to XMP my RAM but zero since. I have Prime? You mean the Pimax thing? Nope. However, just after I uploaded the dxdiag I ran DCS with Pimax' OpenXR and it's the smoothest play yet. Not perfect but to the point where the jerks/stutters could be regarded as pilot buffeting. However, I haven't done anything to disable MBucchia's OpenXR...does the Pimax one over-ride it? - Game Mode disables I'll google that. - Hardware Accelerated GPU Scheduling disabled In NVidia control panel? - Core Isolation disabled Same as the Process Lasso thing? (if so, already done). - Core parking disabled Ditto line above. In Process Lasso I have DCS running on just four P-Cores. All E-Cores are excluded from DCS. Four P-Cores gives the least amount of stutter.

DCS Log. dcs.log

Me file guvnor. Cheers Newy. DxDiag.txt I've just installed some Pimax gubbins, now I see quadviews and stuff in Pimax Play. The next round of experimentation begins...

How do I generate a DXDiag file? I recall doing it many years ago but my brain chose to bin the detail memories due to decrepitation issues.

Hooray! Yes, good point re the stats. I watch a lot of the Big Boys on YT and see a fair bit of stutter in their vids though. My impression is that it's common but people have simply become used to it?