Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
0
Found in
2019.1.0b10
2019.3.15f1
2019.4
2020.1
2020.2
Issue ID
1271787
Regression
Yes
[Android][GLES3] Using framebufferfetch and sampling a texture at the same time throws GSL link errors
Repro steps:
1. Open attached project
2. Build and Run on Android
3. Check for errors in the logcat
Actual: GLSL link error: Error: uniform $inoutSamplerSV_Target0 location or component conflict with others.
Reproducible with: 2019.1.0b10, 2019.4.9f1, 2020.1.4f1, 2020.2.0b1
Not reproducible with: 2018.4.27f1, 2019.1.0b9
Tested and reproduced on these devices:
----------, Google Pixel 3 XL (Pixel 3 XL), Android 10, CPU: NOT FOUND, GPU: Adreno (TM) 630
VLNQA00001, Google Pixel 2 (Pixel 2), Android 11, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00317, Vivo V1924A (V1924A), Android 10, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
----------, Oneplus OnePlus 6 (ONEPLUS A6003), Android 10, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
Didn't reproduce on:
VLNQA00078, Motorola Nexus 6 (Nexus 6), Android 7.1.1, CPU: Snapdragon 805 APQ8084AB, GPU: Adreno (TM) 420
VLNQA00128, Samsung Galaxy Note8 (SM-N950F), Android 9, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
Notes:
- Doesn't repro on Vulkan
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment