hi,
Yes, I believe there was no one else on the forum who was looking for solutions to Routeconverter integration with Flightplan Migrator, so I looked to see if there was any topic and I was not successful.
I think Flightplan Migrator is definitely more demanding than other programs that read .FPL files (including other Garmin devices).
The process of trying to figure out the incompatibilities between Routeconverter and Flightplan Migrator made me create 10 .FPL files by Routeconverter, and from what I saw in the forum, the limit for creating .FPL files is 10, until a donation is made ). So I can no longer create .FPL files, even if it's to test if it's going to work on the plane.
Since the creator of the software was interested in this post , can you tell if there is a real integration (of an easy way) between Routeconverter and Flightplan Migrator?
Quote:Of course, let's start.
I'm wondering that you're to first to report problems with the format. It seems Flightplan Migrator is a bit more picky than the Garmin devices that read .fpl files. Is that correct?
Yes, I believe there was no one else on the forum who was looking for solutions to Routeconverter integration with Flightplan Migrator, so I looked to see if there was any topic and I was not successful.
I think Flightplan Migrator is definitely more demanding than other programs that read .FPL files (including other Garmin devices).
The process of trying to figure out the incompatibilities between Routeconverter and Flightplan Migrator made me create 10 .FPL files by Routeconverter, and from what I saw in the forum, the limit for creating .FPL files is 10, until a donation is made ). So I can no longer create .FPL files, even if it's to test if it's going to work on the plane.
Since the creator of the software was interested in this post , can you tell if there is a real integration (of an easy way) between Routeconverter and Flightplan Migrator?