Search Issue Tracker
Fixed in 5.5.0f3
Votes
0
Found in
5.4.1f1
Issue ID
831836
Regression
No
GetPostprocessOrder method doesn't sort in which order postprocessors are executed
Reproduction steps:
1.Download and open attached project
2.Create any new asset
Actual outcome:
The console outputs:
- AssetPostprocessor named 'AlphaAssetPostProcessor' with Order #2 called.
- AssetPostprocessor named 'FirstAssetPostProcessor' with Order #1 called.
- AssetPostprocessor named 'NegativeAssetPostProcessor' with Order #-1 called.
- AssetPostprocessor named 'SecondAssetPostProcessor' with Order #3 called.
Expected outcome:
The console should output:
- AssetPostprocessor named 'NegativeAssetPostProcessor' with Order #-1 called.
- AssetPostprocessor named 'FirstAssetPostProcessor' with Order #1 called.
- AssetPostprocessor named 'AlphaAssetPostProcessor' with Order #2 called.
- AssetPostprocessor named 'SecondAssetPostProcessor' with Order #3 called.
Reproduced on: 5.2.3f1, 5.3.6f1, 5.4.0p2. 5.4.1f1, 5.5.0b1.
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
Add comment