Search Issue Tracker
By Design
Votes
0
Found in
2017.4
2018.4
2019.2
2019.3
2020.1
Issue ID
1211881
Regression
No
Different Tangent types result in different vertices count in the same fbx model
Reproduction steps:
1. Open "1211881" project
2. Select "Head" Game Object in the scene
3. In the Inspector click on the "Mesh" selector dot
4. In the Model preview, notice the number of verts
5. In the Project window Select "Head.FBX"
6. In the Inspector change the "Tangents" to some other value
7. Repeat Steps 2-4
Expected Result: The number of verts is the same
Actual Result: The number of verts is different
Reproduces with: Direct3D11, Direct3D12, Vulkan, OpenGL
Reproduced with: 2020.1.0a17, 2020.1.0a16, 2020.1.0a11, 2020.1.0a1, 2019.3.0f5, 2019.2.19f1, 2018.4.15f1, 2017.4.36f1
Could not test on(No vertice count): 2020.1.0a20, 2020.1.0a18
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
This is the expected behavior in Unity.
The number of vertices are driven by how the tangents are treated when setting the normals, which can vary depending on approach used to calculate.