Version: 1.4.9
Frequency: Consistently
Severity: Blocker
Bug description:
Part of SU2 is that the PackageOrderHint is made mandatory for our projects.
It sorts the loading order of packages.
My project is a modification of an existing modular aircraft by replacing the existing sim attachments of the modular aircraft. with my own custom build attachment.
It is therefore overriding the the attached_objects.cfg by removing existing simattachments and adding my own simattachments.
And hence dependent on the correct loading order.
This works without any issues in SU1.
In SU2 I assign the correct PackageOrderHint - according to the SKD - : SIMOBJECTS_PATCH
But because the existing modular aircraft (microsoft-aircraft or asobo-aircraft does not have a PackageOrderHint assigned to it, those packages are getting “INVALID” and therefore the loading order is wrong.
Example My Projects:
Asobo-Aircraft (should be SIMOBJECT)
Microsot-Aircraft (should be SIMOBJECT)
Repro steps:
- Start FS2024
- Open Package Reorder Tool
2 Likes
We are seeing the same issue as well.
1 Like
In SU2 Beta 1.4.10 the PackageOrderHint seems to be fixed, however the SimObject Editor does not load the .cfg files from PackageSources folders.
With SU2 Beta 1.4.10 - for the end user - the issue is fixed with the correction of the loading order part of SU2 Beta 1.4.10.
Althoug the existing modular aircraft still do not have a PackageOrderHint assigned to it, with this this correction, the packages with SIMOBJECTS_PATCH are now loaded after the INVALID packages, so solving the issue at loading time.
However for us devs the issue is not fixed.
In the simobject editor - for SIMOBJECTS_PATCH packages - the cfg’s are not loaded correctly in the simobject editor.
After some trial and error, i found that:
For (simobject_patch) packages without cfg’s in the common folder the cfg’s are not loaded in the simobject editor (common folder is taken from the patch aircraft)
For (simobject_patch) packages with cfg’s in the common folder the cfg’s are loaded in the simobject editor.
So it seems to me that the issue in the simobject editor is related to the common folder.
1 Like
Hello @marcfsx8078
The runtime behavior regression was indeed caused by incorrect order hint management.
This is not the case for the SimObject Editor. It does not support the override of cfg outside its known structure at the moment, regardless of what order hint is used.
This is a problem for livery edition and patching/modding existing aircraft.
This is being worked on as we speak.
Regards,
Sylvain
2 Likes
Thanks @FlyingRaccoon for this update letting us know that it is worked upon.
Can you pLease let us know when a fix is available?
Thanks for the support,
Marc.
This should be fixed in the current version of SU2 beta.
Regards,
Sylvain
1 Like
Hi @FlyingRaccoon
Thanks for your and the team efforts to solve this issue.
Unfortunately this issue is not fixed with the latest SU2 Beta update to version 1.4.14.
With this update there are no changes compared to previous versions.
To be complete, and with the aim to help solving this issue:
. According to this post - [ RESOLVED] Hold on Updating your Beta Build - Beta News - Microsoft Flight Simulator Forums - there were issues with publishing this update, however in my experience there were two deployments
. After the first deployment, it seemed that that the CFGs were loading in the simobject editor.
But the package order hints for non-scenery object were disappeared, making them none in the project inspector. Also in the package reorder tool, the title bar was renamed to “scenery package order”, and one could not select anymore the order for non-scenery packages. This blocked my development.
. Then, after the second deployment, the package order hints were back, the same for the package reorder tool. But now the the CFGs are not loading in the simobject editor, as it was before 1.4.14.
So maybe this helps in solving this issue ?
I am using the latest SDK version 1.3.3.
Please keep us posted,
Thanks, Marc.
I am sorry, I meant that the order hint regression was fixed.
The SimObject Editor being unable to find some cfgs is still work in progress and will be likely fixed with SU3.
Regarding the issue you mention first, my understanding is that a SU1 build was deployed in place of a SU2 beta for a short moment.
This could explain your problems and the tools changing name.
Regards,
Sylvain
Thanks @FlyingRaccoon for your update and clarification.
I’ll keep an eye on SU3 then,
Thanks, Marc.
