Search Issue Tracker
Won't Fix
Votes
3
Found in
2022.2.0a2
Issue ID
UUM-5883
Regression
Yes
[Android] [URP] Occlusion culling has performance regression in CullScriptable function when using specific devices
Reproduction steps:
1. Open the attached project "OCIssue-2019.zip"
2. Build and Run on Android device
3. Select CPU Usage Profiler Module
4. Select Raw Hierarchy in Module details panel
3. In Module details panel observe CullScriptable time (go to PostLateUpdate.FinishFrameRendering > RenderPipelineManager.DoRenderLoop_Internal() > Inl_UniversalRendererTotal > Inl_RendererCameraStack > Inl_UniversalRenderPipeline.RenderSingleCamera)
Expected result: The average time of CullScriptable function is ~2.5 ms (values range from 1.6 ms to 4 ms, most of the time stays under 3 ms)
Actual result: The average time of CullScriptable function is ~3.5 ms (values range from 2.1 ms to 5 ms, rarely rises to 7ms, most of the time stays over 3 ms)
Reproducible with: 13.1.3 (2022.1.0b1), 13.1.4 (2022.1.0b3), 13.1.2 (2022.2.0a1, 2022.2.0a2)
Not reproducible with: 7.7.1 (2019.4.34f1), 10.8.1 (2020.3.25f1), 12.1.3 (2021.2.7f1), 13.1.1 (2022.1.0a16)
Reproducible with:
VLNQA00225, Qualcomm null (SDM845 for arm64), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
Not reproducible with:
VLNQA00288, Samsung Galaxy J7 (SM-J730F), Android 8.1.0, CPU: Exynos 7 Octa 7870, GPU: Mali-T830
VLNQA00001, Google Pixel 2 (Pixel 2), Android 11, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00316, Samsung Galaxy Note10 (SM-N970F), Android 9, CPU: Exynos 9 Series 9825, GPU: Mali-G76
Notes:
- In Unity 2022.2.0a1 CullScriptable time can go under 2 ms when launching the app but after ~30 seconds of running the app it rarely goes under 3 ms
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
We are too low on resources to look at this issue, if it is a major issue for you please re-open it