Search Issue Tracker
Fixed in 11.0.0
Votes
2
Found in [Package]
9.0.0 - preview.35
Issue ID
1263720
Regression
No
[URP][Mobile] SRP Batcher is not visible on mobile devices in Frame Debugger
Reproduction steps:
1. Open the attached user's project "srp-batcher-android.zip"
2. Open the "SampleScene.unity" under the "Assets/Scenes" folder
3. In the Player Settings make sure Graphics API is set to OPENGL ES 3
4. Under the "Assets/Settings" folder make sure that the "UniversalRP-HighQuality.asset" has SRP Batcher turned on in the Inspector
5. Build for Android
Expected result: SRP Batcher is visible in Frame Debugger on Android Devices
Actual result: SRP Batcher is not visible in Frame Debugger on Android Devices (See attached Expected.png and Actual.png)
Reproduces on: URP 7.3.1, 7.4.1 (2019.4.6f1), URP 8.1.0, 8.2.0, 9.0.0 - preview.35 (2020.1.0f1, 2020.2.0a19)
Could not test on 2018.4 due to no SRP Batcher option in LWRP asset settings
Reproduces on these devices:
N/A, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00313, Huawei Y6 Ⅱ Compact (HUAWEI LYO-L01), Android 5.1, CPU: MediaTek MT6735, GPU: Mali-T720
VLNQA00310 iPad Pro 12.9 1st gen (iOS 13.4.1)
Reproduces with Graphics APIs: OpenGLES2, OpenGLES3
Does not reproduce with Graphics APIs: Vulkan
Notes:
-Does not reproduce on a new project
-On Android Graphics API is set to OPENGL ES 3 and both devices support SRP Batcher
-SRP Batcher is visible in the Editor in Frame Debugger
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
- 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
CChong_at_Infinity
Feb 19, 2021 04:14
Is there a chance for this to be backported to URP 7.x for Unity 2019.4 LTS?