• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Little Navmap flight planner - beta released

gaabne said:
I are the boss ;) and I understand your approach.
Click to expand...
Me? Boss? Not necessarily.:)
You can get the sources here, apply whatever changes you want, read the build instructions, compile it yourself and then you have you own personalized version.
Just saying.;)
Alex
 
Hello Alex,

albar965 said:
Hi Gérard,
Regarding "map" and double click: Sorry, but I'd like to keep the behavior consistent across all windows (route, search, etc.)
Alex
Click to expand...

I just discovered that "map" in "Simulator Aircraft" follows the value in the [Zoom distance for double click or "Show on Map" menu item], while Airport, or Search (I suppose Ctrl-M is the shortcut for "map" ?) don't...

May be the option for "map" could be separated from the option for "Double Click" ?

I appreciate a lot Little NavMap si I hope you don't feel harassed by me ;).

Regards - Gérard
 
Hi Gerard,
I changed that already. Now all map-links/doubleclicks/"show on map" zoom to the given distance. But with one exception: If an airport does not fit on the the screen it will zoom out more than the given value.
Maybe I can add a separate option for all double clicks.

Alex
 
albar965 said:
Maybe I can add a separate option for all double clicks.
Click to expand...
Oh, yes, please - this would allow to have both possibilities
- detail with double-click (interesting when landing or taking off)
- overview with "map"/Ctrl-M (nice to setup a flight plan to explore the surroundings -bush flying...).
for example...

Gérard
 
Hello,
Sorry to report another small hitch : don't know if it should be considered as a bug.

It concerns detail airport map of KBHB by Orbx.
See the screen shoots on https://www.dropbox.com/sh/s9icchww01w38e2/AAD-gx7LyNsKMXeNr_f5d-EHa?dl=0

You can see that the runways are displayed with a description of "Invalid", where there should be the surface type.
I have open the corresponding bgl with ADE. You can see that the surface type of the runways is Asphalt. On the center line there is also a taxiway.

I cannot upload the bgl file (copyright...), but if you need, I can look for further details.

As you are in the process of updating Little NavMap, I thought it could be usefull for you to know...

Gérard
 
Hi Gérard,

I just checked that airport and ADE 1.7 shows me a runway surface of 132. Orbx is using one of these tricks to avoid the default runway surface showing up.
I applied a workaround and now it shows asphalt as a surface. This should also work for other surface types that have this trick applied.

There are taxiways that go over/along runways in the simulator database but I ignore these since they do not provide any useful information for the user.

Thank you for reporting

Alex
 
Does the "master" branch of LNM include the new built-in SimConnect interface?

I'm tempted to try compiling a snapshot. You use MinGW, right? Do I need QT libraries as well?
 
Hi Bjoern,

the master branch is the unstable development branch and does include the simconnect interface.
I use MinGW now to compile everything.

Problems: I didn't update the build instructions.
You have to build Marble which is a pain since they do not maintain their Windows build very well.
If you want HTTPS and the OpenTopoMap you even have to compile Qt yourself.

Alex

PS: I sent you a PM.
 
Hello Alex,
I am "playing" with your last beta 1.2.2. Great to see so much additions to it. I like it more and more :).

I think I found a bug in the display of the Flight Plan Elevation Profile, while connected to FSX Acc, tracking my aircraft.
As usual a picture is much better than a long explanation. (see aircraft outside at the right of the Elevation Profile).

Little_Nav_Map1_2_2_beta.jpg


The vertical blue mark line is in phase, it is only the symbol of the aircraft which is shifted.

Little_Nav_Map1_2_2_beta_1.jpg


Don't hesite to ask any detail that could be usefull for you.

Gérard

BTW : Happy New Year !!
 
Hi Gérard,

a Happy New Year too!

Thank you for the report but I cannot reproduce this so far.
You're on track and flying in the right direction so I don't know what is wrong.

I know that funny bug where the aircraft flies backwards after passing the destination or that things like this can happen for a short time when the elevation profile is updated but this one is new.
Does it happen often?

I saved your pictures and will add them to a Github issue for later evaluation.

Alex
 
Hello Alex,

I investigated a little bit more.
I tried the same flight and get the same shift between blue line and aircraft on the Elevation Profile, since the departure.

Shift1.jpg


I had a similar shift, but less obvious on another SHORT flight plan.


Shift2.jpg


On a much longer flight plan, the shift is not visible, probably due to the scale.

Which rise the following question : any plan for a zoom on the elevation plan ?
On the next version will there be ground elevation display everywhere ?

If you need more details, please ask.

Gérard
 
Hi Gérard,

Regarding the upper case: That was a problem with the Marble library not giving enough points when calculating the elevation. I added a workaround for this and the distances are now correct.
Additionally I found another problem that the magnetic variation was not used correctly when calculating the flight plan course. Also fixed.

Regarding the lower case: The aircraft has a distance to the nearest/next flight plan leg that is projected on the elevation profile which moves the aircraft right. That distance is the one between the starting position at runway 25 and the airport center. Normally not noticeable except for short flight plans. For the same reason the aircraft flies backward if you pass the destination.
That needs a more elaborated solution in the release after 1.2.

Edit:
About elevation profile zooming: I planned this but cannot promise when it will make it in.
About the coverage of the elevation display: I'm using online data and the Marble library now and plan to use other data source in the future because this has to many problems IMO.

Thank you for the detailed feedback! Very helpful!

Alex
 
Last edited:
Little Navmap stable Release

See the Changelog in the online manual for comprehensive list of changes since version 1.0.5.

Little Navmap Links

Release page on GitHub

Direct download link Windows

Direct download link macOS

Little Navconnect Links

Release page on GitHub

Direct download link Windows

Changes from 1.2.2 to 1.2.4

Version 1.2.3 was an internal release only.

The program will start with a default window layout. You have to rearrange your dock windows again.
Users updating from 1.0.5 need to erase and reload the scenery library database.
  • Removed central map window and moved map to dock window. Docking windows are much more flexible now.
  • Added missing localizer and backcourse ILS frequencies to approach information.
  • Fixed problem with disappearing route due to airport overflow on map.
  • User aircraft track is now cleared if user aircraft jumps too far due to airport change or for other reasons.
  • All known problems in macOS fixed: Map is now centered on last position. Overlays are available again. KML loading and centering is working.
  • Solved display issue in route table where texts lost bold attribute.
  • Problem fixed where program unnecessarily assigned a default runway as departure position.
  • User defined waypoints are now length limited when parsing flight plan descriptions to avoid problems in flight simulator.
  • Fixed automatic numbering of user defined waypoints for flightplan containing user defined coordinates.
  • Added 15 character degree/minute/second coordinate format as used by Skyvector to flight plan route description.
  • Fixed problem with wrong distance and other wrong indications in elevation profile for some flight plans.
  • Fixed missing magnetic variance correction on flight plan course in certain cases.
  • Fixed problem when zooming in to small flight plans.
  • Solved problem where terminal waypoints of add-on airports were deleted.
  • Invalid navaids are now omitted.
  • Jetway indication for gates is correct now.
  • Changed flight plan saving to ensure better compatibility with third party tools.
  • Fixed wrong (negated) UTC time offset on user aircraft display.
  • Updated manual.
  • Cleanup in dialogs. Updated tooltips and tab order.
 
Hello Alex,

A very small "bug" in the Flight Plan Elevation Profile when docked full bottom part of the windows : the height can be increased but after refuse to decrease...
If docked on the bottom right side (same width as the map and full left side column for Flight Plan and Airport information) the resizing works as expected.


Thanks - Gérard
 
Hi Gérard,
this is a known problem. Strange enough it happens only on Windows.
I think you can resize the window again after undocking.
The Qt dock windows sometimes have a mind of their own.
Alex
 
Hi Alex,

I was suspecting QT... And I had already discovered the undocking/docking trick ;)

Thanks - and waiting anxiously for the next release :)

Gérard
 
First, thank you for an awesome product. Little Navmap is an invaluable tool for me.

My question is regarding the vertical profile map. Maybe I'm loosing my mind, but I thought I used to see a TOC as well as TOD, but as you can see, I have only a TOD marked on my profile.
32660252186_db44341d16_b.jpg


Am I going senile, or is there supposed to be a TOC? If there is, any idea what I've done to turn it off?
 
Hi Dan,

there was never a TOC since no aircraft performance is available yet. Only the TOD is displayed and calculated by the simple 3,0 nm per 1000 ft rule (or whatever you set in the options).

Alex
 
You must log in or register to reply here.
Back
Top