[Houdini] Provide support for adding in-memory stages to the GusdStageCache #775
Conversation
This file contains 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
anonymous root layer identifiers.
explicit insertion of stages into the cache. This could be used for stages loaded from files on disk, but is primarily intended for adding in-memory stages to the cache.
|
Filed as internal issue #USD-5099 |
pixar-oss
added a commit
that referenced
this pull request
Mar 14, 2019
[Houdini] Provide support for adding in-memory stages to the GusdStageCache (Internal change: 1947497)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adding support for the explicit addition of stages to the GusdStageCache. The use case here is that we have in-memory stages (with anonymous root layers) from which we would like to construct USD packed primitives. Rather than having the GusdStageCache construct new (masked) stages from these in-memory stages, it makes more sense to just tell the cache that these full stages are already in memory.
Also had to fix the cache invalidation code to properly deal with anonymous layer identifiers so that these in-memory stages can be modified, and the cache properly invalidated in response.