RealDCSpilot

Alright, little update from my end. I had a strange binding config incident with the latest patch. After deleting the config files and restart to reset them, i found a new alternative binding for Aknowledge/Recall (never seen it before). With Aknowledge -> Neutral and Recall -> Neutral it works like before and snaps back to middle position.

Sooo, no idea what that was but after deleting the config files and rebinding everything from scratch the axis invert works again. Really strange because everything was normal a day before the patch and then this...

Available now in special options!

This is available now in special options.

In axis configuration the axis invert tick box has no effect anymore.

No it doesn't work correctly. It was a 3 position flip switch, if you press up or down it always returned to the neutral middle position by itself. You could press it for Aknowledge or Recall and then it would flip back to the middle. This stopped working a long time ago. Now it stays stuck and doesn't return to middle position by itself anymore.

Okay, after some testing i may have found the antidote for this particular problem. As soon as DCS framerate is crashing down and SteamVR's performance graph only shows purple all over - do this: take off the HMD. As soon as the HMD's user presence sensor is triggered all will settle itself again. This seems to be by far the fastest method to get back in the game again. Sadly there is nothing to prevent this at all, it will happen sooner or later. But at least there is something that doesn't need the game or the whole system to be restarted. I hope the switch to Vulkan will lead to better memory management in DCS.

It's somehow working again. One very strange issue was also that all codes started with "0" and there was no way to change it. I can only hope that RAZBAM is soon getting back to it and continue to work on this impressive module.

Alright, now i've seen it in action. It really is the Shared GPU Memory. Without DCS and/or SteamVR running it's about 0.1 GB usage. Having DCS running over SteamVR it's slightly increased at 0.2-0.3 GB. But eventually there comes a moment when all goes bonkers and this value goes up to 0.7 GB. Then it needs around 30 seconds or up to a minute to settle itself and everything might come back to normal. This really never happens with any other VR app or game or i never reached this point with another game than DCS. :(

I simply don't use the Nvidia app. My first fundamental step of performance optimization is to use NVcleanstall to get rid of all Nvidia bloatware and stuff that i never need to have on my system. Nvcleanstall takes Nvidia's huge chunk of driver package, distills the components you choose and recompiles the installer. In normal cases you would only need the pure driver, HD audio and PhysX. The latest NV driver versions, also include the now implemented newest DLSS dll files which are now installed system-wide on your computer. In NVCleanstall this component is a bit strangely named "NVIDIA DLISR". Once you have everything installed correctly, you can simply start the latest Nvidia profile inspector tool and apply the DLSS 4 override globally on your system. (Or for each single game profile, your choice...) There are at least 5 settings in the profiles that need to be set after each new driver installation. Simply check my post and the video in there. As far as i know and how i see it working on my end, ED has nothing to do extra for it to make it work. They still need to have the DLSS API implementation and distribute the dll files with the game, but each Nvidia owner can now choose to make the system wide override that totally ignores those dll files.

Yeah, it also makes the 1000 Mbps mode possible when going over a USB 3.0 10G cable. Looked pretty good when i tested it last year. However, i'm back to tethered VR since Sony released the PCVR adapter...

@mbucchia Thanks for taking the time to answer. I will take a closer look at what is happening with shared memory over time. However, i really hope ED is getting it right with the switch to Vulkan and implements better memory management. It's unbelievable how bad DCS is in this regard in the year 2025.

The problem is back again, seems to be brought back by the latest patch. Was trying to work with GBU-12s yesterday on 4YA with hot start spawn. No chance of getting the laser to work.

If you use the easy global override method (only change settings in Nvidia Profile Inspector, no DLSS swapper tool used, no NVIDIA app needed, no manually copying DLSS dll files), you will always have to check and/or make the settings again after each driver update.

Actually this issue is bugging me since years and over several generations of different VR HMDs i had. Only if i didn't had to use SteamVR (like Virtual Desktop over VDXR on a Pico 4 (later Ultra)) it wasn't occuring. It's always the same behaviour, after a certain amount of time, i can't call up the Steam VR dashboard anymore without getting it to freeze or becoming extremely unstable or eventually crash. Strange thing is, DCS is still running fine in the background, so whenever i can manage to switch back to DCS, it's running fluid VR again as if nothing happened. The thing is, no other VR game shows this issue ever! Even the other big flight sim. My suspect at the moment is only the excessive use of VRAM that DCS is infamous for. It might interfere heavily with SteamVR's own ressource management for dashboard functionalities (access to Windows desktop etc). I would like to ask a pro like @mbucchia Can you shed some light on this?