Jaxsimmer

Normally I cut Asobo a lot of slack. But right now I am fuming. A perfect flight from DAL to TPA completely ruined because of this idiotic behavior of the Xbox controller to light up and capture random items at the worst possible time. I was on a half mile final with the PMDG 737, perfectly setup to land after a flawless flight, and lo and behold, somehow the RESET button on the 737 panel is captured by the hidden (apparently), formerly banished, invisible white dot, and totally locks up any action of the controller, including the throttles, the control surfaces, and the ability to move the camera. And the only way to free everything is to hit the escape key on the keyboard, stop the flight, and resume? And of course, at that point your approach is completely ruined. What genius designed this behavior? Like I said, I am normally super supportive of the developer, having an IT background and understanding how complex this software is, but this just makes me madder than you know what. Yeah, I know, first world problems, but give me a break. Jaxsimmer

I appreciate the help. Like I said, the issue seems to be solved with the latest update. Yes, I had removed everything from the community folder and tried to shutdown any other programs I could think of. It was almost like the main thread was locking up for an instant at regular intervals.

This sim is more temperamental than both my ex-wives combined.... Just got home, fired it up, apparently it downloaded the latest SU5 update, .22, and we are back to smooth as silk performance, no stuttering, and no sound hiccups. That's at 3440 x 1440 and landing at X-Codr KDEN. Asobo, I have very little gray hair left to pull out...but thank you... Jaxsimmer

I sure wish that was my situation. I have a 5090, AMD 9800X3D, 64GB RAM, 1TB SSD, 1000 watt power supply, clean Windows install in a Dual Boot config, empty community folder, 1GB fiber connection and the &$@!# thing stutters every ten seconds with this latest .21 beta build. The audio crackles every time it does it. The frame counter turns red for an instant, then green for a period, then rinse and repeat. VRAM usage is low, regular RAM usage is low, it’s set on 40 frames max. Nuts.

This post takes me down memory lane. I started my IT career in 1980 at 23 years old, fresh out of college, selling Apple IIs with 48KB of RAM, a green screen, two 143KB floppies, and an Epson MX-80 printer for $3,500.00 a pop…and we couldn’t get them fast enough to keep up with demand. How far we’ve come at a fraction of the cost. Jaxsimmer

I for one am really enjoying this aircraft. Making a flight from KSLC to KLIT right now and having a ball. Yes, the Experimental version has quirks, but its fun to fly, and I appreciate the developers admitting they bit off more than they could chew, not folding the tents, and continuing to try to salvage their reputation. Happy Holidays everyone!!!! BAT

Problems for me as well. Gets to 3% loading then crashes. I uninstalled and went back to SU2 and all my settings are reset, including control assignments. Dummy me, I didn't back them up. I've cut Asobo a lot of slack, but this is getting to the breaking point.

Too funny!

My base i7-10400 clock speed is 3.8GHz. Turbo Boost (Intel tech) was increasing it to 4.3GHz automatically at certain points under load. CTD. My Asus MB with AI overclocking allows me to jack it up to 5.1MHz safely. Instant CTD and error with MSFS2024 SU3 beta 10.5.9.0 and 10.5.10.0 when launching program at that speed. Interestingly, SU2 and the earlier SU3 betas worked fine under both overclocked conditions. Now that I’ve locked the CPU to never go over 3.8GHz SU3 10.5.10.0 beta runs fine in a vanilla state. I suspect a lot out there have overclocked systems and that’s causing the CTDs. Of course, the apparent Simconnect issue seems to be an entirely different issue.

I have nothing in the exe.xml file and have not tried fsuipc yet. Totally clean vanilla install of MSFS2024.

Guys, I hope this helps someone. I couldn’t even start 1.5.9.0 and 1.5.10.0 was constant random CTDs. I removed everything from Community folder, exe.xml and still no luck. What fixed it was turning off hyper threading and Intel Turbo Boost in the BIOS and making sure there was no overclocking going on with the CPU and the GPU anywhere. I’ve flown two days in a row with nary a hiccup, and the performance with 1.5.10.0 is great. No stutters on landing. Like I said in another post, this SU3 beta is highly sensitive to memory and CPU timing issues. I hope they sort it out. Also, make sure you don’t have anything running in the background in the system tray, like Navigraph or FS2Crew. Check your startup apps which run when you log in.

Just a follow up. I’m on 1.5.10.0. It would CTD upon startup or after a minute or two of operation, just like 10.5.9.0. I went into Windows Apps and made sure all apps relating to flight simming were disabled on startup. I made sure there were no items in the Community folder. I went into my BIOS and turned off Intel Hyperthreading and Intel Boost. I turned on Rebar in the BIOS. Result - no more CTDs in over six hours of flying with the CJ4, the new Dakota, and the Piper Turbo Arrow IV from Just Flight. Best performance yet from FS2024.

Really appreciate all the feedback, but tried this too. I have the manual for the motherboard and have done exactly as you said with the pairing. Maybe time to get a new system. I've been holding off for a dream machine.

Thanks for the idea, but already did that.

They are fine, thanks for thinking of that though. My big point in all of this is I have never had an issue with MSFS2020 or MSFS2024 with any CTDs while running or startup issues of any significance up until SU3 1.5.9.0. I can count on the fingers of one hand issues I've had in terms of those areas since MSFS2020 was released. So it has to be something that has put this beta update on a knife's edge. Maybe its the added telemetry. Maybe its some tuning they did with CPU cores or the balance between CPU and GPU.