Hello everyone,

I have got the Captain Sim 757/767 for a long time now but one problem keeps accouring. The Top of Descent does not appear! Everything is set propperly in the FMC but still it does not appear. I have the 767 version 1.5. Can anyone tell me how to fix this? 

Thank you!

Greetings! 

Hi,

i have the �Version 1.5 and tried it several times but it does not work. �

Greets

I am at my wit's end with the 767 and the Top of Descent Bug.

I do the trick, and indeed the proper altitude (and speed!) shows for a moment, then switches back to no TD. I have tried waiting until I hit erase, changing waypoints... nothing works. What is really frustrating is that I can see the right values, but only for a second. And we're back to cruise just before the airport.

What a shame such an otherwise nice airplane is plagued with such a frustrating flaw.

You're lucky. The maddening thing is that you can SEE it switch to the proper altitudes, but it doesn't "catch," so it "snaps  back" to a plan without a TD. So clearly it "knows" what it is supposed to do, but for some reason it can't bring itself to do it. I confess I finally gave up on the 767 over this issue. It is character flaw in me that I find it difficult to shrug off things like this. An FMC that can't reliably do the bare minimum of handling a route with basic VNAV just isn't going to work for me.

Don't get me wrong, I like Captain Sim and have most of their products. But a TD bug that was driving me nuts nearly three years ago should really be fixed.

Where do you get your routes? Is it possible you are doing something different than other people are doings? If you fly much at all in the Captain Sim 757 / 767 then odds are you should have run into it, but you haven't. What's the difference?

I have the same issues sometimes with all three of them. Sometimes, when the fix does not seem to work, it helps to change to a different STAR and runway. Also it helps to first program the sid and departing runway, then the route, star name as last waypoint. Then go back to dep/arr section and type in proper runway from the given star in flightplan.

I use the freeware version of Routefinder.
Annoying bug, yes. But in the end I normally find a solution, one way or the other.

Br,
Anders

The difficulty in what you are suggesting, Raymond, is that the waypoints maintain the CRZ ALT, then you might see a waypoint with an Altitude Constraint, then the next waypoint display the CRZ ALT again. So you might wind up in a very shallow descent until you reach the airport, because it doesn't know where the T/D is. The T/D doesn't exist in the route, so can it know where it is? Still, it is definitely worth trying. I have not yet tried it, but it could turn out to be another "fix"!

The problem appears to be that the FMC does not know that at some point you want to reach RWY XXX at (lets say) 20 feet ASL, so even with Altitude Constraints in the latter part of the STAR, it still believes it has to fly at Cruise Altitude beyond the arrival airport (until END OF ROUTE is reached).

In my fix, I will try a waypoint to remove, then erase the change after anything from 10 seconds up to 60 seconds. If that fails, I try a different waypoint to delete, then erase the change. I can sometimes try doing that with ALL the waypoint in the STAR and TRANS!! Other times, I will remove the the altitude constraints that use the A (at or above) or B (at or below) until I get it to hold change and retain the T/D. In the end you can force it to accept the change. In the worst case scenario, I scrap the STAR and just select a runway to land on (i.e. 16, 34 etc.) without the ILS GPS or RNAV associated with the runway. I take note of the waypoints and any constraints in the STAR, and add them manually. In the end, I get my T/D on the route.

If you get impatient, do not expect to get a result. Having said that, if I get frustrated, I fly somewhere else where I get my T/D in the route. Or at worst, I change aircraft if I get p*ssed off enough with it. So that tells you that even I can lose it with the CS 767 (and the 757 which suffers the same problem). In truth, I get better results in the 767 than I do in the 757, so the 757 is worse for me, so I fly it a lot less.

Tim Capps wrote on Nov 18^th, 2013 at 6:52am:
Not necessarily. I may have switched to another CS aircraft. But it would be one that doesn't have an FMC!

Tim Capps wrote on Nov 18^th, 2013 at 6:52am:
MD 80? The only one I have from a long time ago, has a "Lite FMC", and I no longer use it.

This Sao Paulo - Santa Cruz flight is just cursed for me. It is an interesting flight if anyone wants to try it. Start off with a ridiculously short runway. As you speed toward the end, you have to have total faith that your VR speed and the laws of physics will get you in the air before you run out of runway. (Take a full load, said management. On paper that runway is long enough!)

Then it's a perfectly straight line through intersections with lovely names like "MUCUS" ("sorry, all the good names have already been taken, Brazil"). Then a crazy-complicated (for me) procedure at the end.

Once I ran out of fuel fooling around trying to follow the procedure. Another time I tried to show my son my 727 and managed to change my 757 into a 727 in mid-flight! With no engines! That didn't end well. Another time I just bailed out of frustration. ("This is your Captain. I'm leaving. Good luck.")

"The Curse of Flight 812." But break it will I. And, Mark, yes, that was a nice-looking but lite MD-80. It still tempts me once in awhile, but it is just a pretty model bolted onto the default autopilot.

I am hoping really hard that they will get the FMC lined out. From my perspective, the 757/767 are perfect and don't need anything new. Just FMC fixed.