Panzerlang

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.

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.

Same issue here. It previously ran smooth as silk on very high settings, now on the stock VR setting it still has micro-jerking at low level (ground, trees, buildings etc). I've spent the last three hours going through everything I could find on the internet. Already had Process Lasso going. Mouse polling-rate to 500hz. DCS and Saved Games excluded from Windows Defender. Windows Power Service disabled. Crystal Render Rate set to lowest (DCS PD at 1.5). 13900k, 4090, 64GB RAM, game on separate SSD.

I have a friend in china who deals for the super-clone watch factories there. He tells me factories do suffer raids by the authorities, staff get prison sentences and all the equipment is confiscated. They periodically raid and shut down the huge night-market close to the border with Hong Kong. I guess companies like Rolex have sufficient clout.

I've built dedicated ones before but finally went for an all-in-one combo so I can make use of the PC for daily use as well as flight simming. I think this is as good as it can get, short of sliding a motion-platform in under the desk (it's electric, up & down, very handy). Hope it's of some inspiration.

Lul, whut? I'm running DCS at very high settings on a Crystal with a 4090 and it's very smooth (slight steppiness looking sideways, low to the ground, but I've previously had that perfect too...updates are the bane of VR). I originally had a G2 on a 1080Ti and it was playable. Upgraded to a 3080Ti and it was superb. My 4090 would have stomped it.

Hi GV. Is the angle of the foot-plates (rudder and brakes) adjustable? As it is, it looks like it would be difficult to use the rudder on the ground without also activating the brakes, at least for people like me who have canoes for feet. Lol.

Please describe the higher quality. I have no experience of either but I've heard bad things about Winwing.

Crystal: ExperienceHome how to use mouse/recenter if controllers not in use? : r/Pimax

I've experienced flawless smoothness but every time there's an update the view from the cockpit sideways reintroduces very mild 'steppiness'. Lol. It can be quite exhausting trying to re-obtain the previous perfection, but I do at least know it's possible.

On your Pimax controller, headset and controller on, press the button with the Pimax logo on it, that should activate a window in which, bottom-left, you can recentre the headset. I think holding that button down also recentres the headset without the window popping up. It might fix your issue as it fixes my NSXR being out of whack occasionally. Obviously be wearing the headset and facing forward.

Virpil gear is over-engineered and at the top of the quality tree. Lol.

Turn off DFR in Pimax Play, though I've not noticed any difference with it on.