Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.1.X, 2021.2.X
Votes
1
Found in
2020.3.10f1
2021.1.13f1
2021.2.0b1
Issue ID
1342131
Regression
Yes
FBX model has broken UV mapping when the imported model is duplicated or using a newer Unity version
How to reproduce:
1. Create a new project using the default 3D template
2. Import an FBX model
3. Drag the model into the Scene View
4. Duplicate the model (shortcut CMD+D)
5. Drag the duplicated model into the Scene View
6. Inspect the original and duplicated models
Expected result: Both models have properly mapped UVs and Textures and look the same
Actual result: Either the duplicated or both of the models have broken UV mapping
Reproducible with: 2020.3.10f1 (UV mapping break when the model is duplicated), 2020.3.11f1, 2020.3.13f1, 2021.1.13f1, 2021.2.0b1 (UV mapping breaks when the model is imported)
Not reproducible with: 2019.4.28f1, 2020.3.9f1
Notes:
- UV mapping is broken on both the imported model and the duplicated one when using Unity 2020.3.13f1, 2021.1.13f1, 2021.2.0b1
- Tested with FBX model exported from Cheetah3D
- Reimporting the model on 'not reproducible' versions fixed the issue when downgrading the project
- Reimporting the model on 'reproducible' versions introduces the issue when upgrading the project
-
Seola
Jul 26, 2023 12:28
It still doesn't work. Unity version 2022.3.5f1
According to my observations, this is not UV, this is bug material.
1. Create a material with a mobile/diffuse shader (let's call it mat1)
2. Drag the Model to the stage
3. Assign a material to it
4. Duplicate many objects (I have 1444).
5. Duplicate material (mat1)
6. Assign a new material (mat2) to one of the models
7. All models will look like they have no UV.How to fix:
1. Create a new material
2. Assign mobile/diffuse shader
3. Select all models and assign a new material to them.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2022.1):
Fixed in Unity 2022.1.0a6 and above
Resolution Note (fix version 2021.2):
Fixed in Unity 2021.2.0b9
Resolution Note (fix version 2021.1):
Fixed in 2021.1.20f1
Resolution Note (fix version 2020.3):
Fixed in Unity 2020.3.17f1