Sim Object patch projects ordering not working

[MSFS 2024] Bug Reports Aircraft
, ,
1

Version: SU3

Frequency: Consistently

Severity: High

Context: Any project of the type, when loaded.

Bug description:
We have created dummy build packages to allow 3D artists and avionic artist to work without the need of a full project.

We doing this using the “project” patch type of projects as per DA62 mod example, however this is not working as intended, the order of the package never works and artists have to constantly load the VFS system to re-order the package manually always

image
image573×601 26.1 KB

Looks like the projects ordering tool are not being respected at all. For reference this is what we doing: How to setup a Custom extra Livery pack project or a project for livery artist

It works well once we put the order in place “manually” which needs to be done every time we load MSFS, but it should take precedence automatically.

In addition, we would like to use this technique to allow “Sound” artists to work without the need of we having to provide the full projects source in full, upon trying this approach for our Sound contractors, we discovered the project never overrides .XML and sound files properly.

This is critical for 3rd party developers as we hire contractors to do different jobs during a project lifecycle, from 3D works, avionics to sounds.. and having to provide a full project source with everything we do is not practical and sometimes not possible due to contractual restrictions.

We need to be able to provide such contractors “partial”, “dummy” projects, while the main compiled version of the products is sitting on community folder, so they can work on the sections they need, safely, and without us exposing our entire source code and IP property to everyone.

This was possible in MSFS 2020 since they had the “Reload” button, but in MSFS 2024, is not possible anymore, this forces contractors to re-start MSFS 2024 to see any change they do unless they have a full project source.

So it would be ideal if we all could discuss better approaches and have working tools to allow our daily workflows to operate without having to deal with constant issues that make our staff feeling frustrated, irritated and very unproductive.

All The Best,
Raul

1 Like
2

When you say ‘“project” patch type’, do you mean package order hint set to ‘SIMOBJECT_PATCH’?

image

And the package that you are giving contractor as your base package hasn’t got its package hint as any of the higher priority ones?

3

Correct.. in community the normal aircraft, as “custom simobject”.. and the dummy projects exactly like your picture. “SIMOBJECT_PATCH”.

We have to set the order manually always.. and it doesn’t work for sounds like I explained.

R.

4

image
Since your base package is “custom_simobject”, you need to set your Livery patch projects to “custom sim object patch”. “SIMOBJECT_PATCH” is lower priority than “custom simobject”

Editing default aircraft (like the DA62/FA18), “Sim object patch” is fine, editing 3rd party aircraft you need to set “Custom sim object patch”

5

Hello @SimbolFSReborn

Let us know if @kcgb suggestion solves the issue.
I think that’s the correct explanation.

Regards,
Sylvain

6

Yes it does for liveries and avionics, checking with Sound contractors to see..

R.

1 Like
7

This topic has been automatically closed after 60 days of inactivity since it was marked as by-design.

If there is important new information about this same report, you can use the “Request reopen” button below to ask the moderation team to review it again.
For other issues or broader discussion, please open a new topic in the appropriate category.