zildac

The main benefit of these are the savings in VRAM, if you're not VRAM constrained then the performance benefit will be minimal if any.

The only way at present is to use the mod to make the NVGs fullscreen.

Yes

This issue was also present in the initial MT release when used with Tazs MOD.

All of them sequentially is my understanding.

@Alpha Juliet This issue appears to have resurfaced since today's OB update 2.8.8.43489 Firstly, my COM1 and COM2 binds were gone for the AV8 after the update. Once added back in the menu works, however the old behaviour allowed you to close the menu by selecting the same COM channel again. Now, this does not work. You have to click on F12 - EXIT.

This has been the behaviour for many months. Uncaging the IMAV kills off the TPOD display. Process I follow is: 1. Designate with TPOD. 2. Uncage MAV (TPOD goes) 3. SS Forward (switch from iNS to IMAV mode) You should now be able to slew. 4. TDC depress. 5. Launch

As far as I'm aware, no.

I think what @speed-of-heat has said is correct. It looks like you are still trying to control your pitch using the stick. You need to set your AoA with trim and use solely the throttle to control your rate of descent. You shouldn't be porposing like that, and likely the hook bounced and the AoA was wrong. Just get used to controlling your speed with your pitch (via trim) and your rate of descent (or ascent...but you shouldn't be climbing) with throttle. In a GA aircraft, this is akin to "slow flight". It's challenging, but once you get it, it will stick and you'll trap. Not sure if the attached track will play (it's quite old) but this is the general idea. OK scratch the track...it was a 72 but on playback I'm in the sea! The joy of the track system. Bankler-72-1.trk

Is this still needed with the latest core and updates? (Specifically AV8) Disregard...the lack of an overwrite prompt in OVGME suggests it is.

Share a track if possible?

Unfortunately this is a limitation of DCS. I asked a similar question a couple of years ago.

Agreed, I used to have it switched off. Have been running with it on for a couple of weeks and I see no obvious benefit nor degradation in performance as a result.

Agreed, the limit function is the only MP safe way.

Uninstall the old versions and install this: https://github.com/mbucchia/Quad-Views-Foveated

This is correct.

Out of curiosity, for those who are having the issue, what do you get when you run the OpenXR runtime switcher tool? https://github.com/WaGi-Coding/OpenXR-Runtime-Switcher

Launches fine here V20SP

Slow load times appear to be fixed.

Its fixed for me. But no mention in rhe change log.

Yes

You beat me to it

As of two days ago there is a new version of Foveated that supports OXRTK. See here: https://github.com/mbucchia/Quad-Views-Foveated But in answer to your question, no. I was using the previous version of Foveated, MT and had OXRTK disabled.

Same here latest OB and Varjo Base and no issue.

Excellent news!