Search Issue Tracker
Fixed in 10.0.0
Votes
0
Found in [Package]
8.1.0
Issue ID
1242005
Regression
No
PPv3 Bloom does more pyramid levels than PPv2 which causes non-negligable driver overhead
How to reproduce:
1. Open the attached "URP_Bloom" and "PPv2_Bloom" projects
2. Build both projects for Android
3. Inspect the performance of each build
Expected results: URP/PPv3 has similar/better performance when compared to PPv2
Actual results: URP/PPv3 has worse performance when compared to PPv2
Reproduced with: URP 7.3.1 (2019.3.12f1), URP 8.1.0 (2020.2.0a10)
Repro Devices:
VLNQA00173, Xiaomi Redmi 6 Pro (Redmi 6 Pro), Android 9, CPU: Snapdragon 625 MSM8953, GPU: Adreno (TM) 506
Note: The comparison was made between PPv2 Fast Bloom and PPv3 Bloom. With PPv2 Bloom Fast mode disabled, PPv3 Bloom performs better
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
sas67uss
Jan 01, 2021 18:30
Do the bug fixes in the latest version of URP apply to previous versions as well?
For example, I want to use the unity 2019.4 LTS , which finally supports URP 7.5 . Will the bugs fixed in URP 10 also apply to URP 7.5?
because unity said that URP was including in unity 2019.4 LTS