cristi112

Oh, nice. Thanks, I looked 10 times and I was not able to find it 🙂 I was thinking to have the wind direction and force only in special circumstances like being low enough so a pilot might see the waves/trees being affected by the wind, but I'm ok with it being disabled.

@albar965 Glad to hear that. I might also have a little suggestion for LNM, can we have an option for the yellow wind information in the middle-top of the window to be shown or not? I didn't find anything related to it in the settings. Also, if it's easy to implement, maybe we can also have a more "realistic" implementation, like seeing it only if the plane is below a certain AGL, GPT says 2000-3000 for land cues like trees and 5000-10000 for waves.

Let me know if I can help you tshoot.

Actually I'm not I'm using ariac 1801, I have "Select Automatically" on the navigraph sub-menu. I think it all started when I did this: Scene Library - Load Scenery Library - Load, which loads all the airports/navigation points from the simulator.

MSFS2020, littlenavmap version 3.0.16 with airac 1801 (I think is the one that comes by default?). I have the magnetic start and end course checked and it works fine with VOR/NDBs, just those VORTACS are having this strange behaviour.

Vortac radials are displayed wrong in the flight plan. For example going from vortac RQZ to 7A6 shows a 86°M but if I'm doing a measurement from RQZ to the airport it shows the correct value of 80°M. I think it will be better to show the radial when the source of a leg is a navigation aid just like when we are doing measurements.