Here's a situation where the TOD was coincidentally located at a waypoint, and the aircraft failed to descend even though it was in VNAV mode and the MCP altitude had been reset to a lower altitude.http://forums.avsim.net/user_files/37494.jpgTake a look at the PROG page - the distance to the TOD stopped at 0.7 NM even though we were now flying away from it. This must have been the distance at closest approach.http://forums.avsim.net/user_files/37495.jpgI assume this happened because the aircraft turned just before reaching the waypoint and thus never got closer than 0.7 NM to the TOD. Presumeably there is a threshold which is less than this.Anyway, PMDG, I'm letting you know about this in case you're not already aware of it. Maybe the software could be updated to take account of this, admittedly, rare situation.

a couple of questions:First, Are you at service update 1-1?Second, did the airplane ever descend on it's own? Third, can you reproduce the problem? If you try the flight again, a shot maybe a few miles before the T/D point would help. Also, if you could send your flight plan or uploade the .rte file after saving it, some of us could try to replicate it.I notice the vertical path deviation indicator isn't displayed - so it appears that you're not at SU 1-1 OR the FMC hasn't gone into descent phase yet (or at all). I belive the indicator shows up a few miles or more before T/D.I expect Anthony Merton will have additional insight.

Hi Craig,A beta tester reported this to me a few days ago.Your analysis is correct about the reason why it happens.I fixed this and TOD sequencing in this situation will occur as expected in SU2.Until then, an easy workaround is to set a higher lower crz alt to make sure a wpt and the TOC do not collide. If there is a course change at the wpt (wpt sequencing will happen earlier), I'd leave at least 2NM between the TOD and the wpt.cheersanthonyAnthony MertonPrecision Manuals Developmenthttp://www.precisionmanuals.com

TimothyThanks for your interest in this problem, although you will see from Anthony's response below that its somewhat academic now.Incase you're still interested I'll answer your questions anyway.1. I am at SU1.1.2. No, the aircraft didn't descend on its own. A few moments after taking the screenshot I used LVL CHG and then V/S modes to initiate/control the descent myself.3. I haven't tried reproducing the problem. The flightplan was LFRS - RNE - UN867 - BARLU - UN861 - FAWBO - UB11 - KATHY - EGKK. The cruising altitude was, I think, FL330 (whatever was in the screenshot). It wasn't until I entered the STAR for a landing on rwy 08R that the TOD moved to coincide with a waypoint - unfortunately I don't remember which STAR I selected (the flight was performed several days ago and I didn't write this detail down).Anyway, as I said, this is somewhat academic now in light of Anthony's response but thanks again for your interest.

AnthonyCool, thanks very much. Thats a good idea about changing the crz altitude should I stumble across this again.