You should pre-select your descent altitude only when you are in descent mode. Usually it should engage about 5-10 nm before the ToD and you can see it that when the PFD show the glideslope for the descent and the the central MFD display a prompt for the descent checklist
As the comment below your post suggest. This is actually a correct feature.
When you reset the altitude in you autopilot to lover than your current cruise, it will show you a new TOD based off your new altitude selected. This is how it is in the real aircraft.
There should then be a white circle once you start your descent to your new altitude to show where you will cross your selected.
I must be missing something here. On the Garmin G1000, G3000 or the Proline 21 in the CJ4, TOD marks the place where you need to start the descent.
Not so in the ATR: the other day I was at FL140 and my target altitude for the next waypoint was 10 000 feet according to the flight plan. The TOD marker was a white circle and it was exactly where the next waypoint was. How can I possibly descend from FL140 to FL100 in an instant?
Sorry if Iām being an idiot, but I donāt get the logic with the ATR - unless itās a bug
If the waypoint was set up as above 10000, the ATR may decide you donāt need to be at 10000ft at that waypoint. Only if the waypoint was set up as AT, or BELOW, 10000 would you actually need to be at/below 10000. So that may be normal behavior. There are lots of STARs where you just have to be above a certain altitude and the aircraft will typically be looking at waypoints at the end of the STAR, setting up a 3 degree descent to that, and then making sure it doesnāt violate another constraint on the way down.
The waypoint ALT was indeed ā10000Aā in the flight plan on the FMS, so this could be the explanation. Thanks! Iāll do some testing tonight and see what happens.
Canāt say Iāve come across this behaviour in any other plane though, but I do fly mostly GA.
Yeah, that would explain it. I see this behavior all the time in airliners (I primarily fly the A310, A320, B737). Some STARs may say to be above FL200 and Iāll still be at FL300 when I hit the waypoint, just because thereās no need to descend all the way down to FL200 that early in the descent profile.
This seems made on purpose. The windows have a sort of semi-transparent layer, maybe against sun glare.
The effect looks very realistic to me (though I have never been in a real cockpit) but at dusk I agree there is a lot of cabin light reflection which blocks most of the outside view.
I hope some real ATR pilot can confirm whether these shades exist in the real aircraft or notā¦
yeah iām not sure either as i donāt have any real time in an ATR but i can only assume the side windows donāt glow like that at night from inside the flight deck lol
Anyone noticed that the 42 and 72 descend roughly 200 feet below the glidescope when flying an ILS approach. Altimeter settings were double checked and correct. Makes no difference what livery is used and happens with an empty or populated community folder.
Interesting list of fixes, does it now accept in game flight plans from the world map?
Or is this plane still incompatible with the sim it was made for?
Last time I tried the flight plan in the world map did not transfer to the ATR. Tried to report it as a bug but one of the moderators moved it to the wish list. Unsure why basic functionality of the sim would require a wish list to get it added to the plane. Especially when the functionality has been supported for a 3rd party system that uses older navdata cycles then the sim itself unless you are willing to pay a subscription to them.