Search Issue Tracker
Not Reproducible
Votes
0
Found in [Package]
2.2.2
Issue ID
1185474
Regression
No
[DirectX12][PostProcessing] Using DirectX12 and Ambient Occlusion from PPv2 results in a performance regression
Reproduction steps:
1. Open "1185474_minimal_2.zip" project
2. Enter play mode
3. Open the "Stats" tab
4. Note the FPS
5. Select "POSTPRO" GameObject
6. Disable "Ambient Occlusion" Post Processing effect
7. Note the FPS
Expected Result: Using Ambient Occlusion results in similar performance through Graphics API
Actual Result: Using Ambient Occlusion results in a Performance regression with DirectX12
Reproduced with: 2020.1.0a14, 2019.3.0b12, 2019.2.14f1, 2018.4.13f1, 2017.4.35f1
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