Search Issue Tracker
Fixed in 2022.1.X
Votes
5
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.1.0f2
2019.2.0a1
2019.3.0a1
Issue ID
1163684
Regression
No
AssetModificationProcessor.OnWillCreateAsset Callbacks are inconsistent with different Assets
How to reproduce:
1. Open the attached "CustomSceneImporter.zip" Project
2. Create the material by Right-clicking Project View and selecting Create > Material
3. Create a Scene by Right-clicking Project View and selecting Create > Scene
4. Observe the difference in the Console
Expected Behaviour: All Asset Files should consistently invoke Callbacks (either both or just meta files)
Actual Behaviour: On some Asset Files Callbacks are only invoked on .Meta Files and on some on both. (.meta and the asset itself)
Reproducible with: 2017.4.29f1, 2018.4.3f1, 2019.1.7f1, 2019.2.0b6, 2019.3.0a6, 2019.4.33f1, 2020.3.22f1, 2021.2.2f1, 2022.1.0a15
Note: The difference is not only with Scene/Material, other assets may also behave differently.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Add comment