December 26, 20178 yr The iFly 747 takes a .route format. EFB (Electronic Flight Bag) is able to export into this format, but I don't see that option for the latest Little NavMap...is there a way to do this? If not, is it possible to add this? PC: AMD 9850X3D, RAM 64GB, Geforce GTX 5090 (32GB), MSFS 2020, MSFS 2024, Pimax Super 50PPD, Quest 3
December 26, 20178 yr Nope, not yet. I'll check the format if I can add this to the next big release. Alex Alex' Projects: Little Navmap
December 26, 20178 yr Author Thanks Alex! PC: AMD 9850X3D, RAM 64GB, Geforce GTX 5090 (32GB), MSFS 2020, MSFS 2024, Pimax Super 50PPD, Quest 3
November 18, 20214 yr Commercial Member Is the iFly .route export format available yet? Regards, Dave Opper HiFi Support Manager
November 19, 20214 yr 22 hours ago, Daveo said: Is the iFly .route export format available yet? Nope. Meh. Seems this got buried somehow.🤔 Will try for 2.8: https://github.com/albar965/littlenavmap/issues/817 Edit: Can't the iFly import also other formats? Alex Edited November 19, 20214 yr by albar965 Alex' Projects: Little Navmap
November 26, 20214 yr Commercial Member On 11/19/2021 at 8:32 PM, albar965 said: Nope. Meh. Seems this got buried somehow.🤔 Will try for 2.8: https://github.com/albar965/littlenavmap/issues/817 Edit: Can't the iFly import also other formats? Alex No I do not think so with the new advanced version for P3D5. Tried an older version they used for FSX that was already in the export options but that did not work. Here is a clip from the docs. 1. Introduction This document describes the format of our flight plan file (.route). We strongly recommend that third-party software export the route data ONLY, and not export the SID/STAR/APP data, because users navdata may not contain the same as per SID/STAR/APP in the flight plan file, and that may cause some unknown issues. 2. Various navigation data file extensions All pre-defined flight plan files (.route) are stored in FLTPLAN folder, which is located under the directory “Documents\Prepar3D v5 Add-ons\iFlyData\navdata\FLTPLAN” All these files can be opened with Notepad (a Windows accessory) or any text editor. Regards, Dave Opper HiFi Support Manager
November 26, 20214 yr Thanks for the answer @Daveo I can add the .route format. Looks doable for the next release. Just to be sure: We're talking about files which look like the one below: [RTE] ORIGIN_AIRPORT=KMFR DEST_AIRPORT=KORD [RTE.0] RouteName= Name=BRUTE Latitude=42.407528 Longitude=-122.722533 CrossThisPoint=0 Heading=0 Speed=0 Altitude=0 Frequency= FrequencyID= ... Here is the related Github issue: https://github.com/albar965/littlenavmap/issues/817 Alex Alex' Projects: Little Navmap
January 29, 20224 yr Commercial Member Hi Alex, Any progress on this one? Regards, Dave Opper HiFi Support Manager
January 29, 20224 yr 1 hour ago, Daveo said: Any progress on this one? Sorry, no. It's on the list for the next 2.8 but work has not started yet. I'm digging into the most complicated issues first. Currently finishing SimBrief import and export. Alex Alex' Projects: Little Navmap
Archived
This topic is now archived and is closed to further replies.