Fixed an issue with mesh normals when Unity exports them to Houdini #35
Conversation
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
1 participant
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.
Unity is exporting wrong normals to Houdini at the moment. It converts positions from the local space into the world space, but keeps normals in the local space. I added a local-to-world conversion for normals in this PR.
Keep in mind that we should use a transposed worldToLocal matrix instead of a regular localToWorld matrix with normals to make it work correctly with nonuniform or negative scales.
I made this PR for 19.5 because I'm working with this version of Houdini. But it seems that the same issue is in 20.5 as well.