question

Exact same problem here!

Follow up on the above - the problem seems to be that the compiler now looks for data at C:/MSFS when used outside of the simulator, therefor does not see projects at C:/ MSFS SDK. Moving the entire project folder from C:/ MSFS SDK/xprojectfolderx to C:/ MSFS/xprojectfolderx seems to have solved the issue.

While that now solves the compiler issue, something is still not right. There is this new window now:

@Asobo - It would be great if you could alert us before breaking key functionality like this!

I had that issue for a while (then it went away for some reason).

Now I'm having an issue where the packager executes the simulator but then they both hang doing nothing forever.

Hello @DC1973 @PILOTS_Development @runshotgun ,
Indeed It seems that fspackagetool.exe does not like folders with a spaces in their name and an issue about this is already opened on our side.

About the fact that MSFS2020 is trying to start whenever you are building a package with fspackagetool : Are you using Windows 10 or Windows 11 ?


Can you tell us the command line that is used to build your projet ? You can use this steps :
1. Download and run Process Explorer

2. Build your project and in the same time, in the main view of Process Explorer, search for FlightSimulator.exe

3. Right click on the process FlightSimulator.exe and in the new windows search for "Command Line" in the tab "Image".

4. Copy and paste here the content of the command line

Also : Did you try to reboot and Sign Off/Sign In again to the Microsoft Store / Xbox App ?

Thanks,

Regards,
Boris

Edit :
If you are using windows 10, Can you specify us you windows version please (21H1 21H2 ... ) ?
https://support.microsoft.com/en-us/windows/which-version-of-windows-operating-system-am-i-running-628bec99-476a-2c13-5296-9dd081cdd808

Hello,

I have the same problem, which I solved like "PILOTS_Development", but as I also had red error messages in the console, whereas I didn't have any before 1.25.9 (it concerned the .bin of the LOD's), I deleted the _PackageInt and PackagesMetadata directories and the console doesn't show the red error messages anymore.

I have logged out and logged back in to the store, still the same.

I am using Windows 10 21H2 and here is the command line,

"C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.25.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe" -I ; BuildAssetPackages C:\MSFS_SDK\Samples\SimpleScenery-chateau-de-chenonceau-Gltf\france-dpt-37-ftslw-chateau-de-chenonceau.xml C:\MSFS_SDK\Samples\SimpleScenery-chateau-de-chenonceau-Gltf C:\MSFS_SDK\Samples\SimpleScenery-chateau-de-chenonceau-Gltf CheckOutputTimestamps UsePause LauncherPID 9148

Regards,

ftsxfreelw

It's a nightmare:

i'm using the fspackagetool.exe on my project using this command line:

"%MSFS_SDK%Tools/bin/fspackagetool.exe" %xml_def% -rebuild

it compiles without errors and the error log in _PackageInt\_metadata appears to be void.
If i compile using the sim in dev mode with package editor it ends with no errors either, and it produces EXACTLY the same package done by fspackagetool.exe in command line.
I succeed to upload the package in MarketPlace Content Portal, the package passes the validation phase but i can't SUBMIT since it does not find the "package name".
In another case i can upload and SUBMIT the package but during the "ingestion" phase it is refused asking for a re-submit since there are (unknown) issues.
After a month of direct chat with MS Teams nobody was able to tell me what is wrong on my packages, other than "it's made with wrong tool, do not use fspackagetool.exe, use sim in dev mode instead"

So i'm stuck since nobody at Teams was able to say what is wrong on my packages.
Never had such problems before SU 8.
Is there any good soul who can give me some explanation ?
Mario Motta
SIM SKUNK WORKS

Thank you all for your feedback,
We are now investigating this issue

Regards,
Boris

Same problem here since this morning (it was working fine yesterday even after the patch was installed). I am getting same error message in RED saying "Provided project definition file does not exist". I have not changed anything in my project since yesterday.

I am on Win 11 / 21H2 Build 22000.675 and I had a mandatory update this morning (I believe it was a BIOS update).

EDIT: The problem is certainly the spaces in the xml file name. I removed the spaces (and the hyphen) in "LTBA - Ataturk SHARED" (main project folder name) and "Ataturk Project.xml" (my main xml file) and the fspackagetool.exe worked as intended.

Yup, build tools are completly borked since SU9 and HotFix.

1. FSPackageTool now tries to load the game
2. Spaces in the project path are no longer supported
3. In game build log is now devoid of ANYTHING and only reports the same as external build. Previously it would report issues with ModelBehaviours (as well as sundry other issues with every other default aircraft)

Further information - the in-game build does not report accurately what is going on. I have here a screenshot showing how the build fails due to an error, while the builder simultaneously reports 0 errors. This is from a 4-aircraft model pack, three aircraft build normally, one does not. There is zero information on why the failing aircraft does not build. Work has been at a stand-still for four days now, as I cannot identify the cause of the failure.

I should note that the compiler did spot a duplicate entry in one of the .cfg files, so it is capable of spotting some errors at least. I shut down the sim and re-started to recompile in case that was the cause, but no, build not possible and no reason why.