Bio

I decided to give it another look with MSI afterburner. Still in VR, Pico with Virtual desktop at Ultra (2736x2736) SteamVR as OpenXR runtime. A10CII Syria Air-to-Ground mission, just set the plane in autopilot and waited a bit, switched to map and back to cockpit. System: RTX 3070 8gb, 5800x @4.5, 32gb ram, m.2 drive I got more questions than answers. From the screenshot i marked with an arrow where the map switch is done on the GPU usage. Various weird things happen after F10. - GPU usage goes up - FB usage goes down, shouldn't it go up instead ? - VD usage goes down, shouldn't it go up or stay the same instead ? - BUS usage goes up, kind of makes sense but still weird. I probably don't really understand this one - Memory usage goes slightly down. This is super odd - Heavy power usage fluctuation but overall power usage down The last point is the weirdest of all, higher gpu usage but lower and more unstable power consumption? Could it be it's a CPU issue where DCS is trying to do some weird stuff with textures and asks the GPU to do useless work with memory that takes frame time from rendering ?

Yup, plenty of topics about it that seem to just get ignored, not even specific to VR For example: The issues is caused by the multi threading (MT) version of the game. If you use the ST version, you won't see that problem. It is caused by over usage of VRAM most likely. Most posts i've seen are from 8/10/12 gb vram users and most of the time is caused by Syria map but other will eventually cause that too. You only have 3 options i found to work reliably 1 - Use single threaded version of the game, yes you loose FPS but if you're playing multiplayer and simple single player missions with reprojection you won't even notice it that much 2 - After you get that issue, alt-tab to another full screen application and close your headset by putting it in standby, wait 15ish seconds until you hear the GPU fans winding down and go back to the game. 3 - Don't open the map, ever

I managed to find a way to replicate this 100% of the times and fix it every time. Kudos goes to the many posting on other threads such as: and reddit To replicate it open the instant action "Air-to-Ground" for the A-10CII and simply open the F10 map. Other modules might work but you'll have to find them. To fix it you need to alt tab into a different full screen window and count to 15. This number might change for you. I also use the windows task manager for this. Anything works really, as long as it's on top of the DCS client If you have a loud GPU, you will hear the fans wind down. That is your cue to go back to the game. FPS should be back to normal. Tested this on: 5800x, rtx 3070, pico 4, 32gb ram

Same here, I'm at the point where I don't even try to open the map. I'm pretty sure it's a memory issue, either VRAM or normal RAM. It's pretty clear DCS doesn't clear assets from memory when closing the map. I don't even have MSAA on to begin with so the proposed solution is not an option. EDIT: After a bit of debugging i noticed the biggest offender is Syria map because it's already pretty heavy as is. I have a 8gb 3070. If I load fresh "free flight a10 c II" caucasus map i use 6.6 gb of VRAM. When i open the map it immedietlyspikes to 7.5 gb of vram and stays there. Even going back to the main menu doesn't deallocate the memory. On Syria it's much worse because it simply doesn't have anymore memory to work with. 7.8 GB of VRAM and 32/32gb of RAM used up when i open the map. Why is memory not deallocated when closing the map ?

This is most annoying on Pico4. OpenVR works better through VD since you don't have to deal with SteamVR because it uses the Oculus runtime Sad to see support disappear without any warning or acknowledgement.

I wouldn't call this a bug but more of a feature request. Please consider that not every VR headset has the same FOV or clarity around the edges, Rift S is an example of this. Having something like in the KA-50 would be perfect