You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Suggestion
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.
Problem
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.
Suggestion
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.
Note
moved from here ynput/ayon-core#188
[cuID:AY-3895]
The text was updated successfully, but these errors were encountered: