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
Comments (1)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
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