somiller

Is it possible this memory leak is also causing the EFB to be heavy on cpu use. I have a measly 6700K but the EFB app uses 6%-12% cpu cycles - it's killing performance for me. I had pretty good performance with the previous Max ver., I would say on-par with the PMDG 737's.

It would be VERY handy to have LNM "load scenery" able to only scan user selectable directories for only new or updated airports and just append them to the scenery database. That would save a ton of time loading scenery for those of us that use Addons Linker and store our user MSFS assets outside of Community directory. If you could create a load scenery option to only search user directories for times we only need to detect new 3rd party airports that would be very helpful. For example I just bought Aerosoft EDDS on sale and would like to add it to LNM scenery database, but a databases scan take 45 min. on my system.

My brother and I flew his Cherokee 180 from Henry County, OH 7W5 into Meigs on Sept. 10, 2001 for a big printing show at McCormick Place, flew back out that evening after a beautiful walk from McCormick to Meigs under clear skies and about 75 deg. Next day, Sept. 11, 2001 did the same flight to Meigs but never made it...on the way in we were listening to Gary approach talking to a KingAir - Controller: "the FAA has issued a nationwide ground stop, land at the nearest suitable field or return to base." The KingAir pilot begged to be able to get his passengers to Valparaiso but the controller just repeated the same command. Since I'd never heard of a "nationwide" ground stop (neither of us had) I decided that was a good time to let my brother handle the comms and call the Gary controller to see what was up. He repeated the same command to us and said "when you get on the ground turn on the news." We made the mistake of landing at Goshen, IN. My brother's plane stayed there for two weeks and then he had to pay a CFII to fly it back to 7W5 on an instrument flight plan. These were a couple of MANY flights into Meigs and I'll never forget how cool it looked on final to 36 with the city skyline, Soldier Field, the museums and McCormick all right there in front and beside you. I was very angry when that jack@#$ Daley had X's ripped into the taxiways and runway in the dark-of-night. On the 1 year anniversary of 9/11 we took a commercial flight out of DTW to Manchester, NH - when we got to DTW around 8 am the airport was like a ghost-town - there was 1 person standing on the walk in front of departures and inside we probably didn't see 50 people all the way to our gate. Pretty uncommon for DTW any day at 8 am. Guess everyone else was afraid of a repeat.

V1ROTATE, I'm guessing United Airlines.

During install I believe it offers an option to start Couatl with MSFS - either select yes or you will need to start Couatl manually. In Windows Start menu you should have an FSDreamTeam folder and within should be a Couatl shortcut to start Couatl. If you right click Couatl in the start menu, select "more" then select "open file location" which should take you to the shortcut. Right click the Couatl shortcut then select open file location which should take you to the the location of Couatl64_MSFS2024.exe. Try double-clicking Couatl64_MSFS2024.exe to see if it launches.

Please go back to "old" avsim format prior to about 3 days ago.

Scott, The ignore feature on AVSIM works REALLY well...suggest you try it.

I've also seen the freezing aircraft. sometimes on taxiways, and other times on runways - after lining up for takeoff, and also after landing rollout.

I'm really curious about the aig-aitraffic-effects_CVT_ , what is it? I don't have that one in my AIG install.

SayAgain, Karens gotta Karen - they can't help themselves. The idea that culling landing gear at a certain distance is going to improve performance when landing gear represent infinitesimally small percentage of vertices in an airport environment is so ludicrous it's really difficult to try and speak about it with any seriousness. I'd like to hear the argument that was used to incorporate this idea into MSFS 2024. Even on my week system it's not like I see a performance improvement when landing gear disappear. And as SayAgain mentions how hard would it have been to included a slider setting that allows us to control the aggressiveness of the culling.

I'm curious for those that use multi-monitor setups - how do you handle monitor calibration so all monitors color-match? To me there is nothing more annoying/distracting than multiple-monitor setups with monitor colors that don't match.

LittleNavMap aircraft labels used to show origin and destination for most PSXT controlled AI with MSFS 2020, but origin and destination seem to not be available for PSXT controlled aircraft when using LNM with MSFS 2024.

Absolutely NOT 1300 feet away. If it were 1300 feet away I'd barely be able to see them, if at all on my 1440p monitor. I'd go along with maybe 300-500 feet, but not beyond. I wanted to test what I wrote above so I loaded a flight in MSFS 2024 and found something VERY interesting that seems to have solved the gear problem, at least for me. I use ChasePlane, but the same thing can be done for views setup in MSFS - I use a zoom factor of 0.76 to provide a realistic field of view (magnification) calculated from a tool here https://www.avsim.com/forums/topic/669373-how-to-easily-set-up-a-realistic-field-of-view-fov/#comment-5440264. I use ChasePlane but views setup in MSFS can also be customized to alter zoom. From my cockpit view with zoom 0.76 landing gear on AIG AI appear at quite a long distance - further than I can distinguish on my 1440p monitor. From an external view with a default zoom factor of 0.53ish landing gear are missing beyond a range of roughly 300-500 feet. When I went into CP and changed the zoom to 0.76 for my external views...all the missing landing gear appear and are visible beyond ability to distinguish whether they are there or whether they aren't. So zoom may affect gear visibility. I messed with OLOD and could make gear appear and disappear at varying distances, but not equally on on AIG models. On some the gear disappears within 500 or so ft. at OLOD 100, and yet other models the gear doesn't disappear beyond my ability to see them on my monitor. So I think we have several factors affecting gear visibility, including inconsistencies between models of AIG aircraft. As far as path to default models I'd say here: MSFS2024\StreamedPackages which contains these:

SayAgain is referring to the landing gear culling issue that we all see with AIG, FSLTL, etc. liveries. At a certain distance (which is a rather short distance) the landing gear disappear from AI traffic. We've all been dealing with this for some time and it really looks ridiculous to see aircraft taxiing around you with no gear looking like they're magically levitating. I've done some tests while sitting at a gate a moving around in external camera and as you move away from AI the gear disppears, then if you move closer they reappear - all very repeatable. Clearly it is caused by MSFS 2024, I suspect for performance, but I would argue there are other scenery areas of lower importance that could be culled instead that would provide an equal performance improvement. The worst thing about it is that those with high performance systems don't need the performance help from culling, and some of us with lower spec systems would be happy to give up a small bit of performance to NOT see levitating AI.

I would suggest you will probably need to add an lfolder entry pointing to the location of stock MSFS AI, then try unchecking the automatic checkbox and run a livery scan. Throwing darts but that is where I would begin.