Hi, PMDG FlyersI am entering Custom Waypoints in the FMC (Place Bearing Distance format) and can

Can I suggest you read the FMC manual? Here is page 31http://forums.avsim.net/user_files/53368.jpg[h4]Best Wishes,Randy J. Smithhttp://www.precisionmanuals.com/images/betaimg.jpg

What's your point, Randy?The text clearly says DDD.D is acceptable. When he enters that, because his waypoint occurs more than once in the database, the FMC presents a list of choices, and then seems confused presenting no choices and page 1/0.Lee Hetherington (KBED)http://www.precisionmanuals.com/images/betaimg.jpg

Hi, RandyThanks for your fast response.I am doing this flight whit the

I am not convinced one can actually input this format on the LEGS page. The AOMS clearly state " Waypoints entered as place-bearing/place-bearing are indentified by the first three characters of the entry followed by a two-digit sequence number. FIX page maybe?.........[h4]Best Wishes,Randy J. Smithhttp://www.precisionmanuals.com/images/betaimg.jpg

Just checked and it works at least in distance. Also noticed that you are from Argentina, check if the decimal point in windows is . or ,. Some times this problem also happens in com or/and nav frequency values. Could be it.Jos

"Waypoints entered as place-bearing/place-bearing are indentified by the first three characters of the entry followed by a two-digit sequence number."Well Randy you might consider looking at his screenshot again:He is trying to enter a plcae/bearing/distance waypoint and not a place-bearing/place-bearing wpt!Mark

Thanks Mark, glad to see you have joined in to help in this discussion ;) Let me be a little more clear, the TERMS place-bearing/place-bearing OR place-bearing/distance in REGARDS to my above statement is CORRECT for either, i.e. the same format is required for BOTH. http://forums.avsim.net/user_files/53391.jpg [h4]Best Wishes,Randy J. Smithhttp://www.precisionmanuals.com/images/betaimg.jpg

>Just checked and it works at least in distance. Also noticed>that you are from Argentina, check if the decimal point in>windows is . or ,. Some times this problem also happens in com>or/and nav frequency values. Could be it.>>Jos

Randy, the two-digit sequence number they are referring to is the 01 tacked onto the fix name ELN to form the new waypoint name ELN01. It says nothing about digits specifying the distance.Lee Hetherington (KBED)http://www.precisionmanuals.com/images/betaimg.jpg

Hi Randy,As Lee already said, the two digits refer to the custom waypoint name that was created by the FMC. (ELN01 for example). Distances can have decimal points. Unfortunately, I don't know how many digits the distance can have though (is 100.1 or 1000.1 or even 10000.1 accepted?) All I know is that the real FMC definetely accepts 7.5 or even 70.5 for a distance.Regards,Mark

Hi, Jos

>> As an example, if you enter SEA as reference waypoint (alone>in the FMC Database Waypoints) there are not problem entering>Place Bearing/Distance Waypoints whit decimal places. But whit>a reference waypoint as MIA (are some MIA in the Database),>you can

Ok, I got it now. Tim was correct. Bulfer says decimal entries are ok. I tried this on the 737 trainer with MIA which does bring up a choice of waypoints, I typed MIA334/7.5 Clicked on the correct MIA on the list and it worked. So yeah it's a Anthony call ;) [h4]Best Wishes,Randy J. Smithhttp://www.precisionmanuals.com/images/betaimg.jpg

Hi, TimothyGlad to have you in this thread. You are right Tim, Bering don