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
- “This version of Unity is not currently available for use with Build Automation” warning is shown only after setting up Cloud and Version Control warnings when adding Build Automation to a Build Profile
- Crash on ProfilerSymbolsDelayedDeletion::AddCloneObject when deserializing an object-instantiate marker with a dangling/corrupt name string
- Characters overlap preceding text when monospace tags are used on a TMP_Text component set to RTL
- Wrong range is displayed in a 'resolutionPerPatch is clamped to the range of' warning
- Debug mode fails to build in Visual Studio when .csproj file is generated for Built-in packages
Add comment