Version: 1.3.22.0
Frequency: Consistently
Severity: Blocker
Marketplace package name:
Context: What package? When editing or mounted from Community? In main menu or in flight? etc…
Similar MSFS 2020 issue: insert url here if applicable
Bug description: The packagebuilder crashes if my project version number is higher than 1.23.xx. This includes tested numbers such as 1.24.27, 1.45.27 and 2.0.1.
It crashes both when building in sim and when using fspackagetool.
I don’t know if this is unique to my project, or for all projects.
This is happening currently on beta SU1, but I suspect I had the same issue last week on live version.
Repro steps:
Set version number of project to 1.23.27 and build. It works.
Set version number of project to 1.24.27 and build. It crashes on “Generating package information”
Set version number of project to 2.0.1 and build. It crashes on “Generating package information”
Attachments:
Success:
Fail:
Fail:
Private attachments: Send a PM to @PrivateContent with the link to this topic and the link to download your content
I managed to build a BGL package last week with <AssetPackage Version="25.02.1"> https://flightsim.to/file/72056/queenstown-nzqn-zqn-rnp-ar-procedures. Maybe there’s another factor involved too.
Hello @WombiiActual
We would need the project sources that triggers this CTD or a dump file to investigate, whatever is easier for you to provide.
How to report a bug or crash - [MSFS 2024] Bug Reports - MSFS DevSupport
Regards,
Sylvain
@FlyingRaccoon
Sent full project folder and crash report to privatecontent.
I can confirm that other projects work with higher version numbers, but this fails 100% of the time for me. I have tested repeatedly with higher and lower numbers to eliminate random chance.
In a newer version than the one I sent, it also crashes on 1.0.28 and 1.1.0, so now I literally can not increase the version number at all for marketplace upload.
I can not use any version number higher than 1.0.27 at all.
1 Like
I was having issues with my library crashing on package build in the SU1 beta as well. My version number that was crashing was 25.1.9. However, I ended up deleting the release notes entry, changed the version number to 25.2.19, and then added a new change log entry. Since then I have not had any issues building the package.
Hello @WombiiActual
I think the problem occurs when the version set in the Summary Content Manager tab or package xml does not have a corresponding entry in the Release Notes tab or xml.
If you set it to 1.24.27 but create a corresponding entry in the Release Notes list, it no longer crashes.
Do you confirm this?
Regards,
Sylvain
1 Like
@FlyingRaccoon
I can confirm that it works if I set the release note version to the same as the build version. Thank you.
1 Like
Hello
This is fixed with SU2 beta 1.4.7.0.
Regards,
Sylvain
