Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.46f1
2021.3.21f1
2022.2.11f1
2023.1.0b8
2023.2.0a6
Issue ID
UUM-30682
Regression
No
Errors are thrown when using custom AssetImporter scripts
Reproduction steps:
1. Open the attached project “ImporterBug”
2. In the Project window select “Assets/justcube” fbx file
3. Inspect the Console and Inspector windows
Expected result: The Inspector is using the custom Asset Importer
Actual result: There are errors thrown in the Console window “The previous instance of Editor.CustomModelImporterEditor has not been disposed correctly”
Reproducible with: 2020.3.46f1, 2021.3.21f1, 2022.2.11f1, 2023.1.0b8, 2023.2.0a6
Reproducible on: macOS 13.1 (Intel), Windows 10
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:
Embedding AssetImporterEditors inside another Editor is not supported
Resolution Note (2023.2.X):
Embedding AssetImporterEditors inside another Editor is not supported