Taterbootz

Try a earlier version. I dont remembr which one I run, but I run an older version and cant get the newer ones to work. Not sure why tbqh, but I gave up trying after I found one that works.

rename your saved games folder to DCS.old or something and have the game create a new saved games folder. Then move your mods/inputs/bindings/whatever back. This has almost always solved weird little issues with VR for some reason (even ones that deleting FXO and metashaders wouldnt fix). Not sure why, but its an easy thing to try and has great results. Also try completely removing SteamVR (google the correct way, IIRC you delete the default.vrsettings file from the steamVR folder, and a couple of similar files in the steam config folder. I havent had too many CPU usage issues, but most of the issues were resolved with updated files completely unrelated to what you would think would be causing the problem.

Set motion smoothing to "Force Always-On" in the steam video per apps setting for DCS. It will lock your frames to 45 but it will smooth everything out. Only real way to get smooth frames is to either be able to power the headset to its full resolution and speed (90fps all the time) or to run motion smoothing. I find Motion Vectoring with WMR to be superior to Steam's Motion Smoothing, but its also more finicky with DCS it seems.

Just tried this with 1.3 and 1.5 and it wouldnt upscale past some god awful resolution (like 1544x1530 or something) no matter how I set the PD and SS.

That sucks. It was more than likely a conflict with reshade and FSR. I get a massive performance increase running FSR with minimal visual issues.

Rename your saved games folder to something like DCS.openbeta.old and let it populate a new saved games folder. Play and see if its better with that, if so, add some of the custom files or mods back in to see what causes the issue. Getting a new saved games folder made a giant difference for me a few days ago.

Thats weird. What does the openvr_mod.log say its doing with the textures? A lot of times using ReShade will cause the OpenFSR to not work due to using some of the same .dll's.

Yeah I cant see it causing increased GPU mem usage at all, but it could just be the straw that breaks the fragile WMR/SteamVR relationships back for some reason. I've been struggling with issues with steamVR crashing a lot myself. Actually just crashed when I started up my controller, so I found that I had two profiles for controllers in the settings and my drivers werent up to date. Currently its working good.

I've been running into the same issue with SteamVR lately. When I chased it down in the SteamVR logs it was an audio issue when I was also heavily using the GPU, so I disabled "Loudness Equalization" from the headset properties and that seems to have fixed it for me. Check all of the steamVR logs to see what was causing it then you might be able to track it down better.

I use VRNECKSAFER so I don't have that issue. You can make it as much or as little help as you want, but its the only way to play VR IMO, especially with the lack of FOV and peripheral vision compared to normal eyesight. But I have stuck my head out of the cockpit on accident leaning too far, so I just...don't do that...