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.

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.

2 hours ago, cristi112 said:

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.

Maybe, but this step is required. Otherwise flight planning will be very limited. Your settings are ok.
LNM does not use the old navaids despite showing 1801.

I have to check if LNM reads the VORTAC and TACAN declination correctly or if MSFS 2020 simply provides wrong values.

Alex

Also: LNM shows this as TACAN in MSFS 2020 which is not correct since it is a VORTAC. All other simulators and Navigraph data is ok.

Alex

Let me know if I can help you tshoot.

16 hours ago, cristi112 said:

Let me know if I can help you tshoot.

Thank you but I can already reproduce this here. Your detailed report already helped a lot. 👍

LNM creates TACANs for all VORTACs and this only affects MSFS 2020. Additionally it messes up the declination for these. 
I'll fix this for the next release.

Alex

@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.

14 hours ago, cristi112 said:

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?

See options on page "Map Labels" in branch "Top of Map". You can hide the text and the pointer there.

14 hours ago, cristi112 said:

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.

Sorry, I don't understand. Seeing what below a certain AGL?

Alex

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.

 

Not sure if I missed it but having problems with importing userpoints via csv file. Getting error.

Detail: Can no longer import csv file which contain userpoints. (Using MSFS2020 and/or MSFS2024) 

I am using LNM the portable version (non-install version : LittleNavmap-win64-3.0.16.zip which I use when flying in msfs2024)  

but also have the 3.0.12 LNM (non install version) on my system for when I am flying 2020).  (Can't import userpoints from csv on this version either for some reason).

On 3.0.16 I am getting the following error message when trying to import any csv file:  

[img]https://i.imgur.com/mW8Td6J.jpeg[/img][img]https://i.imgur.com/mW8Td6J.jpeg[/img][img]https://i.imgur.com/mW8Td6J.jpeg[/img]

Do I need to use the install version of LNM (to invoke registry paths/settings? or is there something else I need to do to fix the csv import error?

Thanks in advance for your help on this. If you need any other info just let me know.

Norm Richards ([email protected])

28 minutes ago, nbrich1 said:

Do I need to use the install version of LNM (to invoke registry paths/settings? or is there something else I need to do to fix the csv import error?

Thanks in advance for your help on this. If you need any other info just let me know.

You probably ran into a bug that left the undo/redo function in an inconsistent state. This was fixed some time ago but the databases still can cause issues.
Reinstalling LNM does not help and use only the latest 3.0.16.

How to fix:

1. Export all your userpoints to a CSV file.
2. Quit LNM
3. Delete the file "C:\Users\YOURUSERNAME\AppData\Roaming\ABarthel\little_navmap_db\little_navmap_userdata.sqlite"
4. Start LNM and import the previously exported CSV file again.

Hope this helps.

Alex

 

Thanks so much Alex.. Done and FIXED! 

Appreciate it sir and best regards

Norm

 

 

Edited March 30, 20251 yr by nbrich1