Fix a couple issues with glTF tangent processing. #6302
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.
Recently I created a new model, NormalTangentMirrorTest to test what happens in a rendering engine when a glTF supplies tangent vectors. A previous model called NormalTangentTest was testing an engine's ability to calculate missing tangent vectors.
Cesium does a great job of calculating any missing tangent vectors, but unfortunately, when the vectors are supplied in the model, things were very broken. Looking at the code, I found these issues:
'TANGENT'
asVEC3
when the glTF spec says it'sVEC4
.u_modelViewMatrix
instead ofu_normalMatrix
.w
component of the tangent into account.The glTF spec has this to say about using the
w
component of supplied tangent vectors:On master, my new tangent test model looks like this:
On this branch, with the above-mentioned fixes applied, things look correct: