Panzerlang

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.

I've always installed over it and never had issues (other than the permanent ones that no updates ever seem to fix).

I noticed that last night but I also messed with my RAM. Two sticks removed and with the latest BIOS update I finally have XMP working. Even over a big city (I flew for about 30 minutes) there was much less stutter. Trees seem to be the biggest culprit.

That did it, thanks man. Ha, the location tab is there now too.

Yeah, options.lua last datestamp is from yesterday. I broke stuff. Any idea how I'd fix that? I already ran DCS repair prior to the last test missions.

It's seeing graphics settings ok. I tried Pimax Play render and game's Pixel Density at max together, computer said "NO!". Lol. However, I've established that the image quality is superior with max Pimax and min PD. It's also the smoothest regarding stuttering. I also excluded every other active process from using the four P-cores, except those that Process Lasso advised not to. NVidia Overlay is off. I've got DCS running as lean as possible, bar SimHaptics and DC-Realistic (they both default to using the same cores I set for DCS, so I'm assuming the way they work is they're seen by DCS as a native component). I'm going to test with both of those disabled next.

I tried the setting in Pimax Play to limit FPS to 45, it made the stutter worse. I've also previously played with the Target FPS slider in the game settings and that made things worse too. As mentioned above, it's not an FPS issue, I see zero ghosting. And I've tried potato graphics settings, looks like vaseline but the stutter is still there. The weird thing is I currently have the graphics settings through the roof (I was trying to bring the game to its knees) and apart from the micro-stutter it runs perfectly. Pimax Play render at 0.5, DCS Pixel Density at 1.5. I should be seeing ghosting at least but there's none. Re Saved Games, I think you're right Sleighzy, there is no longer a log file in it so I guess I broke something.

There is no Location Tab in the saved games properties window and it appears to be a widely reported missing function in W11.

I can confirm that there is indeed a 'tick rate' to the stutter, which can be seen by flying over empty ground (no trees or other objects to disrupt it). The stutter/jerk happens approx once every 1.5 or 2 seconds. I don't know what kind of clue that provides but it is a clue. If, as I suspect, it's caused by ED's multi-threading code there's not much (if anything) we can do to totally eliminate it. I've got it to a point where everything coming at me through the front of the cockpit is perfectly smooth but I can see the slight stutter of the canopy-frame against the ground (low or high altitude) as I roll. Looking sideways, very obvious but nowhere near as bad as before I restricted the game to four P-cores. I also removed use of those four cores from other main processes (headset exe and a couple of other guesses).

Zero mods. Headset is at 90hz. I tried 72hz but it produces a flickering image. I haven't done MP much and won't until I'm properly 'trained'. FPS...no figure for that, can only say I see zero issues there. Affinity...isn't that what Process Lasso handles?

Looks like it was saving into the one on the desktop. dcs.log

Done. I removed the Saved Games folder from the C drive and copied it into the same location as the game (D drive). I think DCS no longer sees it as there's nothing in the log after I switched locations. I saw in a video that somebody had it on a different drive but I guess it's not as simple as just copy & pasting it over. dcs.log

Overheat protection; as in a unit that doesn't reduce and/or shut off forces when the motors become too hot in a sustained hard turn in a dogfight. So far, AFAIK, only the FFBeast has motors powerful enough (35nm vs Moza and Rhino 9nm) to not overheat, though I think the new Rhino with bigger motors might also have achieved that.

Hours...HOURS! 13900k, 4090, 64GB RAM, game on SSD (not C drive). In-game graphics settings make zero difference. Ditto resolution. Both, max or minimum, same stutter jerking. Quadviews makes a difference but it's not the fundamental issue. Other things tested: Windows Defender, DCS and Saved Games excluded. No difference. Windows Power Service disabled. No difference. Mouse Polling Rate set to 500hz. No difference. Combos of resolution set in the headset or in the game. No difference. 72hz Refresh Rate. Image high-frequency flicker, no difference otherwise. Smoothing on (Pimax Crystal). Stutter worse. NVidia CP, pre-rendered frames. 4 = more stutter, 1 is best. Hyperthreading disabled (Process Lasso). No difference. Quadviews Turbo Off. No difference. All E-Cores off (Process Lasso). No difference. Then I started messing with the P-Cores. Fortunately this can be done while the game is running. Pause game, alt-tab to Process Lasso, change settings. DCS seems to have a thing for the number of P-Cores. With only two enabled, lots of stutter. With four enabled, the least amount of stutter so far. ALMOST smooth. Up it to six and eight cores, the stutter becomes worse. Four active P-Cores seems to be as good as it gets and you really have to fly low and look sideways and concentrate to see the trees infrequently stutter. I'm almost sure that the stutter becomes constantly timed too, like one micro-jerk per two seconds but it's not reliably reproducible. My conclusion is that DCS MT has issues with the number of P-Cores it uses. Fking around with that sht absolutely affects the graphical performance. FWIW. Oh, the first and last P-Cores, disabling individually and together, no difference.