--Enable override of default Attributes Registration checks #928
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.
Motivation and Context
Currently to register an object or stage attributes the specified render asset handle must exist, either as a valid object on disk, a valid existing primitive, or (in the case of a stage) be "none". If none of these conditions are true, the registration will fail and the attributes will not be added to the attributesManager library. This is useful in case errors exist in the attributes, so that object creation does not fail due to misnamed target assets.
The ability to override registration checks for object and stage attributes checks is useful for when render assets are computationally/"hand" crafted meshes. This PR adds a boolean argument to the registration process that allows for overriding the non-existing asset failure with a warning.
The default behavior will be to fail if specified render handle does not correspond to a known/knowable asset.
How Has This Been Tested
C++ and python tests pass
Types of changes
Checklist