HYDRA-2005 : Fix depth peeling with USD data#370
Merged
debloip-adsk merged 3 commits intodevfrom Jan 20, 2026
Merged
Conversation
ppt-adsk
approved these changes
Jan 20, 2026
Collaborator
ppt-adsk
left a comment
ppt-adsk
left a comment
There was a problem hiding this comment.
Thanks for the nice documentation.
debloip-adsk
added
the
ready-for-merge
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Using depth peeling in MayaHydra was causing z-fighting artifacts with USD data due to it being "rendered" twice, once by MRenderOperations and once by MayaHydra's specific USD handling. To fix this, we specifically exclude MayaUsd from MRenderOperations, so they are only handled by MayaHydra's special USD handling.
I could not get the issue to repro in our test environment, even if I tried removing some of our test-specific options. I did find out that the artifacts are only present when MSAA is off, but that still doesn't make the bug work in testing. There is likely some other element needed to repro, possibly an idle event, that is needed for the issue to occur.
Depends on the following PR in maya-usd : Autodesk/maya-usd#4447