desolunatic

@Skael In Nvidia control panel change "Virtual per-rendered frames" to 1. Your current setting of 3 puts unnecessary strain on CPU and should be used only with weak GPUs, yours isn't weak (so using 3 as pre-rendered frames only creates a problem that people then try to solve by lowering settings that affect CPU). Also I find it that for whatever reason flat ground shadows don't perform well. Put Regular Shadows to high, terrain shadows to default. Lower the pre-load radius to something like dunno 60000-80000. These 3 things should fix your issues - the only other setting that really affects CPU significantly is view distance (and I guess secondary shadows but not everyone likes how they look so I usually skip that) but your CPU is strong enough to handle high and even ultra comfortably. On modern CPUs other settings are pretty much only dependent on GPU so you can turn them up for some eye-candy (I also recommend checking out DLAA with some proper super sampling set on your headset, looks really cool imho). If you will try DLAA, turn off MSAA x2 in Nvidia control panel. EDIT: In addition to above you can also use new experimental setting that BigNewy proposed for stuttering:

Read below thread from linked comments till the end, couple findings there that can help with this issue - it's titled regarding f10 and f1 views but if vram usage goes up too high mission load can also trigger what's being discussed there.

Set it to "Prefer No Sysmem Fallback" and check if DCS runs better. (Couz the default setting is different)

Should have said I have this setting on the latest driver version, 546.01

People having this issue, can you check if setting in Nvidia Control Panel - CUDA Sysmem fallback policy set to "Prefer No Sysmem Fallback" helps?

But am I understanding correctly that you are also getting FPS drops in F10 view during normal play?

So, it turns out that if you alt-tab very quickly out of DCS when it is loading new assets in, you will not run out of VRAM in VR even on a 10 GB card. I made a macro for my keyboard that quickly alt tabs out of the game whenever I press F1, F2 and F10 and it appears to be enough to prevent the VRAM related issues that come with browsing different F2 views and going into F10 map (especially in multiplayer or in very complex missions). My VRAM usage with medium / high textures and an approx 3000x3000 per eye headset resolution didn't go above 6 GB where without this alt tabbing I needed to be using medium / low textures for the game to be playable for any reasonable amount of time. I recorded a video and linked it here for partypoopers saying "pics or didnt happen" It is super weird but oh well.

Leave native - you can compare fps with DLSS and DLAA - the latter doesn't do any upscaling.

Hmm, anyone in the team has a Quest and a gpu with 8 or 10 gigs of VRAM? It should be very easy to reproduce on any of the Grayflag servers with such hardware. If not I can even let you guys remote connect to my PC and I can reproduce it 99% of time

I like to use both OpenXR and OpenVR - OpenXR for streaming thanks to the head smoothing option, OpenVR for off-stream flying with reshade.

You can do that via SteamVR but mind you the performance will be suboptimal still compared to simply playing 2D - you need some resources on the GPU to run the SteamVR in reasonably high resolution to warrant readability of the game mirror and the game itself on top of it - if you get Virtual Desktop on steam you can also try doing a "fake VR" - run the game in 2D, tie the game mirror to follow your head movements and then you can run OpenTrack in the background with SteamVR as source of the head movement with 1:1 curves. Regular 2D curves need to be applied for regular "VR theatre" viewing. @Eugel

Try underclocking your GPU a bit and see if it persists, if it persists observe your VRAM usage.

Getting the same issue with these settings: Options.lua Happens on both 1080p and 4k, using Quest 2 via --force_OpenXR if that matters.

Please post your in-game settings also check your cpu, gpu and VRM temperature up until and while the stutters are happening.