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
- Errors "InvalidOperationException: Trying to use a texture (_InternalGradingLut)..." and “Render Graph Execution error” shown and Scene turns black when 16 or more Render Objects are used
- GameObjects in the Game View are rendered differently than in the Scene View when the Rendering Path is set to "Deferred" and Screen Space Shadows Renderer Feature is added
- Errors “InvalidOperationException: Trying to use a texture (_CameraDepthTexture)...” and “Render Graph Execution error” shown when selecting GameObjects with Mesh Renderer from the Hierarchy
- macOS stutters in a minimal project
- [Usability] HDRP Wizard calls for VR fixes when opening the HDRP Wizard a second time after they have already been applied and the Wizard has finished checking
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