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
- Override move options in Inspector are not disabled when only one Override is added in URP Volume
- “NONE”/“ALL” text in Adaptive Probe Volumes Option Override is too light when Editor theme is set to Light
- Default Volume Profile property does not get reset when the property is selected and the reset button is pressed
- Saving Visual Effect Graph closes it in Visual Effect Graph window
- [Android] "Texture2D.ReadPixels" writes pixels into a texture incorrectly when used with OpenGLES3
Add comment