Glide

Currently, if you wish to reject a locked target you press TMS down. This rejects the target and puts the ACM mode in vertical scan mode. This requires another action to put the ACM mode back into boresight mode. It would be ideal if you could reject a locked target and stay in boresight mode. The hat switch is 5-way, so TMS could be mapped to fore, aft, port, starboard, and down. For those without a 5-way switch, they could map a key to TMS reject.

They will win every time. Don't be fooled.

I still see the wobble on the leading edges of the wings of the TF-51D, depending on what kind of textures are behind the wings.

You will always have the ground stutter with those settings. Trust me. I didn't test clouds, since I turn them off. Vis Range LOW, AF off, AA, off, terrain shadows OFF. The issue is in the graphics pipeline.

Whatever. Try just the game settings then. Vis Range = Low, Terrain shadows off, AA off, AF off.

I assume you have DCS set up to launch with OpenXR using the shortcut parameters. I have my G2 set up for maximum quality, and see below for WMR settings. OpenXR Toolkit should be at defaults for this exercise, but you can use the excellent FPS counter on Advanced. Your NCP settings for DCS should be restored to defaults. As for the Quest Pro, try to match my setup if you can. The resolution is already lower than my G2 at 50%. Set your game settings just like the screenshot, and hop into the TF51D on the Caucasus map. Report results.

And thanks to your trolling, the OP won't even try them. So, I guess we'll never know.

Try my settings here: Basically, 50% OpenXR custom resolution, no Motion Reprojection, no NCP settings, no OpenXR Toolkit settings, and the game settings I have posted in that link. They may not be the best looking settings, but you will know if you can achieve 90fps with perfectly smooth ground motion. They look just fine to me.

Still there in this patch.

True. The Mig-29 and Su-27 have them as well. They animate on the F-16, but I'm not sure they provide the added lift during high AoA.

And you say when you watch the track it returns to center? Are you using the mouse or a key bind with yours?

Does anyone know if the leading edge flaps are modeled in the FM?

So, it's supposed to stay in the up position?

Track File uploaded. F-16 Drift CO Switch Not Toggling Syria.trk

I swapped these guys into my favourite dogfight mission as Redfor AI, and they are super fun to fly against! Nice work!

The Drift C/O switch used to be a toggle, but now it stays up in the Drift C/O position. Not sure if that's a bug or correct as is.

I don't think it's quite "correct" yet with respect to the sim, not the real world. The Mig-29 has a lower thrust to weight ratio, but it can escape from my F-16 no problem. So, relative to the other jets in the sim, I think it needs more get up and go. As for the FM, I just learn to fly the FM they give me. The performance improves as the weight drops off with fuel burn, but I still think it needs a higher rate of acceleration.

Can anyone tell me how I got this new symbol in the HUD? It seems to appear after I've released all my Sidewinders.

Would Virtual Reality pre-rendered frames in the NCP have any impact on MR?

DX12? I'm pretty sure DCS uses DX11. Turn off AA and AF because MSAA is outdated, and AF only helps with the lines on the runway. Turn off shadows because they are still broken. And as mentioned, turn down the resolution. I run my G2 on my 3080Ti at 75% custom resolution in OpenXR developer tools, and this is the best I've ever seen DCS in VR.

How much RAM do you have?

I discovered something interesting about my hub yesterday. I started getting BSODs and after a memtest found my memory was failing. (Replacements on order). So, after powering down the unit, I thought to hit the switch on the power supply, but the motherboard was still glowing. I unplugged the power supply, but the motherboard was still glowing. I unplugged my powered USB hub, and the motherboard stopped glowing. The powered USB hub was feeding power to the motherboard. I don't know if this contributed to the early failure of my memory sticks, but the hub is gone from my setup now. I hope this helps.

That could be your target FPS (ie. What the headset wants to achieve vs what it is achieving), if you were running your headset at 60hz, like I do with my G2.

Get a small desk fan. I have the Varnado which is quite effective and not very noisy.

So, I am not sure how the label issue came back, and I have not reproduced it yet. However, I cleared the Environment Data in Mixed Reality Portal and it went away.