As a developer it is truly maddening waiting for this sim to load. It starts
out with two minutes of “checking for updates”. Two seconds would be long
enough. Improving the loading times should be a top priority; it will increase
productivity by orders of magnitude throughout Asobo and all others working
with the sim.
I agree. Also the external compiler doesn’t work as good as the “in game one”.
It’s my understanding that the external compiler is running the same code as
the in game one, it’s just a matter of configuring it with the correct
parameters.
Agreed. Having to select a flight each time is particularly annoying. A
command line parameter to automatically bypass menus and load a flight file
would be real nice.
I second that, it would be very useful if a “skip updates check” flag could be
added, which might be supported by the fspackagetool.exe too. And yes, an
option to load a saved flight and start directly with that, bypassing the
menu, would be very good as well.
There’s no such thing as an “external compiler”. The compiler is only one, and
it’s the simulator itself ( Flightsimulator.exe ). If you are referring to the
fspackagetool.exe, that’s not a compiler, it’s just a launcher for
Flightsimulator.exe which set some arguments to use it as a compiler instead
of starting up fully.
@echo echo %time% “C:\MSFS SDK\Tools\bin\fspackagetool.exe”
“%~dp0\airport.xml” Is use this .bat for compiling my files without opening
the sim, but I get errors over and over. If I open MFS and I compile it with
the in game UI it works with no problems. Why does this happen?
Just drag’n’drop the project XML onto a shortcut of the fspackagetool.
Because there’s a space in the SDK path ( “MSFS SDK” ). I found this bug
months ago and posted the suggestion to fix on fsdeveloper:
<https://www.fsdeveloper.com/forum/threads/msfs-unable-to-build-package-using-
fspackagetool-after-using-patch-1-16-2-0-solved.452642/post-883076>