WolfTangoFox

Disabling the OpenXR Toolkit didn't do a whole lot for me. It did work for a few seconds longer than before, but still crapped itself before everything had a chance to load in properly.

I'm running Pico 4 via Virtual Desktop on a 10900K, 4070, and 64 GB of 3200 MHz DDR4. Yesterday I did a fresh Windows 11 install and was setting up DCS and other things. I fired up the Hornet "free flight" mission, because that's a known "benchmark" to me for testing VR, and I was getting the expected 80-90 FPS. I then fired up the F-4E "takeoff" instant action mission (the one right above free flight), and virtual desktop crashed completely while loading the world. I tried again and got the same result. Sounds like a very similar issue and a very similar direct comparison to another module. I expected the F-4 to be heavy of course, but running at all would be a good start.

Seems like the new FM is very polarizing. I've found it easier to achieve and maintain on-speed AoA, but I did notice the E-bracket can wander during turns. This just reinforces the need to find the on-speed AoA before the turn, and trust it.

Same here, unable to change the code, kneeboard shows 0000.

Tried both DLSS and DLAA, looks the same in terms of ghosting. Didn't investigate much further so didn't bother looking at FPS, didn't have head tracking enabled either. Just twisted some dials and switched screens on a static aircraft. So can't really give you any numbers on that.

Don't know if it's GPU dependent, but on my end I still get plenty of ghosting. Perhaps it's slightly different, but there nonetheless. Oh well, back to MSAA.

Certainly a DLAA/DLSS issue (not using DLAA because of it). I doubt anything can be done about it on the DCS side of things, it's more of an Nvidia issue.