Search Issue Tracker
By Design
Votes
0
Found in [Package]
7.2.0
Issue ID
1255808
Regression
Yes
Procedurally generated normals shade the mesh's material in two pieces/artifacts
How to reproduce:
1. Open attached project "TestNormal20194.zip" and scene "TestNormal"
2. In Scene view, observe the Quad from different angles
Expected result: the Quad material does not change color
Actual result: the Quad is split in half and depending on the angle different shades are shown
2020.2
Reproducible with: 2019.3.0f6, 2019.3.7f1 (7.2.0), 2019.4.2f1 (7.3.1), 2020.1.0b14, 2020.2.0a15 (8.1.0, 9.0.0-preview.14)
Not reproducible with: 2018.4.24f1 (4.10.0-preview), 2019.3.7f1 (7.1.8)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
The result the user was getting before was relying on behavior that's actually incorrect. Shader Graph was able to fix this behavior (and therefore match the renderpipeline) and now it's not doing what the user expects but it's actually correct behavior.
Vertex normals are interpolated linearly, not spherically. It is suggested to pass along the data in a UV instead to get the expected behavior in packages with the fix present.