Jump to content

v1.07 PMDG 777 export now results in "Invalid Entry"


Recommended Posts

The file is being saved to the correct folder, in the .rte format, but no route exported to NGX/777 format with v1.07 has worked when I try to load it into the 777. Files from v1.06 and previous all still work. If I manually enter the Origin and Destination in the FMC and select "Route Request" the file is displayed, but when I click on it I get "Invalid Entry" as well.

Link to comment
Share on other sites

As a workaround. Input the DEP and DEST on the RTE page, then import the Route using the CoRTE RSK.

S

If I manually enter the Origin and Destination in the FMC and select "Route Request" the file is displayed, but when I click on it I get "Invalid Entry" as well.

I've tried that.

I've been successful creating routes for KMLB-KLAX, KATL-KLAX, and EDDF-KLAX but unsuccessful in creating routes for EHAM-KLAX, EHAM-KSFO, and EHAM-EDDF. Dispite the fact that the error message refers to a problem with the destination airport, it appears that it is a problem stemming from EHAM. Here is the EHAMKLAX01.rte output:

Generated by PFPX 17 Sep 2013 19:58 UTC
35
EHAM
1
DIRECT
1 N 52.308 E 4.764 -11
-----
1
0
1
-11
-
-1000000
-1000000
BERGI
5
UL602
1 N 52.749 E 4.359 0
0
0
0
AMGOD
5
UL602
1 N 52.975 E 3.685 0
0
0
0
SUPUR
5
UP1
1 N 53.015 E 3.564 0
0
0
0
GODOS
5
UP1
1 N 53.249 E 3.430 0
0
0
0
BINBO
5
UP1
1 N 53.402 E 3.341 0
0
0
0
ROKAN
5
UM982
1 N 53.663 E 3.189 0
0
0
0
ERLOT
5
UM982
1 N 55.287 W 0.585 0
0
0
0
ROBEM
5
UM982
1 N 55.459 W 1.021 0
0
0
0
RITSI
5
UM982
1 N 55.702 W 1.657 0
0
0
0
SAB
5
UM982
1 N 55.908 W 2.206 0
0
0
0
FINDO
5
UP58
1 N 56.369 W 3.464 0
0
0
0
NEVIS
5
UP24
1 N 56.695 W 4.545 0
0
0
0
ORSUM
5
UP24
1 N 57.052 W 5.295 0
0
0
0
NINEX
5
UP59
1 N 58.856 W 9.500 0
0
0
0
BALIX
5
DCT
1 N 59.000 W 10.000 0
0
0
0
6320N
5
DCT
1 N 63.000 W 20.000 0
0
0
0
6630N
5
NATB
1 N 66.000 W 30.000 0
0
0
0
6640N
5
NATB
1 N 66.000 W 40.000 0
0
0
0
6550N
5
NATB
1 N 65.000 W 50.000 0
0
0
0
6360N
5
NATB
1 N 63.000 W 60.000 0
0
0
0
IKMAN
5
NATB
1 N 62.500 W 63.000 0
0
0
0
FEDDY
5
SCAI
1 N 61.700 W 67.000 0
0
0
0
IRLAV
5
SCAI
1 N 57.974 W 80.000 0
0
0
0
LITRO
5
SCAI
1 N 53.363 W 90.000 0
0
0
0
FERNO
5
SCAI
1 N 51.647 W 92.872 0
0
0
0
YRL
5
V181
1 N 51.071 W 93.762 0
0
0
0
YWG
5
DCT
1 N 49.928 W 97.239 0
0
0
0
DIK
5
DCT
1 N 46.860 W 102.773 0
0
0
0
OCS
5
J107
1 N 41.590 W 109.015 0
0
0
0
URNUW
5
J107
1 N 39.134 W 112.104 0
0
0
0
MLF
5
DCT
1 N 38.360 W 113.013 0
0
0
0
LAS
5
DCT
1 N 36.080 W 115.160 0
0
0
0
HEC
5
DCT
1 N 34.797 W 116.463 0
0
0
0
KLAX
1
-
1 N 33.942 W 118.408 126
-----
0
0
1
126
-
-1000000
-1000000
Link to comment
Share on other sites

Hello,

There is an issue with the 777 accepting airports with negative elevation in a saved flight plan. According to the link below, it has been fixed in an upcoming update:

http://forum.avsim.net/topic/418750-pmdg-777-issue-tracking-thread/

Thank you for that link. I'm glad they're aware of it, and I'm glad it's not just something I'm doing wrong.

Link to comment
Share on other sites

You did it wrong!

All you've first tested is EHAM from or to.

When I see, EHAM -> xxxx, EHAM -> xxxy and xxxz -> EHAM does not work, I would take EHAM out!

You did it and it worked.

This is trolling, right?

You're "solution" precludes using exported routes to or from EHAM. That isn't viable.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use