OK. I got hit by the “slow startup” problem after a rather low-problem period so far unlike some other users here.
TL;DR: So, for all non-IT or non-technical users out there: if you are hit by a slow startup of MSFS, try to limit the number of packages until Asobo fixes their user interface and starts using threads for what they are designed for. Maybe it helps to solve your problem
Long version:
So I pull out trusty procmon.exe and start watching the startup of the application. Here is what I observed:
-
After adding just about every Community package I could get my hands on since the launch I seem to have hit a classic developer problem: you create a ‘purdy’ startup screen to keep the attention of the user while loading but you forget what it’s there for: to explain to the user what the application is doing until the user can start using it. If you insist on going through all packages during startup (for reasons unknown) at least show a progress bar and tell the user which package you’re working on. Your static company logo and corporate lawyer blabla is not helpful when I want to start flying.
-
Why is the application trying to load the “Press Start” video over and over again between package loading without actually showing it?
-
Why does the application go through all the Community packages again after you are finally able to start?
Asobo, this is pretty basic stuff that is easy to fix…
