MSFS20 MSFS - Unable to build package using fspackagetool, after using patch 1.16.2.0 (SOLVED)

[FrancisJohannes]

Hi,

I've attempted to build using the fspackagetool but I get,

provided project definition file does not exist
press any key to continue

Can anyone build their packages under the new 1.16.2.0 patch?

On top of that the fspackagetool launches MSFS and then it claims it failed to open.

Does anyone know a workaround for this issue?

 

[BMW969]

I have the same error.

 

[flympguy]

Same problem here.

 

[BMW969]

New SDK 13 is available.

 

[flympguy]

installed still same errors

 

[flympguy]

 

[virtuali]

Rename your master project XML file with a name with no spaces.

 

[AnnaM]

Rename your master project XML file with a name with no spaces.

I have tested this with the default samples provided with the new SDK 13 and the ability compile via Drag & Drop using the fspackagetool.exe and dropping the XML onto it seems broken, the default sample project names do not have any spaces either and do not compile via Drag & Drop. This is infuriating, it's a massive waste of time to have to open up the simulator and wait for it to start to then be able to do a simple compile, how can such a thing happen?

 

[virtuali]

the default sample project names do not have any spaces

If you installed the MSFS SDK in its default folder C:\MSFS SDK, the full pathname DOES contain spaces ( "C:\MSFS SDK" ) so yes, the problem seems to be caused by space in the whole path, not just the actual XML project name.

I assure you it works if there are no spaces anywhere in the path that contains the master XML project file.

 

[FrancisJohannes]

Rename your master project XML file with a name with no spaces.

Thanks for the advice, yet, no fix here.

I have tested this with the default samples provided with the new SDK 13 and the ability compile via Drag & Drop using the fspackagetool.exe and dropping the XML onto it seems broken, the default sample project names do not have any spaces either and do not compile via Drag & Drop. This is infuriating, it's a massive waste of time to have to open up the simulator and wait for it to start to then be able to do a simple compile, how can such a thing happen?

View attachment 73646

exactly.
They'll fix it and at least we can build from within.

 

[AnnaM]

Further to Umberto's advice, here is the solution that works:

Backup your work and do a full uninstall of the SDK.
Reinstall the SDK and click on Options and modify the path from C:\MSFS SDK to C:\MSFSSDK
Let the installer finish.
Drag & Drop using the fspackagetool.exe will now work again.

The only strange thing is that you will now see this screen in the background while the project is compiling:

Thanks for your help Umberto!

Anna

 

[FrancisJohannes]

Further to Umberto's advice, here is the solution that works:

Backup your work and do a full uninstall of the SDK.
Reinstall the SDK and click on Options and modify the path from C:\MSFS SDK to C:\MSFSSDK
Let the installer finish.
Drag & Drop using the fspackagetool.exe will now work again.

The only strange thing is that you will now see this screen in the background while the project is compiling:

View attachment 73647

Thanks for your help Umberto!

Anna

I followed instructions hoping for a fix and it didn't work for me. I hope it works for others.

 

[Max Addante]

I've removed spaces from the whole path that contains the xml and now it works, while if I remove the space from the sdk path nothing changes.

 

[FrancisJohannes]

I've removed spaces from the whole path that contains the xml and now it works, while if I remove the space from the sdk path nothing changes.

well, there's no spaces on my xml. But perhaps I'll remove the dashes. The SDK is setup so we don't utilize spaces on our file names. At least to my personal knowledge.

 

[FrancisJohannes]

I've removed spaces from the whole path that contains the xml and now it works, while if I remove the space from the sdk path nothing changes.

NOW we're talking business. I removed spaces from the entire path. Thanks, mighty-Max. Now I can utilize the fspackagetool.

 

[AnnaM]

I followed instructions hoping for a fix and it didn't work for me. I hope it works for others.

Copy the fspackagetool.exe into the SimpleScenery folder inside the provided SDK sample folders, then Drag & Drop the SceneryProject.xml onto that fspackagetool.exe there. If that works then you know that your issue is elsewhere, perhaps with your dashes as you mentioned.

 

[FrancisJohannes]

Copy the fspackagetool.exe into the SimpleScenery folder inside the provided SDK sample folders, then Drag & Drop the SceneryProject.xml onto that fspackagetool.exe there. If that works then you know that your issue is elsewhere, perhaps with your dashes as you mentioned.

I did the path fix by removing spaces. That worked. But thanks to everyone who helped.

 

[Max Addante]

NOW we're talking business. I removed spaces from the entire path. Thanks, mighty-Max. Now I can utilize the fspackagetool.

Thanks to Umberto

 

[AnnaM]

I did the path fix by removing spaces. That worked. But thanks to everyone who helped.

Well that's exactly what Umberto had written - I assure you it works if there are no spaces anywhere in the path that contains the master XML project file.

If you still had spaces even after this advice, then it's no wonder it still didn't work.

 

[FrancisJohannes]

Well that's exactly what Umberto had written - I assure you it works if there are no spaces anywhere in the path that contains the master XML project file.

If you still had spaces even after this advice, then it's no wonder it still didn't work.

That’s true. I tricked myself, focused only on the xml file name and went pass through Virtuali advice. I apologize for that. The answer was already there by @virtuali

thank you.