• Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.

    Post 16 Update

    Post 17 Warning old domain name stealing credentials

  • Special Server Maintenance

    Just when you think you have everything running some what better...

    You get a message from the Hosting company. Short story they need to move us to a new server. I have been working with them to plan a good date for all concerned. Here is what we have come up with as a schedule.

    1. November 4th 17:00 -5UTC shut off the forums and start backup proceedures. During this time there will be no access to the forums or the Resource Section.
    2. November 5th Continue with Backups and download same until complete.
    3. November 6th 7:00 turn over server to hosting company to move system to new server
    4. November 7th - 8th restore backups and upgrade forum software.

    If all goes well we should be back online on November 8th.

    To keep you updated we will post updates on AVSIM forums.

    Thank you for your support.

LittleNavMap Error

falcon409

falcon409

SOH-CM-2026
I've been getting this error every time I try to use it with MSFS2020:

Too many errors when trying to connect to simulator.

Not matching simulator interface or other SimConnect problem.

Make sure to use the right version of Little Navmap with the right simulator:
Little Navmap 32-bit: FSX and P3D
Little Navmap 64-bit: MSFS
You have to restart Little Navmap to resume.

Has anyone else come across this or have any idea why this would be happening? Just for clarity, I am using the 64bit version. As for the line about "not matching Simulator Interface, etc, etc" not sure what it's suggesting there.
 
Ed,
I've been using LNM with MSFS2020 for over two years and have not seen any error like this.
There isn't anything in the options that you tell LNM about your MSFS location.
It looks as it may be a problem with your Sim Connect location.
I know it's no help, but maybe the old "erase and download fresh" would be a good try?
Joe
 
Well, I succeeded in flying a full flight with LNM active and no problems. One thing I did was to follow a suggestion from the LNM Forum which suggested this: Another option is to increase the setting for MaxClients entries in the file Simconnect.xml to 128 or more.
The default number is 64. I also waited until I was ready for Takeoff before loading LNM. . .prior to this LNM was already loaded before I got into the Sim. It could be one of those or both but at any rate it seems to be fixed (for now, lol).
 
Well, turns out that didn't fix the problem. My very next flight it crashed again. I was doing a tour of about 12 airports in Oklahoma that I had downloaded from flightsim "to". One in particular might be the problem so I tried again going from my home airport KGYI to a small airport north of Dallas. That trip was uneventful, even after loading LNM once the flight was in progress. Next I'll fly from home to the Oklahoma airport in question (I removed the addon scenery) and see if it causes a problem with the default in it's place.
 
Another uneventful flight into the default KMLC. In the morning I'll resume the tour and see if I have any problem with any of the remaining Airports.
 
Yep. There's nothing wrong with that for me. Let me know which one. If you find it, I'll try it on my setup.
 
I've completed the entire tour without any further errors or problems of any kind. Later this evening I'll introduce the suspect scenery back into the mix and see if it triggers an error.
 
You must log in or register to reply here.
Back
Top