Schmid,

I have been really pleased with the FMC of the new version as before I could not finish a flight in 6 months due to the CTDs. �That seems to be history now.

I have found no problem with setting up STARS, ILS approaches, and SIDS when at the departure airport. �However, the FMC does some odd things when you want to change the runway or approach near the end of the flight. �You have to pay very careful attention as to what waypoints it puts in and make sure that the route is correct, waypoint by waypoint. �Sometimes the runway is added to the end of the route, sometimes Vectors is added in the middle, sometimes waypoints are doubled up, sometimes the current route gets erased and replaced with the ILS approach, and the altitudes need to be checked too, but it is all fixable very quickly for someone with your knowledge of the FMC. �I also am pretty knowledgeble and got caught up by this on an approach when trying to change from Rwy 27 to 18C into EHAM last night. �It took me like 3-4 tries to get it right and even then I missed one odd waypoint that I didn't catch until the last minute. �It definitely is not what I am used to after flying other aircraft, but, well, that is life, time to get used to something else

However, I have to say that other than a few quirky things, the FMC seems to work pretty well. �I wish a few more things were modeled, like ALTN, �MENU, calculation of distance to TOD, for example, but I am happy with it. �The FMC not calculating CG and giving the required takeoff trim is inexcusable though, really. �I have figured this out by now after having taken off a few times with trim values in excess of 6 when it really needs to be 2-3 �We are not used to CG values of 40% but...well..now I am.

Happy flying to you.

I don't use Navigraph updates, partly for the reason that you talking about.  So can't help you with that one.

By the way, I am talking aobut the normal distance to TOD seen on the VNAV cruise page, and distance to first altitude restriction seen on VNAV descent page.  I always have a full route input even if I have to change it later.  I will be coming up to a descent here in a few hours.  I am flying todays Saturday Scramble into the NY area, KPHL to be exact for EHAM, should have full ATC.  I will be able to give it a full shake out and hope I am not the one shaken out.

Schmid, maybe you could ping Carsten Rau for me, please.  I am seeking permission to link to his 757 checklist.  If that's okay, fine, because he did a fantastic job.  If not, that's cool, too.

I haven't had a chance to try out the Siberian Bomber Base to PANC yet    Or anything else.  Still messing around on the ground.

Has anyone tried to create their own STARs using the material at the back of the FMS manual?

Bill.

Now SEGU to SPZO. Page 1/2 of PROG.

All there: DTG, ETA, FUEL and distance to T/D.

Schmid

Yes.  If I could have found an email address I would have.  He is on the IVAO forum, but I can't use that.  If it is easy, thanks, if not, no big deal.  He has a great checklist for the 757.

Just type in the waypoint name to the scratchpad and enter it into the first line of the Legs page and activate (execute) it. �If you don't know what that means, you most certainly need to read and understand the manual or get the info by some other means such as by a tutorial if you don't like reading manuals.

The manual does describe how to do direct to wayponts.

Oh, sorry, you did say that you can't make any sense of the manual so I wasn't sure what that meant really as going direct to a waypoint is just about the easiest thing you can do with the FMC. 

You are right, if the waypoint isn't in the database then you can't really go to it by name.   If you know what the lat/lon is for it you can add it in this way.  This is what I do if a waypoint on a STAR, for example, is not in the database.  I am not familiar with that "Move" feature.  I always manually enter in all my flight plans so have not imported any in nor run up against this problem really.

I have the not in database problem as I don't update my databases with Navigraph every once in a while but it is not a huge problem as there are a huge number of waypoints in the database. The default database that came with Ver 4.3 seems fairly current to me.  I have to do a lot less of this adding in waypoints by Lat/Lon than I do with other aircraft.

Well...good luck.