Panzerlang

In my case, Pimax Play native OpenXR and Quadviews worked a little better on my old install and just as good on my fresh W11-Pro 24H2 install.

Sorry dude, thought I had. No, I'm using the Pimax Play software now. I did previously have MBucchia's software...turbo on or off, no difference (OpenXR Companion). I've had that cockpit jitter too but it was tied to overall settings (at 120htz it was very obvious). Maybe try the cockpit jpg settings? (250 vs 1040 or something).

I had it for a bit (the NVidia App did it) but I saw no impact from it in the game for good or bad.

Oh, I've completely turned off all anti aliasing without any significant visible difference to image quality but with definitely smoother frames.

Nice. But yes, it's a crying shame that different maps have massively different performance for no apparent reason. Caucasus and Mariannas have very similar building and tree densities, but the latter is a spike & stutter fest. Like an idiot I went and bought every single map, only to find most of them are unplayable in VR. Not impressed with ED on that front, at all. Maybe they should focus on making the latest map useable before pumping out a new one.

Is it not possible to swap the lenses?

Ok, I guess the OG and Light have different firmwares then. Nothing for the OG currently.

I thought I'd give 72htz another try after installing the latest Pimax Play software but same old same old, it makes the stutter worse. I'm starting to agree with the notion of others, that it's the Pimax software at issue rather than DCS. How can REDUCING the headset's workload make things the opposite of betterer? Lol. 120htz, way more stutter (as to be expected).

Ah, I think you're confusing firmware with software.

I have only DCS on this rig after I did the OS re-install and I'm running OpenXR and Quadviews on the Pimax native software. I tried the DCS FPS slider on 95 and 45. 95 was no visible difference to 300 but on 45 the image (looking sideways out the cockpit at 50m altitude) was awful. Micro-stutter on steroids. Firmware? No, I downloaded the latest Pimax Play but I had no idea there was a firmware update too. I'll do that now. Um, no I won't, it says there isn't one. Lol. My current firmware is 1.3.0_au0531

Caucasus, very smooth, Mariannas a spike/stutter fest. Why? Is it a palm-tree thing? Even from a distance, out to sea, if I look at the sea it's smooth. Soon as I turn my head and get the island in view, spikes up the yang-yang.

Awesome news!

What headset? I now have to re-center my Crystal with its controller before I fire up DCS. Once in the game I hit the game's VR re-center button (just to fine-tune the view). So, try re-centering your HEADSET before firing up DCS.

This is all very interesting. I've tried capping my FPS, both in the Pimax Play software and in the DCS settings. Both increase stutter. So, in DCS, I have the slider at max (300FPS). My monitor is at 120htz. When I run DCS in monitor mode I can barely see the most tiny evidence of micro-stutter. The FPS window shows FPS at 240-ish to 300. The frame-time graph at the bottom is almost 100% smooth (occasional tiny spikes). Message, yellow/green "CPU Bound, Rendering Thread".

Thanks. Another issue I've discovered...after enabling the UVC, then disabling it, my desktop camera was completely gone from the system. I had to do a scan to re-find it. I hope the pass-through software for the Super will be in good shape. It would also be nice if the Pimax devs would fix existing software before dumping it and moving on to the new stuff.

And then add headset software to the mix. And myriad utilities (NeckSafer, SimHaptic etc). And then when they're combined vs running on their own. It's a minefield. Having said that, DCS stutter seems to be ubiquitous.

If my Pico4 was 'plug & play' on the ethernet cable I'd give it a go. I can't remember how it was with DCS. I do know I seriously considered going back to it after firing up the Crystal for the first time.

Suck it and see. Soon as I reduce it to anything other than max (300) I get stutters. I think it uses a fair bit of CPU to do it.

Oh, might be a clue...running in 2D, the FPS windows shows exclusively green and yellow "CPU Bound, Rendering Thread". In VR, exclusively red "CPU Bound, Main Thread". So, VR is hitting the CPU very hard. Is that a Pimax thing or is it the same regardless of headset brand?

I enabled HAGS and did a test flight. At the margins I'm getting it's kind of hard to know if there's a real difference but I did get the feeling there were less micro-stutters, just the same micro-jerks (inconsequential, because I really have to look for them). I'm going to leave it enabled. FPS window, almost entirely red "CPU Bound, Main Thread". Previous test was with everything connected to running DCS excluded from Windows Defender. Can't say I saw a jot of difference with all that done. I'm of course wondering if HAGS will do better with a 5090. The more load that can be taken off the CPU the better, right? Plus the Crystal Super will almost certainly need the 5090's extra horse power. I'm still pointing my finger at your CPU. I'm clueless about AMD, broadly speaking, but can your mobo accommodate a 7800X3D?

Jesus, and I thought doing it with the Pico4 was a PITA.

They don't do themselves any favours with not showing stock. It's either "Pre-Order" or "Back-Order" and "Back-Order" sees your stuff either immediately shipped or goes into limbo while new stock is on the way. They don't send any emails to tell you which is which or when the limbo stuff is due, so unless you email them to ask (before or after you make an order) you're left hanging. I've bought close to 2000 Euros worth of gear from them over the last couple of years so I've not had any aggro getting refunds in a timely manner (cancelled a Flanker grip and a heli base & grip). Possibly they had ordered a restock to cover your order and got miffed when you cancelled it. They need to clearly show what's in stock and ready to go of course, that whole "Back-Order" thing is a PITA.

When mapping this cockpit knob to Virpil Rotary Encoders it doesn't function correctly. All other knobs (so far) map correctly. I've tested it on multiple encoders that work correctly for other cockpit knobs, so it's definitely the plane's code that's bugged.

Yes, BAR is enabled. DxDiag.txt

Yes to those three, all disabled. One of the devs said a set pagefile isn't needed with 64GB of RAM. I'm on fast SSDs (Samsung "UFOs" according to UserBenchmark, lol). I should point out that, in general, the micro-stutter I see is either extremely low or seen only in specific places. When I'm on the deck of a carrier for instance, looking at the other planes from my cockpit produces noticeable micro-stutter. I consider that to be very odd.