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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment