Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Someone please do a quick test furme?

Featured Replies

Take the information below and save it to the file named TESTROUTE.rte and try and load it up in your PMDG 737NGX and see what you get to happen. Do you get ALL of the waypoints in the LEGS page of the CDU?

 

I've gone through two .rte files ... one that works and one that doesn't and I'll be d**mn*d if I can tell if there is one iota of difference between the two

 

I even got to the point where I thought the problem might be a mismatched AIRAC files ... but the NAV DATA for the 737-800WL is AIRAC-1302 FEB07MAR06/13 and the data within FSBuild 2.4 is AIRAC Cycle 1302 (07/FEB/2013 06/MAR/2013) ... exactly the same which is what I would expect because I downloaded the information from both products from NaviGraph.

 

 

HELP!

 

 

Generated by Fsbuild 2.4

14

KMCO
1
DIRECT
1 N 28.4294 W 81.3090 96
18L
1
1 N 28.4294 W 81.3090 96

1
96
-
-1000000
-1000000

ORL
2
JAG4
1 N 28.5427 W 81.3350 0
0
0
0

GUANO
3
JAG4
1 N 29.0996 W 81.3886 0
0
0
0

MATEO
3
JAG4
1 N 29.7669 W 81.4535 0
0
0
0

VQQ
3
JAG4
1 N 30.2130 W 81.8909 0
0
0
0

YULEE
3
JAG4
1 N 30.7145 W 81.8196 0
0
0
0

CHESN
3
JAG4
1 N 30.8393 W 81.8018 0
0
0
0

DBN
2
CANUK2
1 N 32.5635 W 82.8300 0
0
0
0

RIPPI
4
CANUK2
1 N 32.9056 W 83.3388 0
0
0
0

SINCA
4
CANUK2
1 N 33.0812 W 83.6049 0
0
0
0

CANUK
4
CANUK2
1 N 33.2170 W 83.8077 0
0
0
0

HUSKY
4
CANUK2
1 N 33.3305 W 83.9802 0
0
0
0

ZAMAS
4
-
1 N 33.4211 W 84.1175 0
0
0
0

KATL
1
-
1 N 33.6367 W 84.4279 1026
0
0
1 N 33.6318 W 84.4184 1026

1
1026
-
-1000000
-1000000

Importing all that gives me:

 

DIRECT ORL

DIRECT DBN

DIRECT ZAMAS

 

That's with AIRAC 1301 from Navigraph. Do note that SIDs and STARs are not imported into the FMC when loading a company route, which would explain why you're ending up with less route data than expected (as almost all waypoints listed in your file are part of either the JAG4 SID or the CANUK2 STAR).

Service pack 1 ngx does now have a problem importing a co-route sometimes it works sometimes it does not you have manually input them into the fmc now but Ideal flight program is now being upgraded to fix this problem and should be done soon as Steve has stated.

Rich Sennett

               

  • Author

LEK767 ... that kinda makes sense ... ZAMAS is the last waypoint before receiving vectors from ATC for landing either West or East ops into Atlanta on the CANUK TWO arrival. This route is so short that actually ALL of it is covered by first the SID JAGUAR FOUR with a transition of DBN ... then the CANUK STAR takes over. I believe you hit the nail on the head. This gives me some base upon which I can do some more troubleshooting.

 

Richard ... thanks for that information as well ... looks like I'm up against a couple of factors that I have to understand before I figure it all out.

 

Great forum ... thanks for everything.

Welcome Buddy good luck - guess your going to become more acquainted with the FMC.

Rich Sennett

               

  • Author

I'm very acquainted with it now ... it took a while ... I'm getting pretty good and programming it on the fly, during push back when the ATC changes my expected runway from 27R to 26L ... necessitating a total change in the SID, see NUGGT SIX DEPARTURE (RNAV) in KATL ... then I'm expecting a certain runway in KCLT based upon ATIS ... and I get switched up again by ATC ... the FMC is pretty flexible ... I love it. I came over from the "other guys" ... PMDG is simply such a much more polished product. Love it ... love it ... love it.

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.