Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2021.2.2f1
Issue ID
1381009
Regression
No
[AssetDB] Strange import dependencies between textures, FBX files, and TextureImporter
When a ModelImporter creates a Material as a sub-asset that uses a texture in the project, changing any setting in that texture will re-import the full Model.
Expected scenario: The model only re-import if the texture is moved in the project so the Material has a chance to reference another texture if a new one is a better match.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2022.1):
Fixed in 2022.2.0a1