Search Issue Tracker
By Design
Votes
0
Found in [Package]
13.0.0
Issue ID
1369630
Regression
No
[Android] [ShaderGraph] Shader Graph textures are pixelated when running on Adreno GPU devices
How to reproduce:
1. Open the attached user's project 'AdrenoShaderGraphBug.zip'
2. Open Build Settings and add 'SampleScene' Scene to build
3. Build and Run the application on the Android platform
4. When the app loads, inspect texture on the device screen
Expected results: The texture is not pixelated
Actual results: The texture is pixelated
Reproducible with: 10.7.0 (2020.3.19f1), 11.0.0 (2021.1.23f1), 12.0.0 (2021.2.0b14), 13.0.0 (2022.1.0a11)
Could not test with: 7.7.1 (2019.4.31f1)
Reproducible on:
VLNQA00022, Xiaomi Redmi Note 3 (Redmi Note 3), Android 6.0.1, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
VLNQA00001, Google Pixel 2 (Pixel 2), Android 11, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00225, Qualcomm null (SDM845 for arm64), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
Not reproducible on:
VLNQA00288, Samsung Galaxy J7 (SM-J730F), Android 8.1.0, CPU: Exynos 7 Octa 7870, GPU: Mali-T830
N/A, Huawei - (NOH-NX9), Android 10, CPU: NOT FOUND, GPU: Mali-G78
VLNQA00316, Samsung Galaxy Note10 (SM-N970F), Android 9, CPU: Exynos 9 Series 9825, GPU: Mali-G76
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
- Diagnostic Warning Resets When Navigating Away and Returning to Diagnostics Settings
- Checkbox Collides with Text in Shader Graph Preferences Settings
- Crash on mecanim::animation::TransformValuesFromClip when entering the Play Mode in a project with Animancer Pro v8
- Connection to Named Pipes fails when server and client are run
- Subgraph Block cannot be dragged and dropped to the workspace and it throws errors
Resolution Note:
This is a precision issue based on the time-based scrolling effect. Best would be to use single precision for texture coordinates, but inserting a fraction node between the multiply and tiling/offset nodes will address the issue for this use case.