Press Ctrl+Shift+O or Show all in the context menu. No need to scroll down. I’d always use a filter on aircraft or other to avoid showing really all entries. This can slow down LNM until it freezes.
Sry, rather not. I’d use this function only with a filter as described above to avoid slowdown.
It’s a bit hidden in map context menu → More → Show Logbook Entry in Search. This pre-fills all the search fields to show the logbook entry (mostly only the selected but maybe more). This works for all map features like airports or VOR.
Context menu on logbook entry and Files → Open attached flight plan. Ok, this is only for one plan.
The altimeter reads indicated altitude. LNM is showing true altitude above sea level. If the ambient pressure and (especially) temperature are not standard, your true altitude could differ considerably from indicated altitude. I don’t know what your air temperature was, but if it was above ISA (very likely at lower altitudes in summer) your true altitude will be higher than indicated. The difference can be substantial.
Yep, I’ve never seen it this way before, but wanted to report it in case it was reproducible elsewhere. Otherwise, my recollection is that altitude readouts match - in-cockpit, aircraft tab, moving map.
After WT modified the atmosphere in MSFS back around SU7 to work like the real atmosphere for non-standard temperatures and pressures, indicated and true altitudes will rarely match. LNM is showing both indicated and true altitudes.
Here is a r/w example from the Globe ADSB tracking program. This screen shot (taken just a few minutes ago) is showing traffic near my location.
ROU1883, an Airbus 321 is flying at FL310 pressure altitude - referenced to standard pressure of 29.92. 31,000 feet is what the pilot would see on his altitude display.
The “WGS84” altitude comes from the aircraft GPS, and shows true altitude MSL. The aircraft is actually flying at 32,175 feet MSL - over 1,100 higher than indicated.
What’s your QNH setting? (I don’t know where to look on the G1000 panel because I never fly aircraft that have them, but I didn’t see it looking at your screen shot.) According to my E6B, your true altitude should be about 500’ higher than your pressure altitude at that flight level and OAT. If your QNH is set to 29.92, your true altitude isn’t too far off that.
Thanks. Missed it. The difference between 29.83 and standard is only going to make a difference of about 90 feet, so it seems LittleNavMap is in the right ballpark.
Is anyone having problems uploading flight plans into the sim since the Avionics update?, it doesn’t seem to be reading waypoints for me?, I normally put a manual waypoint about 15 miles from the airport but it doesn’t seem to be reading it, I fly IFR in a 747 btw
Most likely an aircraft issue. LNM can export only the coordinates and waypoint names and these are correct so far. Did you try the rc1 I posted above? It has some changes in the PLN export. Might be as well triggering the issues you see.
Alex
Sorry, but this is unlikely to happen due to the complexity in the elevation profile which already has to deal with the altitude restrictions in the procedures. Maybe if I have an idea how to solve this but not soon.
