albar965

You use MSFS scenery with the included but outdated cycle 1801 navigation database. RNL is gone a long time ago. I can only find it in FSX but not in MSFS and not in the latest cycle 2403. Either update LNM and MSFS using a Navigraph subscription or select in LNM menu "Scenery Library" -> "Navigraph" -> "Select Automatically" to get the best scenery library settings. Either option will get LNM perfectly in sync with the simulator. Alex

Understood, hopefully 🙃. And thanks for the files. So <ATCWaypoint id="LIZZI"> <ATCWaypointType>Intersection</ATCWaypointType> <WorldPosition>S37° 27' 2.20",E145° 38' 16.80",+012800.00</WorldPosition> <ATCAirway>Q29</ATCAirway> <ArrivalFP>LIZI9A</ArrivalFP> <RunwayNumberFP>27</RunwayNumberFP> <ICAO> <ICAORegion>YM</ICAORegion> <ICAOIdent>LIZZI</ICAOIdent> </ICAO> </ATCWaypoint> would be the solution for a STAR without transition. The same would apply if there is a transition like in "KPHX/08 MRBIL1.GCN V208 TBC V210 RSK.LARKS3 KDEN/34L": <ATCWaypoint id="RSK"> <ATCWaypointType>VOR</ATCWaypointType> <WorldPosition>N36° 44' 54.20",W108° 5' 56.04",+013500.00</WorldPosition> <ATCAirway>V210</ATCAirway> <ArrivalFP>LARKS3</ArrivalFP> <RunwayNumberFP>34</RunwayNumberFP> <RunwayDesignatorFP>LEFT</RunwayDesignatorFP> <ICAO> <ICAORegion>K2</ICAORegion> <ICAOIdent>RSK</ICAOIdent> </ICAO> </ATCWaypoint> I'll try to add this for the next update. Problem is that I have to juggle between all kind of add-ons and the stubborn MSFS. I'll post a link here if I have a release candidate. Alex

You're welcome.🙂 Manual updated: https://www.littlenavmap.org/manuals/littlenavmap/release/latest/en/INSTALLATION.html#multiple-installations Alex

From the CHANGELOG.txt (3.0.4): Use --setttings-path C:\Users\YOURUSERNAME\AppData\Roaming\ABarthel-XP12 instead. I forgot to update this section in the user manual about this change. Will do. Alex

I think this is due LIZZI being the endpoint of the airway Q29. Not sure how MSFS loads the plan if I remove the airway (or not) and put LIZZI into the STAR. Not at my flying computer now. When loading a STAR from a PLN file, I'm only looking at the element "ArrivalFP" to identify the procedure. Then I look at the first (here ATPER) and previous waypoint (LIZZI) of the en-route/SID boundary and try to identify a transition (no transition for your example). I have to do this since other tools like SimBrief or Navigraph Charts save the format slightly different. Then waypoints of the STAR are added from the database and not from the PLN file. If all is done loading, I remove consecutive duplicates from the list. Why do you want to identify an entry waypoint? This is determined by the STAR and not by the waypoint list. I completely ignore the redundant list of waypoints when loading SID or STAR. Only entries are used to find transitions. This redundant list of wayoints is not the smartest design, IMO. X-Plane FMS contains only the procedure names and not the en-route waypoints which is much better. Alex

BTW: Also check you detail level in menu "Map". Click "Default Map Detail". A lower detail level lets features disappear early. Alex

All features are hidden above a certain zoom level but the trail disappears last. What monitor resolution is this? Alex

This has new add-on filters: Alex

Little Navmap 3.0.6 released Direct Download ► Windows 64-bit Installer (MSFS and X-Plane) - LittleNavmap-win64-3.0.6-Install.exe ► macOS - LittleNavmap-macOS-3.0.6.zip ► Linux (64 bit, based on Ubuntu 22.04) - LittleNavmap-linux-22.04-3.0.6.tar.gz Other Versions: ► Windows 32-bit Installer (only for FSX and P3D) - LittleNavmap-win32-3.0.6-Install.exe ► Linux (64 bit, based on Ubuntu 20.04 for Debian or older systems) - LittleNavmap-linux-20.04-3.0.6.tar.gz Zipped Windows releases without installer are available in the alternative download locations below or from the release assets at GitHub - Little Navmap Releases - Version 3.0.6 (scroll down to Assets). Alternative Download Locations - Look into sub-folders for beta, development or release candidates: ► Alternative Download Locations Notes This is a stable release of Little Navmap which fixes several bugs and adds a few improvements and new features. Notable changes: New add-on airport filter modes in menu View. Airport and navaid links in aircraft progress tab. Logbook status and collected aircraft performance now kept between restarts. macOS users: Keep in mind that you have to clear the quarantine flag when updating Little Xpconnect. See Clearing the Quarantine Flag on macOS. The updated online user manual is available here: Little Navmap - User Manual. See here for user manual downloads: User Manuals - Stable Releases. A big thank you to all who reported bugs and issues! Changes from 3.0.5 to 3.0.6 Flight Plan and Procedures Fixed wrong warning for runway mismatches in procedure search. Showed unneeded mismatch warning for runways without procedure. Example: KSTK. Fixed issue where SID/STAR could not be reloaded due to wrongly detected runway mismatch when using the MSFS scenery library. Example: EDDE ERNE1V EDDK/I14L could not load ERNE1V when loading the flight plan for MSFS. Flight plan name now updated in window title bar when using Save or Save as. Now correctly assigning ALL as runway designator to SID/STAR having no runway assignments in MSFS. Reload the scenery library if you use MSFS. Fixed issue where STAR could not be loaded from MSFS PLN file. Example: KIAD/30 ANJLL4.DNERO KLAX/06L. Fixed crash when modifying flight plan. Flight Plan Route Description Fixed issue where STAR keyword was not generated from flight plan in route description. Now always adding generic SID/STAR keywords in export formats like the Rotate MD-80 .txt format to avoid issues when loading plan in FMC. Fixed issue with alternate airports having the same STAR as destination. Example: KVHN SSO SUNSS8 KDVT KPHX showed a wrong error message and used KPHX as destination. Fixes in route description where description MUHA EPMAR3 MAXIM SNDBR3 KMIA was not recognized Added Ctrl+Return shortcut to create flight plan from route description. Fixed issues where airways were not recognized. Example: KCNM WHOLE EWM J4 SUNSS8.SSO KDVT where J4 was added as a far off NDB. Fixed plan reset to VFR in route description. Flight plan type is now set from current flight plan type in window Flight Planning when clicking Load from Flight Plan. Flight Plan Export Reverted change for degree sign ° vs. * in MSFS PLN flight plan files to avoid issues with third-party software not capable to read this MSFS compatible format. Added new multiexport format Microsoft Flight Simulator 2020 format using "*" as degree sign for cases where the simulator or add-ons cannot deal with the ° sign. Removed obsolete annotated PLN export. Little Navmap can still read this format from old flight plans. Map Display Added three add-on airport map display options to menu View and toolbar. See User Manual - View Menu - Airports. Add-on no override (Ctrl+Alt+O😞 Add-on airports are shown like normal airports. Add-on override zoom (Ctrl+Alt+Z😞 Add-on airports override zoom distance only but filters like Soft Surface can still be used to hide them. Add-on override zoom and filter (Ctrl+Alt+Y😞 Add-on airports override zoom distance and filters, i.e. are always shown. Filters like Soft Surface have no effect on add-on airports. Added airport filter preset Show only add-on airports in menu View and toolbar. Map theme shortcuts for included themes can now be defined in DGML file. Assigned shortcuts Ctrl+Alt+0 to Ctrl+Alt+7 for all default free included map themes. These do not change when adding additional themes. Fixed disappearing related navaids when drawing procedures. This happened when navaid was outside the bounding box of the flight plan. Added options for airport runway labels and taxiway label size on page Map Display in section Airports. User Interface Replaced outdated airway types Victor and Jet with Low and High everywhere in the program. Fixed too small table cell height on Windows with the high DPI option switched off. Now also closing the startup image splash window in all dialog windows to avoid being hidden. As a result, the program looked like frozen since the hidden dialog window blocked input. Fix in Dutch shortcut translation (‘Ctrl+D’ vs. ‘Ctrl+Down’) which overlapped with other keys. More user interface improvements. Minimum number of trail points lowered to 1000. Aircraft Progress Added map, information and procedure links in progress tab for destination airport, top of climb, top of descent, next waypoint and related navaids. Fixed wrong next waypoint indication when flying missed approach. Logbook Logbook takeoff and landing detection is now kept for program restart. Improved logbook entry creation to avoid creating of unneeded entries. A flight can now be continued after program restart and logbook entry is updated accordingly. Now detecting off-airport takeoff and landing. Logbook entries get coordinates in degree/minute format as departure and landing position in this case. Other Translations updated. Thanks to Flavio, Patrick and Ricardo! Updated user manual for new features and changes. The aircraft performance collection now keeps results on restart. Note that you have to restart the collection manually by clicking in menu Aircraft -> Restart Aircraft Performance Collection, the button in the window or File -> Reset all for a new Flight. Now adding backup log file abarthel-little_navmap.log.1 to issue and crash reports Added new X-Plane 12 VASI types APAPI_L and APAPI_R. Fixed issue where X-Plane airways had wrong type assigned. Example: EVMON to PAPAL airway Z8 was wrongly declared Jet. #1111 Corrected VOR range for X-Plane data to use 130 NM for “unspecified but likely high power VOR”. 🐇🐇🪺🪺 Happy Easter! 🪺🪺🐇🐇 See the included CHANGELOG.txt or here online for a complete list across all versions. All files are checked by VirusTotal.

Hi Dave, I've no idea what can cause this. Never seen this problem. Either there is no fuel flow at all or it is working ok. Did you see fuel flow in the aircraft progress tab during climb? I mean this here: Alex

Yep. 10000 is minimum. If you use the mouse wheel you cannot go lower. I can change the minimum to 1000. Alex

There is no YXH in latest navdata (cycle 2403). Seems the VOR went out of service. I can only find this in the ancient FSX navdata. Check "Select automatically" in the LNM menu "Scenery Library" -> "Navigaph" to have LNM in sync with the outdated P3D navdata. Then LNM should find it again. Alex

Thanks for confirming. I'm scared that this might break third-party programs (like ° vs. * for degree sign broke import to Navigraph Charts 😕). This discrepancy is there for a reason, but I don't know for what, and frankly, I'm too lazy to do research now.🙃 Alex

Name resolution in local networks is a bit touchy. I also have some devices here which I cannot find by name or where it takes forever to resolve. In some I have to add the domain like "computer.fritz.box" "computer.home" to find them. IP-address is a good fallback then. Alex

You have a different problem than the OP if you even cannot connect. Often it is a Firewall issue where the connection is blocked. Having both a Wifi and Ethernet connection is no issue. LNM will listen on both interfaces. You can try a Ping app to check network connectivity to the flying computer. But even then, the port to LNM might be blocked by an overzealous firewall. Alex

Hi Martin, thanks for the files. The initial fix for a transition and/or approach is always listed separately and consistently in the table. This is expected since these are two different procedure leg types. Always has been this way and I'd like to keep them separate. What I don't like is that waypoints of SID/STAR entry/exit points are duplicated in the route description. But this is a change for later. There are plenty of workarounds and all kind of forth and back to get along with MSFS' terribly buggy flight plan loading. So yes, this might look different to what you see in the table. The waypoints are added like this for MSFS to detect the transitions. LNM also has code to detect the saved transitions from MSFS PLN files. I did not check you plan with MSFS. Let me know if it cannot load the procedures. BTW: Your example helped me to find an issue that appeared when loading MSFS flight plans. Alex

Thanks for the report. 👍 And exactly because of the confusion it is a bug and should not happen.🙃 Fixed for the next 3.0.6 update. Alex

You're welcome and thank you for your kind words.🙂 Alex

Something else comes into my mind: Do not use the map to correct the flight plan. MSFS will reset the plan. Use the drop down boxes on the top to select an approach or runway. Alex

Here is a release candidate for 3.0.6: https://k00.fr/3liopl2z Sorry, I had to revert back to the ° sign because the change cause issues with third-party applications like Navigraph Charts. But I added a multexport format "Microsoft Flight Simulator 2020 format using "*" as degree sign." which can be used if you run into issues. Alex

Here is a release candidate for 3.0.6: https://k00.fr/3liopl2z Note the new add-on airport filter options.🙃 ( @Nemo, @VH-WCE and @yrodin ). Alex

This release candidate for 3.0.6 should fix the issue: https://k00.fr/3liopl2z Plus a bunch of more bugs when importing SimBrief and reading/writing route descriptions. Alex

This release candidate for 3.0.6 should fix the issue: https://k00.fr/3liopl2z Alex

I used the green start position which shows parking, runways, etc. No V-shape with this but it shows only the approach procedure legs and not the connection from departure to approach procedure. At first I thought the whole plan was missing until I scrolled North. Also, the simulator ignored the runway selection and placed me on another runway. At least I could change it in the start screen without breaking the plan. I guess this is one of the cases the sim does not like. I did a lot of testing and a lot of plans work fine. Alex

Just tried around with this. The flight plan loads ok on the main screen and then shows erratically in the G1000. No idea what's going on there. Either it shows a V-shape or only the approach legs are visible in the G1000. The planning screen in MSFS always shows the runways ok. I'm at a loss here. No idea what more workarounds can be added. I'd rather say Asobo should get its act together and finally sort out all the flight plan stuff. Alex