Jump to content

albar965

Members
  • Content Count

    3,117
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

712 Excellent

9 Followers

About albar965

  • Rank
    Little Navmap Developer

Contact Methods

  • Website URL
    https://albar965.github.io

Profile Information

  • Gender
    Male
  • Location
    Germany

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

11,362 profile views
  1. There is also a nice tool to remove all the quarantine flags from all the plugins: https://forums.x-plane.org/index.php?/files/file/79828-mac-os-cleanup-quarantine-flags/ Alex
  2. The folder is ".../X-Plane 11/Resources/plugins/". It's always there since it contains the X-Plane plugin manager. Alex
  3. Hi Dane, this can only done by modifying or adding an airport add-on but not in LNM. You'd have to use the MSFS developer tools to do this. Alex
  4. You can try to clear the LNM map tile cache in C:\Users\YOURUSERNAME\AppData\Local\.marble\data\maps\earth\ . Remove a folder like "openflightmaps". Or contact the OFM author. Alex
  5. Aircraft perf does not affect the logbook. You can check here for aircraft performance files: https://www.littlenavmap.org/downloads/Aircraft Performance/MSFS/ You can send me the LNM log file (menu tools) from such a flight. Maybe I can read something from it. Alex
  6. Maybe a add-on selection in LNM can help but I'm too busy with all kind of stuff around LNM. The solution of somiller is the best so far. Alex
  7. Did you quit LNM during the flight? This can cause issues like this. Was a flight plan loaded in LNM? Fuel information might be missing if an add-on "doctors" around simulator limitations and does not provide proper values on the SimConnect interface. Alex
  8. Enable it in menu "View" -> "Show selected altitude range". It should show the range based on the selected autopilot altitude (you can show this in the progress tab). LNM depends on aircraft playing nicely with the autopilot altitude. I have some add-on aircraft which use the autopilot altitude variable their own way making this feature unusable. Alex
  9. There are a few ways to configure zooming to your liking LNM option on page "Simulator Aircraft". See here about the details: https://www.littlenavmap.org/manuals/littlenavmap/release/2.6/en/OPTIONS.html#simulator-aircraft The default is to zoom to aircraft and next flight plan waypoint. You can move and zoom around the map manually and it jumps back to centering after an adjustable timeout. Or disable all zooming and centering in "Map" -> "Center Aircraft". Edit: I doubt this zooming is very demanding except you set map details too high. Also exclude the LNM settings and database folder C:\Users\YOURUSERNAME\AppData\Roaming\ABarthel from anti-virus scanning. Alex
  10. No problem. 🙃 BTW: You can exclude unwanted add-on from yellow ring display in LNM options on page "Scenery Library Database". Add the folder to the lower list. Alex
  11. Now this is really strange. Can you post the section "Scenery" with the BGL paths from the airport information from one of the stock airports? Do you use an add-on management tool? Are the add-on airport folders symbolic links or something? Alex
  12. Did you reload the scenery library? This is required to fix the issue.
  13. Perfect. 🙂 This might have caused the issues if you use the included old AIRAC cycle where navaids do not match MSFS navaids. Alex
  14. No problem since I'm also the developer of this tool (and the core of this tool is a part of LNM) but you better send me an email or post in the Github discussions for LNM which is more for development/database stuff. The log messages are mostly internal/developer and therefore are not formatted nicely. I already reduced a lot of the warnings for MSFS recently since there comes a lot of weird stuff from the scenery library. Looks like I have to check again. Not sure what this means. Frequency out of range? I just fixed a bug in the loading code (other post in this forum) where I found frequencies of value "0" in MSFS data which is actually not correct. Another weird thing from MSFS. These were probably introduced with one of the latest MSFS updates. Alex
×
×
  • Create New...