The title says it all.
Since it is already part of the GNS series, I was wondering when crossfill will be a thing for the GTN series.
I know about the alternative method but the ability to crossfill would also be nice and saves a bit of time imo.

Great product otherwise 😉

3 hours ago, Xander975 said:

The title says it all.
Since it is already part of the GNS series, I was wondering when crossfill will be a thing for the GTN series.
I know about the alternative method but the ability to crossfill would also be nice and saves a bit of time imo.

Great product otherwise 😉

As another user I understand. At one time the same request came across my mind.  Then I took time to think it through. First, in the times i have been up in a GTN aircraft, I have not been up in an aircraft that had (2) GTN's in the panel.  Pocketbooks obviously an influence.  In my FSX/FSX-SE only three of my GA aircraft's have multiple GTN's.  IRL only one GTN will couple as a master device to the NAV/AP.  So the functions of a second GTN default to non-essential but still helpful functions.  Traffic, COM2, and determining factors like OAT and TAS for instance. Lookups of COM freq's for nearby airports, ATIS when nearing destination airport, etc, etc, etc.  Have not found a compelling reason for crossfill and conjecture that with the ease of GTN manual flight plan entry see no reason for crossfill.  it is just too easy to reach meaningful multi-GTN functionality with less effort.

It has been on our wish list for quite a while.. clearly it has not made it to the top 😉

There are always new things coming atop this one nowadays but it would be nice to have.

Having a function to export flightplan from one unit in a format that can be import on another unit could be a workaround for crossfill. A manual crossfill ;). (and in a better way than "playing" with nonvol files if i remember)

But i'm agree, it's really not a top priority. Just one unit can do so much !

Edited August 31, 20205 yr by nirgal76

6 hours ago, nirgal76 said:

Having a function to export flightplan from one unit in a format that can be import on another unit could be a workaround for crossfill. A manual crossfill ;). (and in a better way than "playing" with nonvol files if i remember)

But i'm agree, it's really not a top priority. Just one unit can do so much !

I can send you an Excel spreadsheet that uses routines to convert a flight plan line from say Skyvector into a .gfp file.  Issue is it takes more time to dance through the planning, opening the spreadsheet, copy and paste into it, then after parsing the line copy-and-pasting the result into another text line, and copying that to a text file with a .gfp filename, then positioning that .gfp file on your system in a folder that the the gauge can locate, then importing it, all the while hoping that the Garmin filters will not bounce it due to a waypoint in the the plan no longer matching what is in the Garmin database.

Been there, done that.  It's my own developed spreadsheet. 



I can enter a flight plan into the second GTN much faster manually.  No comparison.  And I rarely find the need to do so.

Sometimes it becomes about the challenge rather than a reasonable approach.......  Would rather have spent the time flying...

Edited August 31, 20205 yr by fppilot

Thank you for your excel sheet but i'm only on MSFS 2020 now (i don't have lot of time for sim so i prefer to stay on one plateform only). Then, for the moment, i don't have usage of my wonderful RXP units :(.

i'm back to roots with needles only (and my eyes) for flying ;).with hope for RXP and their amazing skills to find a workaround.

Edited September 1, 20205 yr by nirgal76