SDK Version: 0.9.2
Frequency: Consistently
Severity: Low
Bug description:
When loading a project containing MSFS2020 simobjects, in devmode, it always asks if the assets should be converted. I assume this is related to the XML files corresponding to the simobject’s textures because that’s the only thing I could find after running this.
However this window still pops up every time, even after the assets have already been updated.
No matter if they are updated, there are also some weird errors popping up when building the presumably updated models/textures:
Hello @Sasa ,
This could be two different issues.
What do you see in the console when building your project ingame using the project editor ? Same errors as using fspackagetool.exe ?
For your both post, do you encouter the sane behavior in all your project ?
Regards,
Boris
Looks the same when building on console:
That xzB@Qd… error doesn’t happen on all models though.
Would be interesting to know what actually is supposed to happen when clicking “Update All”.
Hello @Sasa,
Any chance you can send us your project please ? Or at least a light version that reproduce the issue.
See 3) Provide Private Content
Regarding the “Upgrade All” process when opening an MSFS2020 project in MSFS2024:
It adds XMLs for textures (in modellib and simobjects) and update the PackageDefinition xml file by removing the MarketplaceData tag.
Additionally, it introduces a version type number (1 for ModelLib and SimObject, 0 for other AssetGroup types).
Regards,
Boris
Hi Boris,
I was about to send you a light version to reproduce the issue and while collecting the files it seems like the found the culprit of the “is outdated” error thrown:
The error thrown applies to all simobjects that do not have their own textures but instead have a CFG file in their texture folder that points to a shared texture directory. Like this one:
texture.CFG
[fltsim]
fallback.1=…..\sharedFolder\texture
In this instance no XML files have been created for this particular simobject and the builder/console window seems to assume that no “upgrading” happened and the simobject in question is still outdated.
Could this make sense?
Hello Sasa,
I did not reproduce the same behavior.
Can you share me at least one simobject and the “sharedFolder” ?
See 3) Provide Private Content
Thank you,
Regards,
Boris
Sorry for the trouble. It worked on a smaller environment so the error must be somewhere else. I report back if it’s something that’s not caused by my package.
