Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons?
No
Brief description of the issue:
PFD and VNAV malfunctioning.
Provide Screenshot(s)/video(s) of the issue encountered:
Detailed steps to reproduce the issue encountered:
Using VNAV during flight
PC specs and/or peripheral set up if relevant:
Asus Tuf Gaming F15 FX506HCB, RTX3050, i5-11400H, 16GB DDR4 3200MHZ
Build Version # when you first started experiencing this issue:
Right after the release/purchase of ATR Expert Series
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OPâs steps to reproduce it?
Yes
Provide extra information to complete the original description of the issue:
ATR gets a strange PFD behaviour then a nose dive causes auto pilot to disconnect immediately, leading the sim to âyou crashedâ warning, couldnât record the nose dive which caused auto pilot disconnect
If relevant, provide additional screenshots/video:
I believe that PFD behavior (the flashing vertical deviation bars at the right?) is trying to tell you that you have not set your altitude target down to allow VNAV to take over. With your altitude still set at 23000ft (in blue above the altitude tape) the plane will not descend.
Please do not partially delete the bug template. It is supposed to be left intact.
Please edit your first post and tag the ATR aircraft that this is happening with.
Please edit your first post and add this to the bottom of your post:
------
:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:
[wrap=template key="Topic_template"]
Do you have the same issue if you follow the OP's steps to reproduce it?
>
Provide extra information to complete the original description of the issue:
>
If relevant, provide additional screenshots/video:
>
[/wrap]
The video doesnât play for me so not sure what the OPâs exact issue is but VNAV is definitely wonky.
When you climb with IAS and VNAV off to cruise altitude and then select VNAV it starts to descend. You kinda have to wait until youâre past the TOD marker. At least thatâs what I encountered on my last flight.
VNAV keeps chasing the path and it almost seems itâs calculating multiple paths between fixes instead of one smooth path from TOD down to the last restriction. This leads to sometimes aggressive pitch maneuvers.
I agree that there are vnav issues. I sometimes get a flashing message on the pfd to select lnav under the vertical nav column and vnav will not activate. Vnav sometimes switches to pitch hold and will not reactivate.
Edit: This may be my lack of knowledge of the ATR autopilot. Apparently, vnav will not engage unless lnav is active. I am still learningâŠ
I have encountered this bug too during VNAV descent. My plane goes to a dive and AP disconnects. Luckily, Iâve got plenty of altitude to handle this issue and I saved my plane.
I have to agree. VNAV is unreliable. Sometimes it seem to work correctly, sometimes it doesn ât.
TOD calculations are often not correct and the aircraft will not match hard altitude constraints by many hundreds feet.
I confirm the fact that it does not follow a smooth path: it seem to follow sort of âladderâ profile (slow descent before a waypoint and then abrupt diving after passing it). Tried several approaches at different 3d party and stock airports: same results.
Furthermore I also observed a âlazyâ LNAV behaviour: it struggles to follow sharp turns ,also at low speeds, and sometimes it does not catch the waypoint, wich is therefore skipped: in this case the only possible solution is to manually insert a DTO to the next waypoint, otherwise FMC will remain stuck to the previous one.
I know this is only 20 bucks but nevertheless i think that an âexpert seriesâ aircraft should behave better than thisâŠâŠby now it seem to me nothing more than an advanced beta.
Hope that Asobo will continue to improve this!
Yes, LNAV and VNAV are mediocre at best!
Takes for ever for LNAV to center the aircraft on correct path.
VNAV sometimes doesnât take alt restriction constraint into account, sometime it does!!!
Also experiencing increasing up and down oscillations of the VNAV path vertical bug resulting in the plane oscillating up and down.
VNAV is also taking the plane way below the gliding path on approach, it would run you into the ground if you had to fly the appr to its MDA!
Hope they gonna continue to release updates for the ATR!
Was released way way too early in my opinion!
Even during the Expert serie Microsoft video ATR 72-600 Discovery series Episode 6 Cruise, Descent
The IRL pilot demoing the ATR is turning off VNAV because it doesnât work at all, time code of the video 6:45
Really hope they gonna fix a lot of the issues people are experiencing at the moment, I really love the ATR (a working one)
The CRJ has many of these same issues. Sounds like the developer used the exact same flawed code as his other aircraft. Why he didnât use Working Titleâs excellent and far more accurate flight plan management system instead is beyond me, especially since the ATR is RNP capable.
VNAV PTH tested again today on the ALBET2E ILS4R-Z (LAREN) approach at LIPZ (Venice).
the FMC PATH calculation is totally messed up, leading to continuos climbs and descents btw waypoints (particularly btw waypoints with WINDOW alt constraints).
Furthermore, after manually setting an hard FMC constraint of 4000ft on LAREN, the vertical path purple indicator started flickering up and down and autopilot almost killed me trying to chase it!
I m afraid, but i confirm that this VNAV is definatly brokenâ:disappointed_relieved:
Do you have the same issue if you follow the OPâs steps to reproduce it?
Yes
Provide extra information to complete the original description of the issue:
ATR gets a strange PFD behaviour then a nose dive causes auto pilot to disconnect immediately, leading the sim to âyou crashedâ warning, couldnât record the nose dive which caused auto pilot disconnect
If relevant, provide additional screenshots/video:
I donât know if itâs just for me, but I notice that this option of being engaged with VNAV and LNAV simultaneously with the ILS is creating a strange bug in the ILS GlideSlope. As you get closer to the runway, the GS starts to slightly leave the ramp and the Flight Director doesnât seem to be worried about it, as it continues to show that it is on the descent ramp. These are things that deserve to be reanalyzed by the aircraftâs dev. Iâm even afraid of what will come in next weekâs Patch. Too fast for too many bug reports.
the FD struggles to follow the GS also with VNAV disengaged.
TRY THIS:
start at KSFO rwy28-R with no flight plan loaded. Take off, right 180 degrees turn, climb at 3000ft and set AP (HDG mode). Fly straight ahead until 12 miles DME from IGWQ loc-ils (111.7) Then turn right again to intercept LOC and arm APP. With correct approach configuration (speed,gear,flaps), the ATR will correctly intercept LOC and GS (LOC/GS green)but at a certain point U ll see the vertical GS green diamond slowly beginning to raise and FD not commanding a climb to recover it.
Try the same procedure with the TBM930 and U ll see the aircraft perfectly stable on both GS and LOC until runway threshold.
ALL the vertical autopilot modes in this aircraft (VNAV AND GS follwing) need some tuning in my opinionđ
Hey Alexandre, thanks for collaborating on this error. I had two situations when using the ILS on the ATR. I noticed that if you intercept the ILS glideslope with the aircraft still descending (descending with VNAV, in my test) it supposedly enters LOC/GS mode and starts to descend. As it descends it starts to lose the GS, and if you look at the co-pilotâs PFD (which is not in ILS mode), the GS diamond on the commanderâs PFD will be equal to the VNAV diamond. Now if you let the aircraft stabilize at some altitude below the GS, it captures and descends smoothly. Well both times I tested it worked. I will reproduce your test.
Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
For anyone who wants to contribute on this issue, Click on the button below to use this template:
