Export USD with USD contribution workflow using existing 'model' creator #206
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
BigRoy
added
the
type: enhancement
1 task
Contributor
Author
|
Closing this as dedicated creator seemed to be the easier/safer approach for now. Closing in favor of #205 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changelog Description
Allow the
modelproduct type creator in Maya to also publish ausdoutput that also gets recognized asusdfamily and hence triggers the USD contribution workflow.Additional review information
This is an alternative approach to #205
Most of the 'issues' and discussion is hence described in that PR description already - so best to read up that PR description for this one too.
Together the two PRs are a 'starting point' for a discussion on how we should be doing this going forward.
This PR is more 'hacky' in the current publishing ecosystem - but to me feels a bit more logical where a new plug-in comes in and is capable of stating that "now add this functionality to this instance". But maybe conceptually it's crazy within how the AYON publishing ecosystem works?
Fix #207
TODO
Testing notes:
modelwith USD asset contribution workflow