September 7, 201312 yr Hey guys, I am having a strange issue. I can't seem to import an Flight sim Commander 9 generated plan to the 777 departing from EHAM. I originally wanted to take the LRF from EHAM to RJTT, but I get 'INVALID ENTRY' and an error message of 'Destination airport not found in selected .rte file : Import Aborted' I tried flightplans to other destinations, all have the same error. The flight plans are accepted fine in 747v1, MD-11, and NGX. I then moved the 777 to EIDW, created a EIDW-RJTT plan in FSC9. The EIDW RJTT plan imported fine. The plans show up in the Route Request too. Flightplans going to EHAM were fine as were all previous FSC9 generated plans. Just for ducks, I also tried to create a flight plan from Rotterdam EHRD and got the same INVALID ENTRY errors. I tried both plans that were 'auto generated' and ones that I created myself within FSC9, something is wrong in the Holland area. Can anyone else with FSC9 or another flight plan generator make it out of EHAM? Cheers TJ "The knack of flying is learning how to throw yourself at the ground and miss." - Douglas Adams Tejon 'TJ' Stanley
September 7, 201312 yr Can anyone else with FSC9 or another flight plan generator make it out of EHAM? Not me, I have the same problem as you describe (using Aivla EFB btw), I get the error message on first attempt to load the CO route, any further attempts just fail silently (and erase the destination airport I had filled in manually in the RTE page). In my case the attempt was a route EHAM SBGR. Could only get out of EHAM by manually inputting the route. Still trying to figure out if there is any user error here, before submitting a ticket. Regards and happy flying, Cristian Gonzalez.
September 7, 201312 yr I have started using pfpx which allows me to export flightplan to pmdg and fsc. Bilal Asif Khan
September 7, 201312 yr Same here. There´s another thread with same problem and more people. I submitted a ticket this morning. Let´s wait.... Best. Miquel Egea.
September 7, 201312 yr Author Well it is a headscratcher, I can't tell what is different between plans that work and don't work. Hopefully PMDG will look into this. I created two flight plans for testing EHAM-EDDM and EDDM-EHAM, using same waypoints in each direction, going DIRECT to each waypoint. Can PMDG figure out why EDDMEHAM.rte imports just fine, while EHAMEDDM.rte is rejected? Both plans work fine in 747, MD11, and NGX. Here is the data for EDDMEHAM.rte Generated and exported by FlightSim Commander · Version 9.3.HF_1 · Build: 06-September-2013 14 EDDM1DIRECT1 N 48.3538 E 11.7861 1486-----10 11486--1000000-1000000 LELTA2DIRECT1 N 48.4931 E 10.9553 0000 RIDAR2DIRECT1 N 48.5884 E 10.8028 0000 LIRSU2DIRECT1 N 50.1867 E 6.4533 0000 LNO292DIRECT1 N 50.2678 E 6.2750 0000 PELIX2DIRECT1 N 50.4969 E 5.7625 0000 LNO2DIRECT1 N 50.5858 E 5.7103 0000 TERLA2DIRECT1 N 50.6825 E 5.6656 0000 BROGY2DIRECT1 N 51.1825 E 5.4489 0000 LUTOM2DIRECT1 N 51.2656 E 5.4210 0000 LOPIK2DIRECT1 N 51.9308 E 5.1292 0000 ROVEN2DIRECT1 N 51.9629 E 5.1149 0000 OGINA2DIRECT1 N 52.0975 E 5.0546 0000 EHAM1-1 N 52.3081 E 4.7642 -13-----00 1-13--1000000-1000000 ****************************************** Here is EHAMEDDM.rte Generated and exported by FlightSim Commander · Version 9.3.HF_1 · Build: 06-September-2013 12 EHAM1DIRECT1 N 52.3081 E 4.7642 -13-----10 1-13--1000000-1000000 OGINA2DIRECT1 N 52.0975 E 5.0546 0000 ROVEN2DIRECT1 N 51.9629 E 5.1149 0000 LUTOM2DIRECT1 N 51.2656 E 5.4210 0000 BROGY2DIRECT1 N 51.1825 E 5.4489 0000 TERLA2DIRECT1 N 50.6825 E 5.6656 0000 LNO2DIRECT1 N 50.5858 E 5.7103 0000 PELIX2DIRECT1 N 50.4969 E 5.7625 0000 LNO292DIRECT1 N 50.2678 E 6.2750 0000 RIDAR2DIRECT1 N 48.5884 E 10.8028 0000 LELTA2DIRECT1 N 48.4931 E 10.9553 0000 EDDM1-1 N 48.3538 E 11.7861 1486-----00 11486--1000000-1000000 "The knack of flying is learning how to throw yourself at the ground and miss." - Douglas Adams Tejon 'TJ' Stanley
September 7, 201312 yr I already emailed this issue to the Guys at PFPX. It seems PMDG changed the format of the FPL in the new 777. The routeplanners are not up to date yet. Issues known with PFPX,Routefinder,FSC etc. The guys from pfpx are looking in to it. Don't know about the others but to drop them an email won't hurt Tip: make an manual route in the fmc, save it and include it in the mail to show the difference between them Greetings Mark Mark Visch
September 7, 201312 yr Author I created a manual plan in the 777 using the same one auto generated by FSC9 which worked fine from EHAM. It still doen't quite explain why other plans generated by FSC9 work fine, while those just from EHAM/EHRD area don't work...possibly other airports too. Here is EHAMEDDM001.rte as directly entered in the 777, following the route autogenerated in FSC9. PMDGFMC *5.1* 15 EHAMEHAM-110DIRECT1 N 52.3081 E 4.76417 -13-----10 1- -13 -1000000 -1000000- -1e+0060 0 0 0X00000000000000000000 0 040 -1000000 0 00 -1000000 0 00 -1000000 0 00 -1000000 0 0-1000000 -1000000 0 dtobasedtobase-200DIRECT1 N 52.3081 E 4.76417 -13100X00000000000000000113.0400 0 040 -1000000 0 00 -1000000 0 00 -1000000 0 00 -1000000 0 0-1000000 -1000000 0 OGINAOGINA-210UN8521 N 52.0975 E 5.05463 0000X0000000100000000000 0141.883000.569007 0 040 -1000000 0 00 -1000000 0 00 -1000000 0 00 -1000000 0 0-1000000 999 0 ROVENROVEN-210UN8521 N 51.9629 E 5.11485 0000X00000000000000000000.283143 0 040 -1000000 0 00 -1000000 0 00 -1000000 0 00 -1000000 0 0-1000000 999 0 LOPIKLOPIK-210UN8521 N 51.9308 E 5.12916 0000X00000000000000000000.243468 0 040 -1000000 0 00 -1000000 0 00 -1000000 0 00 -1000000 0 0-1000000 999 0 LUTOMLUTOM-210UN8521 N 51.2656 E 5.42101 0000X00000000000000000000 0 040 -1000000 0 00 -1000000 0 00 -1000000 0 00 -1000000 0 0-1000000 999 0 BROGYBROGY-210UN8521 N 51.1825 E 5.44889 0000X00000000000000000000 0 040 -1000000 0 00 -1000000 0 00 -1000000 0 00 -1000000 0 0-1000000 999 0 TERLATERLA-210UN8521 N 50.6825 E 5.66556 0000X00000000000000000000 0 040 -1000000 0 00 -1000000 0 00 -1000000 0 00 -1000000 0 0-1000000 999 0 LNOLNO-210UN8521 N 50.5858 E 5.71028 0000X00000000000000000000 0 040 -1000000 0 00 -1000000 0 00 -1000000 0 00 -1000000 0 0-1000000 999 0 PELIXPELIX-210UZ2101 N 50.4969 E 5.7625 0000X00000000000000000000 0 040 -1000000 0 00 -1000000 0 00 -1000000 0 00 -1000000 0 0-1000000 999 0 LNO29LNO29-210UZ2101 N 50.2678 E 6.275 0000X00000000000000000000 0 040 -1000000 0 00 -1000000 0 00 -1000000 0 00 -1000000 0 0-1000000 999 0 LIRSULIRSU-210UZ3151 N 50.1867 E 6.45333 0000X00000000000000000000 0 040 -1000000 0 00 -1000000 0 00 -1000000 0 00 -1000000 0 0-1000000 999 0 RIDARRIDAR-210Y1611 N 48.5884 E 10.8028 0000X00000000000000000000 0 040 -1000000 0 00 -1000000 0 00 -1000000 0 00 -1000000 0 0-1000000 999 0 LELTALELTA-210DIRECT1 N 48.4931 E 10.9553 0000X00000000000000000000 0 040 -1000000 0 00 -1000000 0 00 -1000000 0 00 -1000000 0 0-1000000 999 0 EDDMEDDM-110DIRECT1 N 48.3538 E 11.7861 1467-----00 3- 1517 -1000000 -1000000- -1e+0060 0 0 0X00000000000000000000 0 040 -1000000 0 00 -1000000 0 00 -1000000 0 00 -1000000 0 0-1000000 -1000000 0 -------------------------------1e+006EHAMEDDM690 122-1e+006 0-1000000-10000001 ****************************** Here is the autogenerated EHAMEDDM.rte FSC9 plan of the same route. Generated and exported by FlightSim Commander · Version 9.3.HF_1 · Build: 06-September-2013 14 EHAM1DIRECT1 N 52.3081 E 4.7642 -13-----10 1-13--1000000-1000000 OGINA2UN8521 N 52.0975 E 5.0546 0000 ROVEN5UN8521 N 51.9629 E 5.1149 0000 LOPIK5UN8521 N 51.9308 E 5.1292 0000 LUTOM5UN8521 N 51.2656 E 5.4210 0000 BROGY5UN8521 N 51.1825 E 5.4489 0000 TERLA5UN8521 N 50.6825 E 5.6656 0000 LNO5UN8521 N 50.5858 E 5.7103 0000 PELIX2UZ2101 N 50.4969 E 5.7625 0000 LNO295UZ2101 N 50.2678 E 6.2750 0000 LIRSU2UZ3151 N 50.1867 E 6.4533 0000 RIDAR2Y1611 N 48.5884 E 10.8028 0000 LELTA2-1 N 48.4931 E 10.9553 0000 EDDM1-1 N 48.3538 E 11.7861 1486-----00 11486--1000000-1000000 "The knack of flying is learning how to throw yourself at the ground and miss." - Douglas Adams Tejon 'TJ' Stanley
September 7, 201312 yr Yep I had the same problem today as well! I wanted to go from EHAM - KBOS and couldn't import it as well... EDIT: I am using FSBuild 2.4.019. Arjen Vandervelde
September 7, 201312 yr Me too, no plans generated with FSC9 from EHAM or EHRD can not be imported in the 777. Tried EHBK to LOWI and EHGG to LOWI and worked fine, but not EHAM or EHRD to LOWI. Johann van Rhyn
Create an account or sign in to comment