I have been using MSFS 2020 since I bought it on steam 3 months ago - and took a break flying for a month.  When I returned yesterday to launch a flight I got the launching screen and progress bar reaches about 70% then...nothing.  I have to Ctrl-alt-del to quit flight simulator.  I have repeated this at least 15 times - and last night reinstalled 100+GB of core game only to find this morning that the same problem persists.  Previously had no problems and getting smooth performance all round at mid to upper quality.

 

Chip - I7 8700

memory 16320 mb DDR4 sdram

graphics GeForce GTX 1060 3GB

 

Any suggestions welcome - the trouble is that this is so time consuming to trouble fault, and I'm close to giving up.  Life is too short.

try renaming your  community  folder   than see  if it  loads, if  it  does  than  you  have  a addon   thats  causing  the  issue  and  reinstalling  it  again  most likely  wont  fix  the issue

Thanks Pete - I carried out a few pre-tests before reinstalling again (presently on 16%) and emptied the community folder, as well as downgraded my graphics settings to low - but still the same problem.  Steam verified my previous instillation - so this is really baffling.

Try this link @crazydog.  It pretty much answers your question 🙂 

Cheers

 

Terry

 

 

Another possibility?

I found the sim freezes on loading airports (Marketplace only) that have not been updated to SU5+.

you don’t say which airports this happens with… 

I understand this is a bug and should be sorted in SU6. 

I think there’s a thread about this on the Flight Simulator Forums 

Thanks for the help and links so far.

 

Rayharris - I am only using airports that come with MSFS2020 - and have no add-ons at all.

Looks like I will have to wait for the SU6 update. I don't understand why some people are affected only.

Known bug per posts in other thread that is linked above.

Its not incompatible add on scenery - can easily happen with stock airports etc.

Its not community folder content. - can be replicated with an empty community folder.

Its not conflicting BGL files in add on scenery - used the tools in Add on Linker to find and rename duplicate BGL file entries and problem persists.

Its not rolling or manual cache files - resetting or deleting will cure for a few flights then problem returns.

Does not seem to be related to disk performance, fragmentation or access speed problems - occurs on my healthy system with MSFS installed on a 1TB SSD drive that is less than 50% full.

Waiting for the hang to recover has never worked for me - have waited up to 30 minutes but task manager still showed FlightSimulator.exe as "Not Responding" while GPU fan was blowing full tilt (since MSFS does not seem to cap frame rates until flight has started).  Healthier option for your system is likely to cancel the task via task manager as opposed to waiting for extensive periods to no avail while GPU heat rises.

This known problem *may* be resolved in upcoming SU6 update although it is not explicitly listed in the SU6 Beta change log. Fingers crossed.

The only thing that has worked for me to consistently avoid these hangs is to run Microsoft's Process Monitor tool right before loading a flight.  Ironically, the very tool that might actually pinpoint what is hanging at the file system or registry entry level, seems to serve as a consistent workaround by prohibiting whatever race condition or other error or timeout is occuring.  Has cured the problem for me consistently for two weeks running now.  Details provided in other thread.

The only thing about this annoying problem is that it is a) consistently inconsistent and b) apparently afraid to show its face when confronted with proper system monitoring tools (which is at least a saving grace and workaround)

Thanks Stoopy - glad to know I'm not alone.

 

I have completely reinstalled FSim - and the problem persists.  For me, it hangs EVERY single time I launch a flight, so the sim is effectively useless to me unless I can find a work around.

 

I have noticed in Content Manager that there is one MS FS file in the list named 'temp' which is indicated as "not installed".  Clicking on the Information tab shows that it is 'waiting'.  I have no idea if this is the culprit - it showed up on the previous installation as well.

For me, it also depends on the departure airport..

Try something far from a city.

5 hours ago, rayharris108 said:

Another possibility?

I found the sim freezes on loading airports (Marketplace only) that have not been updated to SU5+.

you don’t say which airports this happens with… 

I understand this is a bug and should be sorted in SU6. 

I think there’s a thread about this on the Flight Simulator Forums 

Some MSFS marketplace sceneries are known to cause the loading screen to freeze.  This is something that happened after SU5, as most of these sceneries would load fine before SU5.  The same sceneries do not seem to have this problem if you purchased it at a 3rd party website, which would mean you would place the scenery in your Community folder.

You can search for this problem.  It's a known problem with many scenery developers that have sceneries in the MSFS marketplace (if my memory is correct, it may be related to the encryption of MSFS marketplace products, and that encryption is causing problems for sceneries purchased in the MSFS marketplace). From my understanding, there may be a fix in SU6 but then again, this problem has not been fixed in the last few patches since SU5 so who knows if SU6 will fix it.

For a temporary solution to this problem (until it is fixed by Asobo), see my next post below, which has worked for me.

Edited October 15, 20214 yr by abrams_tank

20 minutes ago, Stoopy said:

Known bug per posts in other thread that is linked above.

Its not incompatible add on scenery - can easily happen with stock airports etc.

Its not community folder content. - can be replicated with an empty community folder.

Its not conflicting BGL files in add on scenery - used the tools in Add on Linker to find and rename duplicate BGL file entries and problem persists.

Its not rolling or manual cache files - resetting or deleting will cure for a few flights then problem returns.

Does not seem to be related to disk performance, fragmentation or access speed problems - occurs on my healthy system with MSFS installed on a 1TB SSD drive that is less than 50% full.

Waiting for the hang to recover has never worked for me - have waited up to 30 minutes but task manager still showed FlightSimulator.exe as "Not Responding" while GPU fan was blowing full tilt (since MSFS does not seem to cap frame rates until flight has started).  Healthier option for your system is likely to cancel the task via task manager as opposed to waiting for extensive periods to no avail while GPU heat rises.

This known problem *may* be resolved in upcoming SU6 update although it is not explicitly listed in the SU6 Beta change log. Fingers crossed.

The only thing that has worked for me to consistently avoid these hangs is to run Microsoft's Process Monitor tool right before loading a flight.  Ironically, the very tool that might actually pinpoint what is hanging at the file system or registry entry level, seems to serve as a consistent workaround by prohibiting whatever race condition or other error or timeout is occuring.  Has cured the problem for me consistently for two weeks running now.  Details provided in other thread.

The only thing about this annoying problem is that it is a) consistently inconsistent and b) apparently afraid to show its face when confronted with proper system monitoring tools (which is at least a saving grace and workaround)

I have this problem with the Sam Scene 3D Hong Kong scenery where it would freeze on the loading screen.  There are two solutions for me:

1. Spawn outside the scenery's area and then slew to the scenery where the freezes happen.  For example, I will spawn in Macau which is just outside the area covered by Sam Scene 3D Hong Kong.  There is no freezing on the load screen. I can then slew to wherever I want in Hong Kong and start the flight there.

2. Spawn at some random airport where the scenery that causes the freezing isn't being loaded as your first flight.  For example, I will spawn in some random New York airport, and then exit the flight. When I load up at a Hong Kong airport within  Sam Scene 3D Hong Kong's area, because this is my second flight, the freezing does not happen anymore at the loading screen.  The key is to successfully load a first flight, and then exit that first flight, and then you may be able to load the second flight at the scenery that is causing the freezing on the load screen.

Edited October 15, 20214 yr by abrams_tank

1 hour ago, Bert Pieke said:

For me, it also depends on the departure airport..

Try something far from a city.

I have tried.  It makes no difference what airport I use - and these are all airports that came with MSFS, not add-on scenery.  Having completed the reinstall and updated everything just now - same problem - this time, the programme just stopped working and could only be exited via ctrl -alt- del.

 

hopeless.

53 minutes ago, crazydog said:

I have tried.  It makes no difference what airport I use - and these are all airports that came with MSFS, not add-on scenery.  Having completed the reinstall and updated everything just now - same problem - this time, the programme just stopped working and could only be exited via ctrl -alt- del.

 

hopeless.

Try the Process Monitor workaround. Seriously, much simpler than doing a reinstall and it has eliminated this problem when it's monitoring FlightSimulator.exe.

https://docs.microsoft.com/en-us/sysinternals/downloads/procmon#download

It's a small free download from Microsoft and the program doesn't go through an install process. Just download the zip, extract the contents to a folder wherever you like (could be a folder on your desktop)

Launch ProcMon64.exe and click the green filter triangle on the top toolbar.  

In the filter dialogue box set up a filter for MSFS by selecting "Process Name" from the drop-down list, then the option for "is" in the next field, and enter FlightSimulator.exe in the third field. Then select Apply and OK. Your work is done.

Launch MSFS and set up your flight, but before you click "Fly" make sure you have launched ProcMon64 and it is running the filter you set up (it should automatically show up when you launch ProcMon64 so you just have to hit OK).

With ProcMon64 doing its thing and showing you a bunch of gobbledegook, click Fly and watch your flight load. When it completes you can go exit ProcMon64.

Easier than it sounds and cannot mess anything up on your system. Its just watching and looking at events. Not writing or changing anything.

If by some crazy reason this doesn't work (which has not been my experience yet)  that's actually great news too because any clues about what the problem *really* might be should be in the logged data that ProcMon64 generates! 

 

Edited October 15, 20214 yr by Stoopy

Thanks Stoopy - will try tomorrow.  I am opening a bottle of red to drown my sorrows for now.

2 hours ago, crazydog said:

Thanks Stoopy - will try tomorrow.  I am opening a bottle of red to drown my sorrows for now.

You're very welcome and as you'll see the first-time setup should take about the same amount of time as uncorking that bottle and pouring a glass.  I made it sound more complicated than it really is.

But I get that it's finally Friday and time to knock back a drink or two. 😁