Search Issue Tracker
Duplicate
Votes
2
Found in [Package]
12.0.0
Issue ID
1330273
Regression
Yes
[Android][OpenGLES3] SRP Batcher does not render when the Graphics API is set to OpenGLES3
How to reproduce it:
1. Open the user's attached project "NoSrpShaders.zip"
2. In the Player Settings make sure Graphics API is set to OpenGLES3
3. Build and Run it on Android
4. Observe the SRP Bacher code path time values in SRP batcher window
Expected result: SRP Bacher doesn't render and all SRP Bacher time values are 0,00ms
Actual result: SRP Bacher renders and all SRP Bacher time values are not 0,00ms
Reproduces on: 7.6.0 (2019.4.27f1), 10.5.0 (2020.3.9f1), 11.0.0 (2021.1.8f1), 12.0.0 (2021.2.0a17)
Could not test with: 2018.4 - URP was not yet available
Reproduced on these devices:
VLNQA00122, Samsung Galaxy S9 (SM-G960F), Android 10, CPU: NOT FOUND, GPU: Mali-G72
VLNQA00331, Huawei P20 lite (ANE-LX1), Android 9, CPU: HiSilicon Kirin 659, GPU: Mali-T830
VLNQA00321, Xiaomi MI 9 (MI 9), Android 10, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00038, Htc Desire 510 (HTC Desire 510), Android 4.4.3, CPU: Snapdragon 410 MSM8916, GPU: Adreno (TM) 306
VLNQA00285, Samsung Galaxy J4 Core (SM-J410F), Android 8.1.0, CPU: Snapdragon 425 MSM8917, GPU: Adreno (TM) 308
Notes:
- Not reproducible with Graphics APIs: Vulkan, OpenGLES2
- Not reproducible in the Editor's Play Mode
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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
This is a duplicate of issue #1331098