albar965

Sorry, took a while. Here is a 3.0.7.rc1: https://k00.fr/ca0o2ubp Tested a bunch of plans with the latest MSFS beta and even complex plans load without issues. Alex

I'm sorry, but its unlikely that I can add this in the future. The calculation through procedure altitude and vertical angle restrictions while keeping descent and climb paths is already quite complex. Adding variable paths would be a nightmare. Alex

Sorry, but this is not doable. Not sure why you need this to fine tune the TOD calculation. I'd rather make a profile for each flight scenario (light, mid, heavy or short and far). Alex

Sorry, but I cannot help with this program since I did not develop it. It seems the developer gave up on it 4 years ago. Alex

You're welcome and thank you for your kind words!🙂 I see no need to drop FSX. It is still used. Alex

This is only the information window showing. Map is missing. This can happen after changing "Allow to undock the map window" and is also noted in the option dialog. Click LNM menu "Window" -> "Reset Window Layout to Default" to all back to normal. Alex

Not in the dialog windows which read coordinates (userpoints, jump to coordinate and others). You can use measurement lines for this: Alex

There is a plugin or tool to connect LNM to FG but it seems the developer gave up on it: https://github.com/slawekmikula/littlefgconnect I'll try to continue but I cannot do everything.😞 Alex

If this can be downloaded in OpenAIR airspace format or KML it would be no issue to add it to LNM. Alex

Maybe an addon inserting the ILS. But anyway: I really recommend to set LNM menu -> "Scenery Library" -> "Navigraph" -> "Select Automatically" to let LNM select the best database configuration. Alex

No need to do that. Just press F11 (Window -> Fullscreen map). To allow map undocking you have to check "Allow to undock the map window" on options page "Map". Then restart and maybe reset the view in menu Window since the map window disappears in some cases after changing this option. Alex

You collected far too many trails. Right click in the elevation profile and select "Delete aircraft trail". This does not affect the trail on the main window. But I recommend to delete the trail before each flight and use the ones stored in the logbook if needed. BTW: I changed this in one of the 3.0.X versions so that the trail in the profile is cleared for each flight to avoid this. Alex

You can't have an additional map window in LNM. However, you can separate the map window from the main window if required (see here in options on page "Map": https://www.littlenavmap.org/manuals/littlenavmap/release/latest/en/OPTIONS.html#map-icon-map). You can use the webserver (menu Tools) and a browser for an additional view: https://www.littlenavmap.org/manuals/littlenavmap/release/latest/en/WEBSERVER.html Alex

The only difference I see is that I'm using the MSFS beta. Maybe they fixed some of the issues but I doubt it. Alex

No problem at all, Michael. If all goes wrong you can also create the plan in MSFS, save it as PLN and import it into LNM for flight following. You can load MSFS PLN files from LNM menu "File" -> "Open flight plan" like LNMPLN files. LNM detects the format automatically. Alex

Looks alright to me. Below shots are with all export options off and exported with "File" -> "Export Flight Plan as MSFS 2020 PLN". Then loaded in the MSFS opening screen. Also the GPS in the aircraft shows it ok. The altitude at waypoints from LNM is usually ignored by MSFS. This is as expected. I have a lot of more complex examples here with SID, STAR and approaches that work ok. It also may depend if you have the Navigraph navdata update installed or not. I tested with and without and see no issues. LNM: MSFS latest beta 15: Alex

Thank you for the plan, Michael. I'll have a look at it. It should not be impossible to load a plan properly into MSFS. It should work mostly ok. Alex

Hi Michael, you can insert the plan as LNMPLN and maybe as PLN to directly in a post here. The flight plans are text files. See here how to do this: See here about common MSFS flight plan issues: https://albar965.github.io/littlenavmap-faq.html#flightplan-msfs Also make sure that LNM and MSFS scenery libraries are in sync. Check "Select Automatically" in LNM menu "Scenery Library" -> "Navigraph". Also reload the scenery library database after simulator updates. Alex

I suppose you use "Export Flight Plan as MSFS 2020 PLN". More information would help, e.g. the text of the warning dialogs (copy and paste with the mouse). The flight plan and maybe a screenshot of the plan in MSFS. What options are checked in menu "File" -> "Export options"? I recommend them all off. MSFS has its problems importing flight plans an behaves erratically at times. Alex

Thank you for the kind words.🙂 LNM knows only timezones if they come from the simulator. This is the current local time in the progress window. But it does not do its own timezone calculations nor it has a timezone database. Showing time zones on the map is a bigger task, more for a future release, if at all. This is a complex task due to daylight savings time which differs in countries/states/provinces when it starts and ends. No sure if I want to do that, sorry. I use only UTC for all time when flying and compare this to the dawn and dusk times shown for an airport. These are also shown in UTC. Alex

Yes. And use one of the Zip archives without installer: https://github.com/albar965/littlenavmap/releases/download/v3.0.6/LittleNavmap-win64-3.0.6.zip In contrast to the installer, you can change all the files there. Alex

You can still install into any folder from the Zip files. This allows you to edit the shortcut of the stock maps or to remove them. Do not remove the OpenStreetMap since this is used as a fallback. Alex

Did you install using the installer or the Zip? Try the installer if not already done. Also use the latest one 3.0.6. The UAC virtualization separates a program into its own space/folder which means that you cannot load and save files anymore. So it's normal and a good thing this is disabled for LNM. What are the last lines in the log file C:\Users\YOURUSERNAME\AppData\Local\Temp\abarthel-little_navmap.log ? Maybe LNM is open but frozen at exit or startup? Or the main window is off-screen since a monitor was removed? Is it still visible when doing Alt+Tab? Alex

You can add an element "<shortcut>" to the map themes you need. From the changelog of 3.0.6: See here for an example: https://github.com/albar965/littlenavmap/blob/421431f1120f29dd4eb7a966c61340d3a559ced2/marble/data/maps/earth/opentopomap/opentopomap.dgml#L17 The shortcuts should not overlap with the ones used by the stock themes. These are fixed. Note that you need to use the latest 3.0.6 for this. Previously it was assigned more or less randomly depending on installed user themes. Ok. Will update. Alex

Good to know. Anyway I better skip the correction when loading from the command line. Alex