lemoen

What is your DCS VR shortcut's command? the --force_oculus option doesn't work with MT I think you need --force_enable_VR

Check in Oculus software if your runtime is set to openxr.

I have a similar problem with the Virpil CM3. When the throttle is in cutoff, it "holds" the cut-off button and releases it the moment you move the throttle forward. Seems to be only an issue in the EE, I have to click the throttle in the cockpit to move it to idle then move my throttle to match.

I'm in VR, away from the airfield it goes to 72fps on my quest2 and stays there mostly as I would expect given the graphical settings I have, but when I'm at the airfield or looking at it like when I come to land, it'll drop to 18fps. I think it has something to do with the shadows bug that is in the current version of DCS, those 6 or 7 planes really shouldn't have that big an effect on the performance.

Anyone else have terrible fps at the airfield? I had to remove the non-player stationary Mirage F1's from the mission which fixed the issue. It was drawing 25-50M triangles with those planes in the mission, without them about 4M

Run a repair.

I have the same, but on mine even more is cut off, can only just see the red arrow above the cutoff.

Some of the missions starts the Helo in a state where the left pedal is trimmed some ways, and full right pedal doesn't give you the full right tail rotor. I've now started hitting the trim reset button as I get into a mission. I'm not using rudder trim.

+1 The situation is getting pretty desperate in VR.

Using up more than 8GB of VRAM at low settings is clearly unwanted behaviour. Maybe the video manager isn't aggressive enough in cleaning out unused stuff, or maybe the art assets have components in them that has too high a resolution, we can only guess but we really should plead with ED to look at this and improve it, because along with that will come increased performance for everybody, even people with 24GB cards.

So it looks like Airlink just uses less resources than default Link settings, but this same thing happens on Airlink too. I had to set everything to low, disable MSAA and reduce the render res to 0.9x to get Blue Flag PG to stay inside my 8GB VRAM. My GPU was running at 40% usage at this point, there is clearly a large divide between the amount of rendering that needs to be done and the amount of memory it uses while doing so. ED please please please look at this excessive VRAM usage.

Good practice for Raduga-Sh sight

After some more testing I found out that when using Airlink, DCS still goes over my allotted VRAM, but the 100% GPU usage and subsequent glitching does not happen in the same scenarios as before, even with higher graphical settings that will use more VRAM. So I suggest for those on Quest 2 with this problem to test Airlink.

OK tried HIGHER settings than before, but with Airlink, same rotorheads server, scenario was similar. Still saw high VRAM numbers but the fps stayed stable and no glitching. I suggest to Quest 2 users to try Airlink instead of link.

I see you're using Airlink and don't have this issue. I wonder if there isn't a difference between that and Link system, where maybe the Airlink stream uses a lot less VRAM to be prepared. In every single case I had this, my total system video memory was clearly over 8GB but at least a few 100mb, and I've just been using Link because for the most part its the same but airlink eats the battery much faster. Some things I can try later...