Panzerlang

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?

ED have us chasing our tails with this, with zero input. Even if it was only to say "It's our code and we can't fix it", at least we'd be able to quit. Lol. Here's a question...DCS "now supports OpenXR natively"...does that mean we could use it instead of Pimax' OpenXR? I have no idea how to disable Pimax OpenXR though but I'd like to give it a shot.

Funnily enough I ran that NVidia overclock thing on it yesterday, it gave me around 200 extra mhz. So no, before and after that, zero difference.

Yes, purchased before the Prime program was introduced (in my case, the original Crystal last year). "This update introduces the Prime program, which requires new users to download the updated client." So the updated client is an optional component within the latest Pimax Play, and doesn't need to be activated by owners of pre-Prime hardware?

Yes, it is something else. As I said above, with all (ALL) graphics settings set to potato, there are still micro-jerks. Nope. Capping the FPS (in the headset or in the game's settings), stutter becomes worse. Smoothing, ditto.

So owners of pre-prime hardware are being forced to subscribe to Prime?

It's very difficult to see it but the same stutter exists in 2D mode also. It's like the code of something is failing to send imagery to the headset fast enough and it has next to nothing to do with settings. Yes, the stutter can be made worse with mental settings but even with the load almost entirely removed (all DCS graphic settings set to potato) it still exists. It's very evident with Quadviews disabled but with QV on and potato settings the graphics should flow smooth as silk. But they don't, VR or 2D. And, given it's a very common experience, it can't be down to a particular mobo, CPU, GPU or RAM etc. Brute horsepower and potato everything, ED need to investigate and sort it out.

Original Crystal with eye-tracking. And yes, QV Companion.

I found the FPS counter. It doesn't seem to go lower than 80fps (a lot of "CPU Bound" message). So, I set the FPS limiter to 80, as expected the jerkiness was made worse. Back to max (300) and smoother again. Unfortunately the counter doesn't appear in the screen-recording I made with Bandicam (replay-track). I've also set the 2D resolution to 1080p, to see if that would make a difference (thinking a lower-res monitor output for VR mirror might help). I've also tried HMD-Mask. It's like the stutter is baked-in. It can be hugely reduced but not eradicated.

Well sure, you can have a headset's render at max and DCS PD at max too, that'll bring a 4090 down to an art gallery with a white cane. But in sane use, with all the aids (OpenXR with Quadviews) I can run very high DCS settings in VR and apart from very minor jerking while doing what no real pilot would do (on the deck, admiring the scenery sideways) the 4090 stomps it.

I wasn't going to update mine, due to reports of Quadview implementation screwing up Quadviews for those who use the external version. Then, while messing around, a Pimax window with a new name popped up, asking for permissions. I figured it might be an existing component, re-asking for permissions, so I yessed it. Bammo, Pimax Play upgraded to latest version. However, DFR can be disabled in Pimax Play, so no apparent harm done.

I had a go with SteamVR, dog's dinner. Back to OpenXR and I thought I'd play with the Quadview settings in that, to really take a load off the system. I reduced the box to 25% x 25% at 100% resolution. Peripheral to 1% (lol). It looked terrible in the menu but surprisingly not that bad once in the cockpit. So, you'd think buttery smooth, right? It was the best so far but still the micro-jerks when looking sideways at low level and really not much different to 35% x 35% and 5% peripheral. And what's going on with capping FPS to half making the jerkiness worse? "Hey GPU, take half the load off...oh, now you're going ass over tit like you got hit with a quart of bourbon?" There is something seriously up with the DCS code, I can think of no other explanation. Having said that, at this point it really is nit-picking because I'm really having to look for it. In actual play the visual experience is more than playable/acceptable. That's in fast planes, I haven't tried the low & slow chopper experience yet.

Are there any that fly the 15, 19 and 21? I'm in Japan so I guess the US timezone(s) would be appropriate. Or Japan, but it's mostly console-jockeys here.