I have so far not managed to engage VNAV during climb while in-flight. It arms on ground but then is immediately lost in flight.
The VDEV randomly appears, instead of 5 minutes prior TOD.
Adjusting the flight path angle (PERF INIT page) does not affect the TOD.
Cruising altitude should not be adjustable during flight, while correctly displayed as a green value, it is adjustable. Incorrect, cruise altitude selection is automatic in flight.
When in VNAV PATH, the VDEV (left of the altitude) seems to act like a flight director (a vertical speed deviation indicator of sorts) rather than showing the vertical deviation. The VDEV in the FMS is always showing -1 feet, the VDEV centers when the vertical speed matches the magenta bug.
What the VDEV should be showing is the deviation above or below PATH, 250 ft per dot, 500 ft being full scale deflection.
The FMS TGT VS makes zero sense, as can be seen in the video, while diving below the path, the TGT VS increases. When below path, the opposite should happen.
Selecting VNAV after TOD causes an insane 6000 ft/min dive.
It all just seems completely random to me, in any case, this is how it is supposed to work:
With the VDEV displayed, select VNAV to start a PATH descent
Deviate above or below the path, observe the VDEV on the FMS not changing
Now select VNAV back on and observe the VDEV acting like a flight director, it isn’t indicating the altitude above or below path, rather, it centers when the TGT VS is reached.
Note that the TGT VS not making any sense for the deviation from the path.
YOUR SETTINGS
Not relevant.
MEDIA
Cruise altitude green, yet adjustable (should not be adjustable in flight):
Selecting a lower altitude, VDEV appears immediately (here 12 minutes before TOD) instead of 5 minutes prior to the NEW top of descent. Even though we haven’t even reached TOD yet, the target VS is 1900 ft/min and the vertical deviation is -1 ft, despite being on path (VDEV -1 ft) the VDEV indicator next to the altitude tape indicates that we are full scale above path…
Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.
3 tags are required - add them in the tag section next to the title above:
One for aircraft (start typing in your aircraft name in the tag section and pick correct option)
Feel free to delete this quote section after adding your appropriate tags.
ISSUE DESCRIPTION
VNAV in the ATR is still a mess after AAU2.
The Aircraft is not able to follow the VNAV-PATH. It always changes to other AP-Modes.
Normal (if you read any SOPs) is to fly in VNAV-IAS to the TOC. Than it should be in ALT (with VNAV-PATH) armed. When you reach the TOD ist should automaticly descend if you set a lower Altitude wehn reaching the TOD (< 10 NM).
I just cant get it to work! VNAV-PATH always gets deselectet. At TOD nothing happens!
FREQUENCY OF ISSUE
Every flight!
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
Start Flight
Initialise the FMS
Go flying
YOUR SETTINGS
No Mods. Only the AAU2-ATR72
MEDIA
No Screenshots because of constant issues. VNAV-Modes just dont work as the SOPs say.
You cannot arm VNAV on the ATR, as soon as you level-off at ALT SEL, VNAV will cancel (both during climb and descent). So it won’t automatically descend. But yes, it is really borked.
This is how VNAV functions (should function) on ATR:
I have this happening as well. As for the climb, ever since the latest update, it does arm and switches to VNAV IAS mode, but it just ignores any altitude constraint, blows right through it. And it also won’t change to ALT*/ALT as it reaches the selected altitude, instead it remains in the VNAV IAS mode. The speed changes to cruise speed, and it continues to climb slowly at that speed instead of leveling off because it never captured the selected altitude. Disappointing really, after all the years of development, this aircraft still can’t do basic stuff. LNAV also does some weird things, but that’s a whole different story.
