Search Issue Tracker
Not Reproducible
Votes
0
Found in
2019.1.0a9
2019.1.0a10
Issue ID
1107279
Regression
Yes
[Android][Vulkan] Indirect Compute shader is not rendered on the screen
To reproduce:
1. Open the attached project;
2. Change Graphics API to Vulkan;
3. Build and Run "ShaderTest_Custom_ComputeShader_Indirect" scene on Android devices.
Expected result: On the left side there should be rendered a pink cube
Actual result: The cube with Compute shader is not rendered at all.
Not reproduced with: 2019.1.0a9
Reproduced with: 2019.1.0a10 - 2019.1.0a12.
Devices under testing:
Reproduces with:
VLNQA00217 Razer Phone 2 (Phone 2), Snapdragon 845 SDM845, Adreno (TM) 630, 8.1.0
VLNQA00017 Huawei Nexus 6P (Nexus 6P), Snapdragon 810 MSM8994, Adreno (TM) 430, 8.0.0
VLNQA00165 Samsung Galaxy S7 (SM-G930F), Exynos 8 Octa 8890, Mali-T880, 7.0
VLNQA00142 Samsung Galaxy S9+, Snapdragon 845, Adreno (™) 630, 8.0.0
VLNQA00093 Samsung Galaxy S6 Edge, Exynos 7 Octa 7420, Mali T760, 7.0
Does not reproduce with :
VLNQA00164 Samsung Galaxy S8 (SM-G950F), Exynos 9 Octa 8895, Mali-G71, 8.0.0
VLNQA00175 Samsung Galaxy Note 9, Exynos 9 Series 9810, Mali G72, 8.1.0
VLNQA00224 Samsung Galaxy A5, Exynos 7 Octa 7880, Mali T830, 7.0
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Incorrect Shader keyword activation for Shadows when no Light is present in URP
- Editor freezes when loading a specific AssetBundle
- WebGPU builds with Multithreading enabled crash on Safari
- Set as Value in UI Builder doesn't work across all properties.
- Calculating time durations in RenderDoc with DX12 causes 'Device Lost error' popup
Add comment