When attempting to compile a package outside of the sim by dragging the main .xml file onto fspackagetool.exe, instead of compiling in a Command Prompt window, it launches the sim.
This is new behaviour and is preventing me from building anything for 2020 or 2024. This only just started happening so I assume its linked to a recent update.
Can anyone confirm if this is happening to them too?
same here, I noticed an issue yesterday using google earth optimization tool made by Thalixte. At the end of the optimization process it launches the SIM, there is no building packages it no longer shows the console, I haven’t found a way to prevent the game from launching !!!
Hello @Gobby @demoken9484
We are not able to replicate the issue so far.
You have the issue with both MSFS 2020 and 2024, using their respective SDK?
Are you using Steam or Microsoft Store versions?
Are you both using an up to date version of Windows 11?
Regards,
Sylvain
Microsoft Store version for both 2020 and 2024.
Windows 11 fully updated.
Latest 2020 fspackagetool.exe (Modified: 12/09/2024)
Latest 2024 fspackagetool.exe (Modified: 10/03/2025)
Hi FlyingRaccoon,
i have the issue with both FS20 & FS24 i use Microsoft Store version .
and Windows 11 is updated
last update SDK, MSFS_SDK_Core_Installer_0.24.5
Thanks for the reply
Demoken
Try running it on the command line…
C:\MSFS 2024 SDK\Tools\bin\fspackagetool.exe (path to the XML file)
everything works ok here
i normally build outside the game and use a simple batch to launch the the game and compiler
the game window always opens but then so does the com window after a few seconds - i tested both 20 and 24
i do use the -nopause comment but that only saves from ‘hitting any key’ to exit the console window after the build
a sample of my build files (these are in the project folder next to the xml)
Build.cmd for 2020
“C:\MSFS SDK\Tools\bin\fspackagetool” -nopause “XCub Extreme.xml”
Build.cmd for 2024
“C:\MSFS 2024 SDK\Tools\bin\fspackagetool.exe” -nopause “XCub_ClassicFX.xml”
Pro tip (slightly related) - this works in 2020 no matter where you install the SDK, I assume there’s another environment variable for 2024:
"%MSFS_SDK%\Tools\bin\fspackagetool.exe" package.xml
I’ve been doing the same thing, but for the past two days, and for no apparent reason, it’s been launching the sim instead of opening the console
And is there any specific printed in the console when you do so?
Completely blank Command Prompt window for around 10 seconds, then the sim launches and the window closes.
Also, attempting via the .cmd prompts provided above gives the same issue.
Have you created a .cmd file that you double click to execute?
If so, please try to open a prompt and type the command in it instead. Prompt should remain open after your command ends in such case.
Regards,
Sylvain
Yes, that method the window stays open, but no additional text is posted to the prompt, and the sim launches.
Okay, this looks like an launch argument corruption issue, which is something we already saw in the past.
Last thing, can you try typing the command displayed in your picture directly in the command prompt, bypassing fspackagetool.exe.
You just need to replace the corrupt part in the middle by
…FlightSimulator2024.exe" -I “;” BuildAssetPackages…
and check if it is still corrupt the same way in the Task Manager.
Thank you
Yes, it gets garbled too when bypassing fstackagetool.exe.
Ok, so that’s coming from the launcher, which also explains why you suddenly had the issue on both MSFS 2020 and 2024 without any exe or SDK update.
We will forward the information.
Thank you for testing this.
Regards,
Sylvain
