During a flight the sim freezes suddenly and after a few seconds this screen popped up and the sim crashed.
I use the latest version of LittleNavmap ( 2.8.10 64-bit.)
Anyone in this group who has a solution for this issue?
Thanks for your help and advice!
Guess, the main problem is, your sim crashed and LNM just gave you an error message because it couldn’t communicate anymore with your crashed sim. Don’t think LNM crashed your sim.
I’ve had this twice. In both cases I had MSFS, LNM running as well as Simbrief and Skyvector running in Google Chrome. When I tried to open one more thing in Google Chrome I got the same message. Another time it happened when I tried to look up a waypoint in LNM. I’m not sure, but I concluded I just asked for too much out of the memory or processor which caused LNM to get an error and fail.
I’ve had this happen on two or three occasions, with MSFS and LNM the only things running on my system. But then, from what I recall, I started a Chrome session and either right away, or shortly afterward, this CTD occurred. I restarted everything, and tried the Chrome session again with no CTD. Go figure!
Thank you for your post! Your topic has been moved to a subcategory of General Discussion & Community Support. The General Discussion category is meant for discussions that fall outside of our other sub-categories.
Please check out these other categories for your future posts:
Aircraft
is where you discuss current or future planes coming to MSFS.
World
is where you discuss scenery, airports, and weather.
Tech Talk
is where you discuss graphics, drivers, performance, CTDs, and hardware.
Menus & Activities
is where you discuss activities (landing challenges, bush trips, etc), plus anything accessed by the menus including the Marketplace, settings, logbook, cameras, etc.
Unfortunately, no, since after I restarted, it didn’t happen again, and on subsequent occurrences, I didn’t associate it with Chrome. I certainly will now though.
FWIW, It still happens. I did a fresh reboot of my computer, nothing in the community folder (thru AddonsLinker), running Little NavMap only with MSFS.
It happened twice to me today. The first time after loading and about 3 or 4 minutes after going into the aircraft on the parking ramp. Started the plane and did some GPS stuff. MSFS crashed to desktop and I got the LNM message shown above. I reloaded, again using only LNM addon. I flew for 20-30 minutes. Went back to main menu and it crashed again a few minutes later. I ran MSFS a third time without LNM on, and zero problems. I was not running Chrome or any other programs at the time.
This problems seems to come and go. It was happening occasionally with 2.8.6 and 2.8.7, and seemed to disappear after 2.8.8. I have been running 2.8.12 since it came out a month or so ago without issues until today.
The message appears whenever MSFS crashes. LNM is just telling you it is not connected to a simulator nothing more. I fly with LNM every single day…no crashes (at times for 5 hours or more). If it were causing crashes for everyone the sim world would be up in arms. Those having issues need to look else where.
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.
Im getting this problem now but only running LNM and the fenix A320 on every attempt. As soon as i start the fenix without little nav map, i cam fly fine. Its definitely something in LNM. Mind you in any other plane its fine.