Search Issue Tracker
Fixed in 2022.1.X
Votes
0
Found in
2019.4
2020.3
2021.1
2021.1.3f1
2021.2
Issue ID
1331542
Regression
No
Secondary Texture AssetImporter reference error when using same texture as Main Texture in Sprite Editor
Reproduction steps:
1. Open project "case_1331542"
2. Open Sprite Editor from Windows>2D>Sprite Editor
3. Select the Sprite "T_MAINTEXTURE"
4. Change the Sprite Editor to Secondary Textures
5. Set the Texture to "T_MAINTEXTURE"
6. Press Apply
7. Observe Console window
Expected result: Secondary Texture is applied
Actual result: Error occurs and Secondary Texture is set to None
Reproducible with: 1.0.0 (2019.4.24f1, 2020.3.4f1, 2021.1.4f1, 2021.2.0a15)
Could not test with: 2018.4.33f1 (Secondary Textures not featured in Sprite Editor)
Error:
AssetImporter is referencing an asset from the previous import
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
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Inconsistent "Mock HMD Loader" naming in the "Project Settings"
- Search Field breaks when deleting a Search Expression that has been converted to a Visual Query Block
- Outdated documentation page is linked when clicking on the Help icon for "Virtual Texturing" Module in Profiler Window
- [Linux] No “File already exists” pop-up thrown when saving Shader Variants with an already existing name from Build Profiles or Project Settings window
Resolution Note (fix version 2022.1):
A fix for this issue will be available on Unity 2022.1.0a2 and above