Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
0
Found in
2019.3.7f1
2019.3.9f1
2020.2
Issue ID
1243747
Regression
Yes
Mesh.RecalculateTangents drops 3rd & 4th component of UV0 (for Vector3/Vector4 UVs)
How to reproduce:
1. Open the attached project's Scene labeled "Temp"
2. Enter the Play Mode
3. Observe the Console Window
Expected result: UVs are not changed after Mesh.RecalculateTangents() function is called
Actual result: Vector4 UV .z and .w components are changed to zeroes after Mesh.RecalculateTangents() function is called
Reproducible with: 2019.3.7f1, 2019.3.13f1, 2020.1.0b9, 2020.2.0a10
Not reproducible with: 2017.4.40f1, 2018.4.22f1, 2019.3.6f1
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 (fix version 2020.2):
Fixed in Unity 2020.2.0a12
Resolution Note (fix version 2020.1):
Fixed in Unity 2020.1.0b10
Resolution Note (fix version 2019.3):
Fixed in Unity 2019.3.15f1