FS2020 crashing when I use Little Navmap 2.8+

[Babaleia 0]

Hi.

I love little navmap. An awesome app! But my flight simulator is crashing when I use any little navmap 2.8+.

How to reproduce:

- start in an airport (I'm using the a320 fbw) with the zoom all in

- after the take off the simulator crashs after 1-3 min

If I dont zoom in at the airport everything goes fine but if if I zoom in during the flight it crashs sometimes too.

 

It crashed about 10 times on 2.8.8. I downgraded to 2.8.7 and crash a few more times. Now I'm running the 2.6.9 and its running smooth.

I was discussing this last week with other people with the same issue on the microsoft forum. Here:

https://forums.flightsimulator.com/t/little-nav-map-2-8-7-crashing-msfs-2020/576264

Any help would be great.

Thanks in advance!

Marcelo

[albar965 1,043]

Hi Marcelo,

I have absolutely no idea what can cause these MSFS hiccups. Have not seen this yet here. It can happen that this is probably caused by some sort of SimConnect conflict if other tools use the same interface. This is normally no problem but one never knows what triggers such errors. Just guessing.

Did you try the MSFS SU12 beta? I see at least two annoying problems fixed there: Active pause and moving waypoints to the North Pole when loading plans.

Can you confirm it really started with LNM 2.8.7? Might be a hint for me what change causes this.

I'll try a few shots into the dark:

1. Try stock aircraft.
2. Avoid other tools also using SimConnect just for testing.
3. Disable all traffic in the LNM connection dialog.
4. Install the redistributables as linked here in this FAQ section: https://albar965.github.io/littlenavmap-faq.html#no-simconnect

Alex

 

[thecanarian 16]

I have lnm running on a networked PC, and recently I have been getting CTD's when starting an approach or towards the end of a long flight. Very frustrating. I no longer engage littlenavconnect, and navigraph simmlink and the last couple of longish flights have been free of ctd's. I suspect (and I have no evidence of this) that a recent update to MSFS has tweaked simmconnect  to trip up mapping software that isn't paying dues to Microsoft. 

[albar965 1,043]

Might be a conflict if more than one application uses SimConnect. This is *normally* no issue but I've seen all kind of problems with MSFS already.

You can try to run only one of LNM or Navigraph simlink if this is a conflict.
Sorry, I cannot help more with this. It should be reported to Asobo if it can reproduced reliably.

Alex