Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2018.3.0b11
2019.3
2020.2
Issue ID
1227467
Regression
No
[Mobile] Android and iOS do not support fp16 on Compute Shader
How to reproduce:
1. Open the attached "fp16Test" Project
2. Switch the target platform to iOS or Android
3. In the Project window, select "NewComputeShader" and observe the Inspector
Expected result: the Compute Shader is compiled without any errors
Actual result: there are errors indicating "Unknown parameter type"
Reproducible with: 2019.3.7f1, 2020.1.0b3, 2020.2.0a5
Could not test with: 2017.4.38f1, 2018.4.20f1, 2019.2.21f1 due to URP not being available for the shader
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a8