[bug-fix] Object-attached Agent with Split Semantic Scene #694
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
Python implementation of split SEMANTIC render assigns the agent SceneNode's parent to the semantic SceneGraph root before rendering. Attaching an agent to a simulation object creates all rendering assets for the object under the agent's SceneGraph sub-tree. This results in an error during the secondary SEMANTIC rendering pass over the active SceneGraph added in #679.
For reference this error displays as:
This PR re-assigns the agent SceneNode's parent to the active SceneGraph root before the 2nd pass to fix this bug.
How Has This Been Tested
Still no separate semantic testing on CI, leading to this bug slipping through. Tested locally.
Types of changes
Checklist