somiller

I saw the same issue yesterday at KDCA - aircraft departing on RWY 19 were rolling to the very end or slightly past the departure end of the RWY before rotating and climbing. Interestingly all arriving aircraft to RWY 19 were touching down almost exactly on the 1000 ft. marks.

Pretty sure it's in the EFB. I'm going to be firing up a flight shortly so I'll check and report back.

I got the WASM crash during 1st flight of 738 since updating to the supposed WASM fix update - occurred on rollout after landing. Previously on all other versions since the 738 original release I had exactly a single WASM crash.

Well I'll give it a try. I hadn't updated to the previous 737 update because of the reported issues with saved panel states. The latest update, according to Randazzle supposedly fixed the issue with panel states, so I thought great lets update. WRONG - first flight WASM crash on rollout after landing. Previously I had experienced only 1 WASM crash across all three models 737, 738, and 739 since purchase when they were released.

I'm using FFB-Bridge with Moza AY210 yoke base and at least at this point it provides better control loading than Moza Cockpit. The problem I have with Moza Cockpit is elevator friction - using the Moza function to reduce elevator friction introduces a break-away force required to move the elevator axis from a resting position. Ex.: while flying with aircraft pitch trimmed to fly level if one wants to input a minor pitch correction one has to overcome a momentary resistance before the yoke moves and once past that stiff point less force is required - makes it impossible to make small pitch changes. Using FFB-Bridge I don't get that force. Unfortunately it seems impossible to lower elevator friction using FFB-Bridge. It's like friction is programmed into the base and Bridge can't eliminate it.

I can use the FMC with PMDG 737 and 738 but not 739 - when I load the 739 it locks up MSFS 2024 and I have to kill the sim from task manager. When this happens I end up with an error in Win 10 application error logs - SimAppPro WASM crash, which takes out MSFS 2024.

Same here with the PFP3N. For some reason anytime I try to load PMDG 739 with PFP3N and SimAppPro it causes a SAP crash (as indicated in Windows error logs) and takes out MSFS. I did an online support session with them on remote access to my PC (23:00 my time) for over 4 hours to accomplish nothing. I can use it with PMDG 737 and 738 but not 739. It's been 3 months and I've still not figured it out. I've even tried with MOBI and still get the crash.

Has anyone sent Nico a TBLO for the new EDDF? Until that happens and Nico has a chance to run learner on it and include it in the archive there will be no parking at the new terminal. Without the updated archive as far as PSXT is concerned the new T3 doesn't exist.

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.

I could be wrong, but at the end of the ini dev update there was this: "But as one chapter begins to unfold, another is already taking shape..." followed by a picture of a bizjet with reg. HB-JFX. HB-JFX is registered to a Global 6000 operated by Rolex SA - is that the next chapter taking shape, a Global 6000? https://www.planelogger.com/aircraft/Registration/HB-JFX/873626 https://www.flightradar24.com/data/aircraft/hb-jfx Of course maybe it's just a picture of an AI traffic aircraft.

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.

IGNORE