Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2019.3.10f1
2019.3.13f1
Issue ID
1246876
Regression
Yes
Default UV3 value isn't zero when importing an FBX Asset with missing UV3 values
How to reproduce:
1. Open the "FBXPartialUVDefaultIssue-2019.3" project
2. Reimport "buil_lowBuilding_U.fbx" from Assets folder
3. Select "A_LOD0" Mesh inside "buil_lowBuilding_U" in Project window
4. Run Test > "Dump UV3" MenuItem
Expected result: the missing UV3 Vector2 has a value of (0,0)
Actual result: the missing UV3 Vector2 has a random value
Reproducible with: 2019.3.10f1, 2019.3.14f1
Not reproducible with: 2018.4.23f1, 2019.3.9f1, 2020.1.0b9, 2020.2.0a11
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
- Incorrect vehicle rotation when using ForceMode.VelocityChange
- [Linux] Dropdown Menus are filled with empty entries when the Menu intersects with the Editors borders
- [HDRP] [Metal] Tiled artefacts when using DRS
- [HDRP] Empty template starts with incorrect Physically Based Sky ground
- Big chunk of "Untracked" memory in the Memory Profiler screenshot when a custom .obj file is loaded while in Play Mode
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a15
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b14
Resolution Note (fix version 2019.4):
Fixed in 2019.4.3f1