Unreal: Representation priority on Layout loading

[antirotor]

Is there an existing issue for this?

• I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?

When loading layouts to DCC, representations of assets referenced there might not be optimal for it. Imagine layout published from Maya, where assets have both alembic and FBX representations, but alembics are used during the publishing.

How would you imagine the implementation of the feature?

When you load such layout into Unreal for example, alembics are used, but it might be better to use FBX representation then (or any other, based on needed workdlows). Right now, you can either re-publish this layout with different loaded representations or change them after layout is loaded, but that adds unnecessary steps into it. It would be nice to have settings for the Layout loader where you could specify preferred Loader plugin and representation (if exist). That in itself could be helpful even on other load pipepelines.

Are there any labels you wish to add?

• I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

No response

Additional context:

No response

[cuID:AY-3895]

[antirotor]

closing for ynput/ayon-unreal#6