Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
38
Found in [Package]
2.2.2
Issue ID
1202538
Regression
No
[PostProcessing][URP][Built-in Renderer] FPS drop due to PPv2/Universal RP/Built-in Renderer
Reproduction steps:
1. Open "1202538" project
2. Build & Run for Android
3. Notice the FPS in the top left corner of the screen
4. Toggle "Post Processing" and "PBR Scene"
5. Notice the FPS
Expected Result: No FPS drop due to PPv2/Universal RP/Built-in Renderer
Actual Result: FPS drops due to PPv2/Universal RP/Built-in Renderer
Reproduced with: 2020.1.0a18, 2019.3.0f4, 2019.2.17f1, 2018.4.15f1
Did not reproduce on(No Packman): 2017.4.35f1
Reproduces with: IL2CPP, Mono; OpenGLES2, OpenGLES3, Vulkan;
Repro Devices:
VLNQA00173, Xiaomi Redmi 6 Pro (Redmi 6 Pro), Android 9, CPU: Snapdragon 625 MSM8953, GPU: Adreno (TM) 506
VLNQA00288, Samsung Galaxy J7 (SM-J730F), Android 8.1.0, CPU: Exynos 7 Octa 7870, GPU: Mali-T830
iPad mini 3 (iOS 10.3.2)
No Repro Devices:
VLNQA00287, Motorola moto g(7) power (moto g(7) power), Android 9, CPU: Snapdragon 625 MSM8953, GPU: Adreno (TM) 506
VLNQA00266, Xiaomi Mi A2 (Mi A2), Android 9, CPU: Snapdragon 660, GPU: Adreno (TM) 512
VLNQA00005, Samsung Galaxy S7 (SM-G930V), Android 7.0, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00262, Sony Xperia XZ Premium (G8141), Android 9, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00163, Lge V30 (LG-H930), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00015, Samsung Galaxy Note8 (SM-N950W), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00224, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830
VLNQA00320, Xiaomi - (Redmi Note 8 Pro), Android 9, CPU: MediaTek Helios G90T MT6785T, GPU: Mali-G76 MC4
VLNQA00138, Huawei P20 Pro (CLT-L29), Android 8.1.0, CPU: HiSilicon Kirin 970, GPU: Mali-G72
VLNQA00021, Samsung Galaxy S7 (SM-G930F), Android 8.0.0, CPU: Exynos 8 Octa 8890, GPU: Mali-T880
iPhone 6S iOS 13.3.1
VLNQA00242 iPad 7th gen (iOS 13.2.2)
VLNQA00301 iPhone 7 (iOS 12.3.1)
VLNQA00191 iPhone 6 (iOS 10.3.3)
Windows 10 GeForce GTX 1060 and Radeon (TM) Pro WX 5100 Graphics on all suupported graphics APIs
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
Resolution Note:
This umbrella case has been split into the following:
https://issuetracker.unity3d.com/issues/ppv3-bloom-does-more-pyramid-levels-than-ppv2-which-causes-non-negligable-driver-overhead
https://issuetracker.unity3d.com/issues/ppv3-lut-not-merged-due-to-per-frame-recalculation-which-causes-a-performance-regression-when-compared-to-ppv2
https://issuetracker.unity3d.com/product/unity/issues/guid/1294126/