Search Issue Tracker
By Design
Votes
1
Found in
2020.2.0a1
2020.2.3f1
2021.1
2021.2
Issue ID
1313940
Regression
Yes
Assets are reimported when AssetPostprocessor class is renamed
Reproduction steps:
1. Open the user's attached project
2. Navigate to Editor/Folder1 and open TestPostProcessor2 script
3. Change the class name to TestPostProcessor1 (or anything else)
4. Return to Unity and observe the Console window
Expected result: Assets are not reimported
Actual result: Multiple notifications about assets postprocessing are logged (meaning that assets were reimported)
Reproducible with: 2020.2.0a1, 2020.2.5f1, 2021.1.0b7, 2021.2.0a5
Not reproducible with: 2018.4.32f1, 2019.4.20f1, 2020.1.17f1
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (2021.2.X):
Our Postprocessor hashes are based upon the class name so, whilst moving a Postprocessor shouldn’t trigger a reimport, usually renaming it would. The reason we use the class name rather than the GUID for the Postprocessor hash is that there’s not an easy way to convert from a Type to a GUID, not least because one type can be composed of multiple partial classes, each with their own GUIDs