Flight Plans Missing

[floydcox 3]

Only seeing flight plans based in the UK - EGNX.EGLL etc, no plans show up from other areas, LFMN.LFML, etc. Any ideas?

[RXP 2,338]

Hi, do you mean when copying flight plan file to the correct FPLN folder location, only the flight plans in UK are showing up in the list, all others being excluded?

Our flight plan sample pack included an example: KSLE_KSLE.gfp. Is this one showing up in the list when put in the FPLN folder?

You might want to cross check the content of the 'hidden' flight plan files to make sure they are properly formatted per GTN requirement. To assist you in this, you might want to read the guideline document included in the sample pack.

[Alvega 2,124]

Just ran the update and it prompted me to download the new 6.41 trainer. No problem here.

I have one question: since i updated the trainer can I delete the folder "GTN trainer data" that resides in "C:\ProgramData\Garmin"? I guess this one was just used by the old trainer version, right? I would like to get back 2+ GB.

 

[RXP 2,338]

Hi, you might want to save your sys_nand files found in the GTN subfolder. They store your device settings, routes and user waypoints and might be loaded in the new trainer once put into the new trainer 6.41 equivalent subfolder.

[Alvega 2,124]

8 hours ago, RXP said:

Hi, you might want to save your sys_nand files found in the GTN subfolder. They store your device settings, routes and user waypoints and might be loaded in the new trainer once put into the new trainer 6.41 equivalent subfolder.

And after that I can delete the "GTN trainer data" folder?

[RXP 2,338]

Hi,

I'd guess yes! Besides the non volatile memory files, the other files are the databases and the resources 'only' and are superseded with the ones installed with the latest trainer.

[andro_b 1]

I have the same issue, having just purchased the GTN 750, no matter how carefully I check the flight plan location according to the documentation, in the Jetstream J32 at least, no plans show up in the catalog. Any clues anybody? Using version 6.41, X-Plane 11.10.

I now notice that the Garmin Trainer executable finds the flight plans in the catalog folder, but the Reality-XP GTN 750 does not. What is that telling me?

 

[andro_b 1]

With X-Plane 11.01 and the Jetstream J32 and the Reality-XP GTN 750, no flight plans show up in the catalog menu. They appear in the Garmin Trainer just fine, including my own plans created with the new 1.8.4 export function in Little Navmap (thanks Alex for the most wonderful program!).

Given this, what could be wrong? My error, or a defect?

[Sorry, this should have been posted in the Reality XP X-Plane forum. I don't know how to shift it.]

[andro_b 1]

Hi all,

A very careful reinstall of the Reality XP GTN 750 and the Garmin Trainer cleared up this issue.

I had installed the Garmin Trainer separately, and also aborted the process a couple of times when it appeared to be hung - not very wise in hindsight. By solely using the GTN 750 installer which installs the Garmin Trainer for you, everything is now fully functional. And what a delight to be able to import user defined waypoints. And amazingly, just today the new 1.8.4 Little Navmap can export to the GTN 750 in X-Plane.

[RXP 2,338]

@andro_b I'm glad you've solved the issue, but please, try not to cross-post, it makes it harder to provide support otherwise.

[floydcox 3]

Just updated GTN and littlenavmap to latest versions and using the dedicated export to GTN function, the route do not show up for import to the GTN. Any ideas anyone?

[RXP 2,338]

You might want to further read fppilot post:

 

[kneighbour 32]

On 10/21/2017 at 3:49 PM, floydcox said:

Only seeing flight plans based in the UK - EGNX.EGLL etc, no plans show up from other areas, LFMN.LFML, etc. Any ideas?

I certainly do! I have this problem also. In my case, the issue is that the flight plan name has to start with a letter within a certain range. ie A-E or something. I don't know the exact range, but I now begin all of my flight plan names with a_ and they show up fine.