edmuss

Should be more than enough

If you have sufficient CPU and ram then run a local private multiplayer server and join that instead of just playing the mission single player, get much better CPU usage this way

In the latest update, this appears to be fixed. No longer seem to have any major fps drop once the rotors are at full speed @BIGNEWY can you confirm if this is the case officially or has it been fixed in along with something else?

Unless you have a full blown simpit then I think passthrough XR is more immersion breaking for the purposes of a simulation game. For me, a well setup leap motion is far more immersive to reach out and flick a virtual switch as you retain the lighting from DCS, added bonus you can use the leap hands to shade the MFDs in bright sunlight Regarding the xr4, a lot of reports are of display artifacts which haven't been solved as of yet; it's far from mature and I wouldn't want to think about dropping that value on a headset without it being perfect.

Yeah, it is only a vague notion that it might do something, certainly no hard and fast change. For reference, don't rely on the VRAM usage in task manager as that will always show full with DCS (what DCS has allocated), use the expanded performance metrics and that will show you the actual VRAM in use.

Check the vram usage and budget (expanded performance metrics with right ctrl+pause) when this happens, it sounds symptomatic of overrunning the vram; when it happens the FPS jumps in square steps about 15-10 and the smoothness goes out the window regardless of your FPS. I suffer from it on certain modules (moreso the hind with it's masses of textures) if I run with high textures enabled; older modules like the A10C have a lower texture load so can run high without an issue. Also try the 'no sysmem fallback' option in the nvcpl, it stops the GPU driver paging vram to system ram. Theoretically it should only be for CUDA applications, however the nvidia GPU core architecture is also called CUDA so it might apply across the board? I have it enabled but can't say for certain that it helps, it certainly doesn't eliminate the issue and it may well be placebo.

Yeah, they're not cheap, but I figured having got the top end headset it would be silly to not spend on the controllers As it was, my G2 sold for 250 which covered the index controllers. It's quite possible to pick them up cheap with stick drift and I believe it's pretty simple to replace the sticks.

Likewise, sold my G2 and bought some index controllers Never use them for DCS though, only get turned on for HL Alyx and Into the Radius. I have a leap motion on the aero for handtracking and use mouse cursor slaved to the headset with mouse controls bound to hotas for backup when the leap motion isn't practical.

I typically see about 75% with the 7800x3D and 3080ti as well, I shouldn't worry about it

It's might be a break in the wire between the plug and the daughter board, in one position it breaks connection, flexed another way it makes connection. A multimeter on continuity connected to both ends whilst wiggling the wires would help identify if it happens again.

Possibly a broken solder joint or wire inside, only way to tell is disassembly.

Your settings are higher than I would run with your hardware, ghosting is typically a result of DLAA (Not specifically DLSS) and the lower you fps the worse it will be. However if you still get ghosting with DLAA off it's because you're below refresh rate of the headset and there is a frame desync; two options, get the fps above refresh rate or enable reprojection.

Using the meta PTC? V63 breaks DCS, rollback to V62 is the current workaround.

Not had any issues flying around Damascus, also I'm not using quad views but varjo foveated which is lighter on the CPU anyways. Worth remembering though if there is unexplained performance loss

Now of course with the qpro you might be beyond the point of diminishing returns with the 1200x1200, at some point the panels will become saturated as they're physically a good deal lower resolution than the aeros. With DLAA I find that there is no perceptible shimmer/resolution artifacts on the peripheral, perhaps just wind it down so it's at 60% and see how it goes. I know that the QVFR numbers work slightly differently to VFR but the concept is the same and whilst beta testing QVFR I found that performance was pretty much en par once the resolutions were matched. My reasons for using VFR over QVFR is that there is an eye tracking data bug between varjo base and QVFR and there is a higher CPU load with QVFR. Functionally though, they're pretty much the same system