Hi Stoopy - the wine helped - but not with MSFS.

 

I ran the program and then FS, which showed loads of processes starting up - but it never kicked in.  I ran it a again and again - nothing.  I rebooted the computer and ran FS again - this time it started up and told me I had to install the base program yet again (another 112GB - no way!).

 

Something is seriously wrong.  Any thoughts?

I have just discovered that if you verify your files in the Steam app - it deletes your entire installation.  Brilliant!  So for the third time this week, I am again downloading the whole lot - and will no doubt discover that it doesn't work once finished.

4 hours ago, crazydog said:

Hi Stoopy - the wine helped - but not with MSFS.

I ran the program and then FS, which showed loads of processes starting up - but it never kicked in.  I ran it a again and again - nothing.  I rebooted the computer and ran FS again - this time it started up and told me I had to install the base program yet again (another 112GB - no way!).

Something is seriously wrong.  Any thoughts?

Ouch! At this point with MSFS not even starting and you getting the message about a reinstall needed, it sounds like any thoughts I have wouldn't make much difference.  I'm very sorry top hear this occurred.  I'm also running the Steam version and have learned the hard way on other programs to avoid that stupid file verification process. 

I have used ProcMon from a cold startup and just did it again this morning and no issues - again, it's just monitoring and in years and years of using it at work and for personal dev stuff at home I've never had an issue with it.  If I had to speculate, not that there's much value in it now but you are asking, I have to think that your problem was a bit worse and with a different root cause than the known issue of intermittent flights not loading (like 1 or 2 out of 3 times) on a stock install with stock airports.  Maybe a full delete and reinstall was inevitable?   

I'm not a wine drinker but of I was there I'd offer you a good full glass of my best Rye to see you through the install...

 

Thanks again Stoopy - on 69% of reinstall (to a clean folder).  I will persevere - and use Procman to diagnose any potential hiccups.  I have to say that I was very impressed with the few flights I managed early on - so am looking forward to a few more in time to come, particularly around Lake Baikal.

A single Malt might well be needed as the final few percent approaches:-)

 

On 10/15/2021 at 4:10 PM, abrams_tank said:

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.

This is what is working for me. I only had this problem in populated US areas, the Procmon64 thing did not work for me. So Iam hoping the next update will fix it...

Hello Micko - thanks for your input.

 

Just an update.  I have again run MSFS with procmon running.  Again it freezes (no matter where in the world I take off from) when the flight launches.  Procmon shows many processes continuing even though it has frozen.  Several times I am seeing "Name not found" in the results section - otherwise all looks okay.  I am not sure what Procman is supposed to do or how I am supposed to interpret the data.

 

I await the next update with bated breath.

2 hours ago, crazydog said:

Just an update.  I have again run MSFS with procmon running.  Again it freezes (no matter where in the world I take off from) when the flight launches.  Procmon shows many processes continuing even though it has frozen.  Several times I am seeing "Name not found" in the results section - otherwise all looks okay.  I am not sure what Procman is supposed to do or how I am supposed to interpret the data.

I'm sorry this is still not working for you.  The problem you are experiencing definitely sounds far worse than the intermittent issue that's been reported.

If ProcMon is not serving as a workaround for anyone else then I also apologize for the false lead.  It works so well to eliminate the problem on my system that I felt so confident on encouraging anyone else to try it.  The value isn't so much in the data it collects but in the idea that it invokes some very slight additional overhead in what's going on and seemed to eliminate an apparent race condition that was causing a conflict and subsequent hang - two things trying to get done at the same time in the loading process, and ProcMon slows stuff down just enough that they don't crash into each other.  I'll keep using it (have to, if I want to fly) but will cease brining it up. 

What to do with the data?  Share it with the right people who have ability and insight to look into it, There is value to it if it captures details on what fileis locked, not found, or unable to be created, etc.  You can save it (File menu, save, and for good measure save both the native PML format as well as CSV which is readable by anyone).  Ideally, to ensure you capture all the data that may be important, you can turn on all the events by selecting the activities to collect in the top right toolbar for Registry, File System, Network, Process and Thread, and Profile Event activity.  Then, since that will generate copious amounts of data, try to limit it to the relevant window of time where the problem occurred,  Don't start collecting data until right before you press the button to launch the flight in the menu, then turn the capture off once you are positive the load process has hang up.  Take a note of the time as well.

Now, who would you want to share the data with?  Well, sure, I can take a look but to be honest any root cause won't be immediately apparent to me since it's actually quite normal to see file locks and other messages that can look as if they are problems when they really are not, and none of us here have access to source code to be sure.  Yes we can guess.  And since the full pathname of files is recorded, your Windows account name may be evident in the data, so as a general rule I wouldn't share this with strangers on the net. Not that anyone can hack your system by having just that data, it just creeps me out to give even that away.  But I'm kind of paranoid and don't even do Facebook or social media.  

The REAL people who can use this data, and have an obligation to, are the good folks at Microsoft/Asobo.  Not to pass the buck here, but really.  If you were to open a ticket (and by all rights you should, even before we got up to this point) and attach this data, now it's going into exactly the right hands, and what you'd be providing them is miles ahead of what they normally get.  TBH the Tier 3 support folks who are usually working in very close conjunction with, or may even be, devs themselves, LOVE to get detailed data like this when looking into a problem.  It can be a godsend because otherwise they are shrugging their shoulders and wondering what is wrong with the system on your end - they have no insight but that's what this tool provides if looked at by the right eyes.  Who knows, they may discover a problem on their end that they can fix now so you won't be waiting for the next update after SU6.

There is also a sweetly diabolical aspect of this, if you enjoy that, in that you will at least cause some consternation on their end in return for the pain you are going through.   😉

Edited October 17, 20214 yr by Stoopy

Thanks Stoopy.

 

I updated MSFS last night - and... yes, still MSFS freezes soon after I attempt to launch a flight (even in safe mode).

 

So I have wasted £50+

I’m having the same problem for days. Community folder is empty, every addon from market place is uninstalled and the sim stop responding when loading a flight.

Turning off online functionality solves the problem, but i won’t fly in a sim where I spent $60 and not even have sattelite data.

There are some people with this issue for months and even with the enourmous SU6, Asobo won’t fix this.

i found since updating to win11 if i launch msfs then launch a program like chrome and overlay onto of msfs then minimize chrome it will make msfs freeze then i have to force shutdown 

I only get the hang when loading my Meigs addon.  I run taskman to close MSFS.

bs