Search Issue Tracker
Fixed
Fixed in 1.0.0, 2023.1.0
Votes
0
Found in [Package]
2021.3.0
2022.1.0
2022.2.0
2023.1.0
Issue ID
DANB-133
Regression
Yes
Importer(TextureImporter) generated inconsistent result for asset when importing assets from Unity 2020.3
How to reproduce:
1. Open the attached project "Heads"
2. Open the "SCENE" scene
3. Observe the result
Expected result: Assets look the same as they look in 2020.3 (heads are not missing)
Actual result: Heads are missing, "Importer(TextureImporter) generated inconsistent result for asset" warning in the Console or in the Editor.log
Reproducible with: 2021.2.0f1, 2021.3.5f1, 2022.1.5f1, 2022.2.0a17, 2023.1.0a1
Not reproducible with: 2019.4.38f1, 2020.3.36f1, 2021.1.27f1
Reproducible on: Windows 11 Pro
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
- Mouse inputs cannot be inputted when searching the Shortcuts Menu by type "Shortcut"
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
Resolution Note (fix version 2023.1.0):
Fix will be available on Unity 2023.1.0a10 and above
For the fix to work, it needs to be upgraded from the original 2020.3 asset metafiles.
The repro case metafiles has already been upgraded. Thus using the repo project attached in this bug to verify the fix won't work.
One way to achieve that is to edit the individual texture importer meta file and remove the `nameFileIdTable:` entires
Resolution Note (fix version 1.0.0):
Fix for this issue will be available in Unity 2022.2.0b9 and above
Resolution Note (fix version 1.0.0):
Fix for this issue will be available on Unity 2021.3.11f1 and above
Resolution Note (fix version 1.0.0):
Fix for this issue will be available on Unity 2022.1.18f1 and above