I changed the title because F10 was placebo. Tried SteamVR as my runtime. Less tracking issues but more VR issues. It might well be that I just need to quit the Rotorheads server. I’ve always had issues with it. But I figure with the new PC build, I could swing it. Anyway, not a bug. Just a player and his PC swimming in a pool that’s too deep.
This might be VR only and also maybe MT only. For me, a Quest 2 user, the bug works like this: the flight is progressing fine with liquid smooth frames until one hits F10 to peek at the map. When back to 3D you notice either an immediate degradation of performance (frames, tearing, tracking) or one that gets progressively worse within a few minutes regardless whether you ever use F10 again. With the Quest, the performance loss comes with a slight loss of tracking, which sometimes persists all the way back to the 2D DCS GUI. If you look left and right, the screen drags slightly left and right as well—VERY nausea-inducing. Sometimes this corrects over time. Usually DCS needs to be restarted. (I can also temporarily cure it with passthrough, but the problem returns within minutes). There is a thread about this on the DCS forum but it only has a few responses so this may not be a universal problem among players. Respondents included Reverb and Pimax users. So it doesn’t seem restricted to Oculus.
So far the only cure for me is to avoid F10, especially if the mission is resource-heavy.