Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2022.2.2f1
2023.1.0a25
2023.2.0a3
Issue ID
UUM-27627
Regression
Yes
Post Processing does not work when Motion Blur and Depth of Field effects are enabled or disabled
Reproduction steps:
1. Open the attached “Test Project” project
2. Open “Scenes/SampleScene” Scene
3. Select “Volume” GO in the Hierarchy window
4. Enable “Motion Blur” and “Depth of Field” options under the “Volume” component in the Inspector window
5. Observe the Game View
Expected result: All Post Processing effects are visible
Actual result: Post Processing isn’t working
Reproducible with: 2022.2.0b1, 2022.2.2f2, 2023.1.0a25, 2023.2.0a3
Not reproducible with: 2020.3.44f1, 2021.3.16f1, 2022.1.24f1, 2022.2.0a15
Can’t reproduce with: 2022.2.0a16-2022.2.0a18 (Post Processing not working in the Camera, therefore making Game View black)
Reproducible on: Windows 10
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
- 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
Resolution Note:
Issue is no longer reproducible in 2022.3 LTS and 2023.2 or later.
Resolution Note (2023.2.X):
Issue is no longer reproducible in 2022.3 LTS and 2023.2 or later.