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:
When I’m on my cruise level and set the altitude for descent, the TOD marker on the ND moves forward.
Provide Screenshot(s)/video(s) of the issue encountered:
weird atr42 TOD behaviour - Clipped with Medal.tv
Detailed steps to reproduce the issue encountered:
Climb to cruise. Set lower altitude for descent. See how TOD marker moves forward on ND
PC specs and/or peripheral set up if relevant:
Build Version # when you first started experiencing this issue:
World Update 13 (1.32.7.0)
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?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
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:
Same issue
If relevant, provide additional screenshots/video:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Exact same issue.
Provide extra information to complete the original description of the issue:
As OP states, decreasing the alititude via the dial moves the TOD further out.
If relevant, provide additional screenshots/video:
I have seen this on the 72.
1 Like
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:
If relevant, provide additional screenshots/video:
The TOD is not always shown, and when it does is not where it should be. The VNAV should be overhauled. I think the TOD only calculates the final altitude and not all constraints.
2 Likes
Also happens with the ATR72
2 Likes
I think it might also be related to the bug that the plane does not get the altitude correct when the standard pressure is set. When I do that, the plane levels of at for example 19800 feet instead of FL200. When I set a vertical speed to further climb it will climb a little bit and then it also registers the cruise (you can see the speed target change from 180 to (I think) 220 or 240.
Weird that this wasn’t found during testing (assuming this thing has been tested by others than the dev)
I found that if you press B after setting standard altimeter, the plane will reach the final cruise altitude. This is a workaround.
1 Like
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:
Additionally if you set a custom alt constraint in the FMC it calculates it, displays T/D marker, and when changing altitude on the mcp the T/D moves
If relevant, provide additional screenshots/video:
N/A
Is anyone still experiencing this issue in ATR Update 1.0.8?
yes, it is present also in the latest update 1.0.8. Only solution is leave the altitude unchanged until the VPATH profile appears on the PFD. Only then U can lower the altitude and engage VNAV or VS. If U lower the altitude before that, TOD will move further away and the vertical profile will never appear on PFD.
1 Like
yes, i understood.
the fact is that in this simulation the vertical bar appears exactly at TOD and not 5 minutes before it.
So , as I said, U can lower the ALT value only after passing it.
can be listed as another bug:
VDEV showing too late
1 Like
Do you have the same issue if you follow the OP’s steps to reproduce it?
Yep - same problem
Provide extra information to complete the original description of the issue:
did uninstall all mods, no change in behavior
If relevant, provide additional screenshots/video:
In my case this happened less than 5 mins before tod. I will retest tonight.
Tested, but can’t see the TOD marker at all now anymore
edit:
Now that I think of it, the TOD marker did appear while I was enroute. But then I entered two more waypoints and I think it disappeared then. So this test is invalid.
I’ll do another one now. Same route, LFBO to LFBO, via FIST6C - PIMQO - BELPA - AFRI7N at FL90.
edit 2:
There’s no TOD marker in the ATR42 on this flight
So really, I cannot test if this problem has been fixed because the TOD marker has disappeared from my planes.
1 Like
Voted - it happens to me too and it is major bug for now I believe
1 Like
It is correct behavior according to real life pilots.
