Search Issue Tracker
Won't Fix
Votes
0
Found in
5.5.0f3
Issue ID
861866
Regression
Yes
[Gles3][Adreno] Custom shaders are not rendered on some Adreno devices
How to reproduce:
1. Open the attached project
2. Make sure that graphics API is set to Gles 3
3. Build and run on Android device
Result: Model is not rendered (only eyebrows are visible)
Reproducible: 5.5.0f3, 5.5.1p3, 5.6.0b8
Not reproducible: 5.4.4p2
DUT(reproducible):
OpenGLES3
LG G5 [LG-H850], Qualcomm Snapdragon 820, Adreno 530, OS 6.0.1
Motorola Moto G (4), Qualcomm Snapdragon 617, Adreno (TM) 405, OS 6.0.1
Samsung Galaxy S7 [SM-G930V], Qualcomm Snapdragon 820, Adreno 530, OS 6.0.1
DUT(not reproducible):
OpenGLES2, OpenGLES3
Samsung Galaxy S 5 Neo [SM-G903F], Samsung Exynos 7 Octa, ARM Mali-T720, OS 6.0.1
Galaxy S III LTE (T-Mobile) [SGH-T999L] Qualcomm Snapdragon S4, Adreno 225, OS 4.1.1
iPhone 6+ (iOS 10.1)
OpenGLES2
LG G5 [LG-H850], Qualcomm Snapdragon 820, Adreno 530, OS 6.0.1
Motorola Moto G (4), Qualcomm Snapdragon 617, Adreno (TM) 405, OS 6.0.1
Samsung Galaxy S7 [SM-G930V], Qualcomm Snapdragon 820, Adreno 530, OS 6.0.1
WON'T FIX: this issue is Adreno drivers bug and it is no longer reproducible with Android 7.0. Issue only happens when the same vectorized matrix is being used in both vertex and fragment shader. Such case works correctly only if all 4 vectors of the matrix are being used within both vertex and fragment shaders. Non vectorized matrices work correctly. Resolving as "won't fix", because it's rare case and switching shaders generation to non vectorized matrices could potentially cause other issues.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Usability] Can't create Target Frame Time presets in Profiler
- Text is not displayed in the Inspector window when using Korean characters
- [macOS][iOS][IL2CPP] Crash when using the nullable enum as a parameter and passing a default value into it.
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
Add comment