Visibility override fixes #1320
Merged
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.
PR #1290 addressed various issues when drawing scene caches in maya's ViewPort2. This PR attempts to fix a regression introduced by this PR. The actual visibility determination is done correctly by
LiveScenebut then stomped over by any value present in the cache itself, disregarding overrides made in the scene. This change was introduces to fix an issue where lower level locations would be drawn even with an override higher up. But with theLiveSceneimplementation this seems not needed anymore.We also address an issue for scene shapes that represent a root location, e.g. when we have set it to
objectOnlywhere the various instances never checked visibility when set to "draw root bounds". That means we would always draw the bounds in the viewport even when overriding the visibility.