Sr.

Upgraded: Slight improvement if anything.

Haven't played MP in while but, I can't imagine it wouldn't be. Doesn't affect any original files except openvr_app.dll

At a minimum, I would try Open FSR https://github.com/fholger/openvr_fsr/releases

I have seen this behavior before too. It's like no matter what you set in SVR, WMR would take over. Since then, I've had this option set in my default.vrsettings file Not sure if this is still applicable but I've never had reason to change it... it will default upon reinstall of WMR for SVR.

Sorry if I missed but, are you running any shader mods? Open FSR would probably shave off 5ms by itself. Another thing I just remembered from my 1080ti days... I got a pretty decent performance gain after uninstalling GeForce experience and opting for drive only installs. Even better after I stopped using the Nvidia CP altogether and only OC the 1080ti using MSI Afterburner.

Ah, so you're in multiplayer? How's everything perform in single mode?

This was a much debated and widely reported issue the devs are looking into. For now, I have simply dialed back my SteamVR SS to a level where I can maintain 14-17 ms GPU frametimes in Caucuses and still have a readable cockpit. I've also decided I like flying NTTC a lot more lately. Curious what your GPU temps are hitting when running DCS?

This sounds exactly like what I posted over on the MSF Simu-loader forum months ago. I finally deleted that turd once and for all.

I get the same. Easy trade off though considering MS off is unbearably jerky.

https://www.guru3d.com/files-details/display-driver-uninstaller-download.html

Same

Oddly enough, whichever order I toggle, I still get Overlap warnings. Decided to just confirm them and let the game load. Main menu hangar still clouded out.

What would be the proper "firing order"?

Didn't at all say I "fixed" it. What I did is find a way for me to enjoy flying with no stutter and readable clarity. Something to do until there is an actual fix. Sorry if I prefer to not add to the ED dogpiling.

I seem to have gotten mine back to "normal". At 90Hz: I had to dial back SVRSS to 60% from my previous 80-100% (I ran tree heavy maps at 80 and Nevada at 100) both at 4x MSAA with motion smoothing enable and maintain 45 fps/15-7 GPU frametimes. I decided to try setting WMR to 60Hz, and while yes there is a slight flicker in the sky, I've gotten used to it. Hardly even notice it now. I can run my usual "High" in game settings, SVRSS 80%, NO motion smoothing (and no stutter), solid 60fps 10-15ms GPU frametimes. Very enjoyable flight experience, readable cockpits, ZERO stutter. I am running 1.2 Open FSR at .77, 0 sharpen. Reshade mod and the following other mods.

Relative how? Like worse for "high" end and less worse for lower end specs?

Oh yeah. If I ran 2.7.6 at 60/70% it was close to 10ms GPU frame time. But I usually ran 2.7.6 at 90/100% SVRSS at around 14-17ms GPU frametime.

NP Was I supposed to crash into the water?

Barely 1 ms for me

I got my fps back doing the above... ultimately had to settle for 70% SteamVR SS. But pit still readable. Also using SOH DCS VR Shaders mod for 2.7.7.14727 (Clear Water) & Open FSR

Is there a particular order when toggling these?

I'd be happier if they just gave an option under "Special", to turn them off like with the Hornet and Viper. One less mod to jack with.

Maybe they just have lower standards/expectations I know... NOT helping

Just started messing with this one. Should my night cockpit look like this? Also the hangar lobby looks like it's under water.