albar965

Answered below. The SimConnect variables come from FSX and are not documented for MSFS but they work when reading. Perhaps it's simply a matter of the developer filling the two in. Alex

LNM does not provide a full screen in its webserver (only the main application has it). This is entirely a client function. I use Brave on Android and it moves the tab bar out when scrolling down. Maybe try Brave or Vivaldi. Alex

I know https://ourairports.com/data/ and https://www.openaip.net Alex

This can be a large aircraft trail. Try menu "Map" -> "Delete user aircraft trail". Maybe have a look at options page "Map Aircraft Trail" and reduce the number of points. Airspaces are also very taxing. Or reduce the detail level in menu "Map". Or menu "View" -> "Reset map display settings" and as a last resort "Tools" -> "Reset all settings and restart". The latter one will reset everything back to default I'd also exclude the LNM installation folder and at least the settings folder C:\Users\YOURUSERNAME\AppData\Roaming\ABarthel from anti-virus scanning. You can create an issue report in menu "Tools" and send it to me if all this does not help: https://albar965.github.io/contact.html Alex

Install the Windows version of LNM in the Proton environment and then generate the scenery library databases. You can copy the databases to the Linux installation then. You can treat the Proton and Linux installations like two separate computers. https://www.littlenavmap.org/manuals/littlenavmap/release/latest/en/NETWORK.html Alex

What do you expect if you put in wrong values like a too high cruise altitude? The profile simply cannot be calculated and shows a red error message below the flight plan table (see screenshot above). Nothing odd at all.🤷‍♂️ Alex

@john9002 you gave zero information about the issue and I already answered your email. Obviously at least a screenshot or the flight plan is needed to diagnose any issue. But first have a look at the flight plan table. Below the table is a red error message that gives you hints why the profile calculation failed. Hover the mouse over the message or click it to see details. You can use the flight plans in X-Plane even with a failed profile calculation, BTW. Alex

This is just one of many issues MSFS has with flight plans, by the way. See here in the LNM FAQ: https://albar965.github.io/littlenavmap-faq.html#flightplan-msfs Alex

LNM already limits the waypoint names. I'll have a look at it. Noted. Alex

What LNM add-on do you use? I cannot help much if LNM shows the line on its own map and on the web server page (menu "Tools" -> "Open web server page in browser"). I'd rather contact the author of the add-on. Alex

I use the two variables "AI Traffic Fromairport" and "AI Traffic Toairport" when requesting data for AI traffic. Looks like these are still from FSX and can be requested from MSFS although not documented. https://github.com/albar965/atools/blob/79316ebe1bca68aa9904fdf6da6a386f18e1fba6/src/fs/sc/simconnecthandler.cpp#L703-L704 Alex

SimConnect provides this information. Not for all simulators. Alex

Just moved to the right one (hopefully). Alex

Wrong forum?

I already added an optional precision mode for the next release which uses more accuracy for distances and courses in the measurement lines. This also covers the radial. This feature is intended for scenery or procedure developers. I doubt this makes sense for flying. The two numbers you see are the start and end course of the Great Circle line (Measure Distance). These appear for long measurement lines. Alex

Looks different here. The wind barbs are normally much bigger. Go to options on page "Map Display" and change the size back to 100 percent. Alex

No. Either there is already a stock airport/helipad or an add-on providing one. I cannot change the limitation which is entirely simulator based. Most simulators cannot place you at an arbitrary coordinate. You can move your aircraft to the position in the sim (dragging on the simulator map?) and still use LNM for flight following. Alex

That's the limitation I forgot to mention. While LNM can deal with such plans most simulators and add-ons can not. You need an airport add-on to start from there. Alex

The userpoints are a special thing. LNM does not "know" if such a point is an airport or not. But you can add arbitrary points to a flight plan anyway. You can right-click on a userpoint and select "Add/Append position to flight plan". LNM will create a user defined waypoint in the plan taking the user point name. You will even get an elevation profile if you have the GLOBE data installed. You can click anywhere on the map and add the position to the plan. Below is a "plan" from a userpoint "Helipad" to a point on the map. Alex

Deselect "Map Tooltips" -> Airspaces on the shown page to disable this one. Alex

Options -> "Map Tooltips and Clicks". You can also disable tooltips for the whole application In "Display and Text". Alex

A copy protection system. DRM (Digital Restriction Management). Alex

Maybe a problem with DRM: https://albar965.github.io/littlenavmap-faq.html#no-airport-msfs Alex

The above is related to the calculated flight profile. https://www.littlenavmap.org/manuals/littlenavmap/release/latest/en/PROFILE.html#tooltip-label Alex

MSFS 2020 and 2024: totally different handling there by LNM. MSFS 2024 will read these navaids and will deliver them through SimConnect to LNM. Provided, these navaids are linked to a procedure or the airway system. Yet another limitation of the MSFS 2024 interface. MSFS 2020: LNM reads all from BGL files (which are not officially documented, BTW). Alex