Panzerlang

Those most easily impressed are those least worth impressing.

This seems to be reasonably believable. Around 3000 Euros for the 5090s. Obscene. Like, properly obscene. Anyone who believes any amount of R&D and blah blah blah for consumer-grade electronic components can justify or explain such a price needs their head tested. Custom GeForce RTX 5080 and RTX 5090 pricing emerges: made for gamers with deep pockets - VideoCardz.com

I reckon the frame-capping etc uses CPU cycles and as DCS is already flogging one or two of my cores at 100% it just adds to the burden. Using the DCS FPS counter I see very low spikes, so I think Frame time is decent. My stutter is very minimal, I have to look for it to see it.

I've yet to find/use an OpenXR frametime app. 90hz. I've tried all the frame-capping, lower Hz, re-projection, on their own and in combos, they all made the stutter worse.

There was a bunch of components on the cargo plane that crashed a few months ago, that's why the Flanker grip got so badly delayed.

I know, just can't remember his name. Yeah, he'd thrive on a shady car-lot, selling old beaters. "This old Toyota Prius, we tweaked the ECU and now it can go as fast as a Ferrari!"

No matter what you do, you won't be able to completely eradicate micro-stutter/jerking, no matter your graphics settings. Having said that, you can reduce them with settings and Windows and hardware tweaks. Regarding resolution (OG Crystal here with 13900k and 4090), I run the headset at native resolution (1.0) and DCS Pixel Density at 1.0. I've had the headset at 0.75 and could barely tell any visual difference (image quality) but as it made no further improvement to the stutter I put it back to 1.0. Why does 1.0 and 0.75 have so little difference on image quality? Somebody elsewhere pointed out what might be obvious to some (if correct) and that's that the game itself has a limit on how high the resolution of the objects (planes etc) can be. If the hardware is set beyond that limit, you won't see the 'expected' improvement. So, 0.75 Headset and 1.0 DCS PD with my set up, with a 4070Ti YMMV.

What an absolute spiv. The guy in the video.

The SimHaptic line in the lua file vanished by itself in my case. Reinstall SimHaptic.

I was rather interested in his detailed description of dialling in the physical fit, which seemed to eradicate most of the issues MRTV described (who didn't mention any of that). Could it have been that simple?

Couldn't be more opposite to MRTV's one.

No, I don't. But I have no idea how the Quest Pro works in that regard. I never used to have to re-centre the headset, now I have to do it every time I fire it up. It's pretty quick, just hold down the Pimax logoed button on the controller, wait for the green circle thing to do it's turn, keep the button pressed until the short vibe indicates the controller is shutting down and carry on.

Cynicism alert...I have little doubt NVidia has their tech one or two (or three...) generations ahead of what they're currently selling. They trickle it out like treacle to maximise revenue. I reckon.

With me (Pimax OG Crystal), that happens until I centre the headset (that's separate from centering VR and/or NeckSafer). It's not a bug in NeckSafer.

For the squished XRNS panel issue right click on its desktop icon, then: Properties -> Compatibility -> High DPI Settings -> Override scaling behavior performed by System. Simple tool to check your six - Page 29 - Virtual Reality and VR Controllers - IL-2 Sturmovik Forum

And this is the company that asks people not to send parcels with signature required. Red flags anyone? Or just me, being 'paranoid' again. Where's Calvin these days?

I covered my definition in this video (posted in this thread a few days ago).

Four days for my parcel to be 'security checked' at Frankfurt. I expect they'll now fly it to china before it gets here to Japan.

Now delayed to late Feb or March.

Thanks man, good to know. By printer cable, you mean a USB that has a square connector on one end?

Well, maybe it's apples and oranges but IL2 (single core) thrashes the GPU quite nicely but barely touches the CPU, assuming the Game Bar widget is accurate. That reports 7% CPU usage (highest I saw at least). Yeah, kind of hard to believe the widget's accuracy, one would think 87% GPU would be pushing at least one core on the CPU way higher than 7% (I'm assuming the GPU render-load can't be split over multiple cores).

No idea. It might be hardware dependent but given how many people with high-end kit are suffering from stuttering, at some level or other (it can be mitigated with a shed-load of tweaks that we shouldn't have to be doing) I think it's a good guess that the over-loaded single-core scenario is a good candidate.

Mine seems to be warehoused in Frankfurt since Friday. How's the setup going? The software was patched to 2.5 the other day and there's a firmware hex in the zip, not looking forward to flashing the thing.

Seems to me, 'all they need to do' is stop the code from maxing out a single core. If the load was spread evenly (as in 35% on ALL cores, instead of 35% on all the cores but the one getting hit for 100%) I think the stutter would be fixed. It's only my inexpert opinion but it does appear the MT coding is currently fubar.

Wow! The very definition of 'picture perfect'! 36% package with one core getting a 100% flogging.