[VR implementation for MFS2020]

For me, Aivlasoft is a much better tool than Navigraph, but I mostly fly VR so...

With all respect, but I think Aivlasoft should really start thinking about porting its code into a more flexible platform that supports

mobile apps and VR  before it's too late.

Especially VR, because it will become dominant in flight simming over the the next coming years.

VR investments and progress are rapidly increasing. 

[Decision Height and Decision Altitude]

Thanks for clarifying. I guess the way you've implemented DH/DA is even more readable than original approach charts.

So I suppose in the cases that  FBW320 MCDU only gives the option to enter DA (baro), it won't be a CAT II or III approach. 

[Decision Height and Decision Altitude]

I'm in the 30 day trial now and I love it.

This software is so much better suited for flightsimming compared to Navigraph charts.

Everything feels more convenient and organized.

One thing I was wondering. I read that the AIRAC cycles don't provide enough data to show DA and DH for all airports so standard values are used

for certain airports. That's ok with me. However, the approach charts only show Decision Height (RA).

Isn't it possible to also show Decision Altitude?

In the FBW A32x, sometimes you can only enter Decision Altitude(baro) into the MCDU approach data.

 

Thanks

 

[edit] I just noticed the Airport Elev(1046ft) so you can quickly add RA to get DA, but displaying DA in the bottom tablw would be "nice to have"

[edit2] Now I also notice , it's either showing DH or DA. (would prefer to always see both)