• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

The continuing headaches of MSFS 2024 (for me, anyway)

Navy Chief

Navy Chief

Senior Member
Most of the time, I am able to start a flight without any problems. But every so often, after I select a aircraft, location, etc, and hit Start Flight.....all that happens is the dreaded "spinning disc". Period.
I have tried all the tricks, i.e. reduce LOD, move the view as far out as possible, OR move it as close as possible, tried different airports, different aircraft, turned off Photogrammetry. Nothing effects the problem. After 2 hours of frustration, I gave up for the day and went back to MSFS2020. Grrrrrrr....
 
That's usually due to a faulty addon airport scenery or a faulty addon aircraft - does this happen in a default aircraft at a default airport?
 
I had that happen today testing the new SWS PC-12 update. Turned out it was the PC-12 add-on liveries that hadn’t been updated. Removed those from the Addons Linker list and all loaded well.

So that backs up Tiger1962’s theory.
 
Started the 2nd update of the Microprose B17 and took off from 35L of KSDF, the end where the engine recently fell off causing the UPS plane disaster. The flight went well w/o a CTD.

Started another flight from EBBR Brussels in the B17 toward Palaise de Justice and CTDd after reaching there. Two more attempts with the same goals also ended in CTDs.

Flew another flight in the C172 with the same goal successfully. Then back to the B17. This time with the same goal the B17 worked successfully w/o a CTD.
Another quirk with my 2024 install?
 
Any chance you're overclocking your CPU at all? Seeing people reporting on the official forums that MSFS is so CPU intensive that it can crash otherwise-stable overclocked systems. Folks have reported setting "Intel defaults" in their BIOS and putting an end to CTDs.
 
DennyA said:
I had that happen today testing the new SWS PC-12 update. Turned out it was the PC-12 add-on liveries that hadn’t been updated. Removed those from the Addons Linker list and all loaded well.

So that backs up Tiger1962’s theory.
Click to expand...
When I was tracking this same issue down on my end, I found that the non-compatible livery doesn't have to be on the aircraft you're trying to fly, for it to cause the issue that NC is having. If it's anywhere that MSFS can see it, it will cause the never-ending spinning disk.


Forest
 
DennyA said:
Any chance you're overclocking your CPU at all? Seeing people reporting on the official forums that MSFS is so CPU intensive that it can crash otherwise-stable overclocked systems. Folks have reported setting "Intel defaults" in their BIOS and putting an end to CTDs.
Click to expand...
I do not overclock, but thanks for the info.
 
DennyA said:
Any chance you're overclocking your CPU at all? Seeing people reporting on the official forums that MSFS is so CPU intensive that it can crash otherwise-stable overclocked systems. Folks have reported setting "Intel defaults" in their BIOS and putting an end to CTDs.
Click to expand...
I have never messed with overclocking on my pc. Always been afraid to.
 
I don't want it to look like I'm piling on, but I am. :p

Over-clocking, to me, is like buying an expensive, brand new sports car and immediately taking it to the closest interstate to see if it will hit 200 MPH. This is rarely a good idea unless your folks own a repair shop for expensive sports cars and your brother happens to be a state trooper.
Otherwise, what you're about to do is going to get expensive. :indecisiveness:
Even back in the days when average CPUs ran around .75-1.5 GHz, overclocking didn't make sense to me. The ONE thing over-clocking does is add heat to the silicon inside the CPU. You could run a liquid nitrogen cooling rig and it will do nothing to the internal temps. Try setting an ice chest next to a gas grill. Does the ice make the flame cooler?

Of course, the chip makers and the boutique shops will tell you not to over-clock while they wink and grin. That's how they get to sell a lot more stuff. :wavey:
 
I have Afterburner but only use it to set the fan speeds - I have an HP omen and the common practice for most commercial PC mfg's is to set the fans to run slow across the thermal spectrum. Why would they do that? because the number one
customer complaint when starting up and running a new rig is about whether or not the new rig is 'louder' than it ought to be. So they set the fans low and set them to ignore temps.
Afterburner has a nice feature where you can set relative fan speeds to match and counter temp increases when you load and run taxing programs.
If you have a commercially built PC I highly recommend looking into how your fans are set.
 
You must log in or register to reply here.
Back
Top