Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.4.X
Votes
0
Found in
2019.4
2019.4.2f1
2020.2
Issue ID
1262788
Regression
No
[Metal][iOS] GPU crash on shader warmup with INSTANCING_ON keyword when Metal Editor Support and Metal API Validation are on
How to reproduce:
1. Open the attached 'SDGPUHang.zip' project
2. Make sure that Metal Editor Support and Metal API Validation are on in Project Settings
3. Build for iOS and open the Xcode project
4. Deploy Xcode project to an iOS device
Expected result: Project builds successfully
Actual result: GPU crash on launch with Xcode error is thrown to the console: 'Execution of the command buffer was aborted due to an error during execution. Caused GPU Hang Error (IOAF code 3)' or 'Execution of the command buffer was aborted due to an error during execution. Invalid Resource (IOAF code 9)'
Reproducible with: 2018.4.26f1, 2019.4.4f1, 2020.1.0b12
Not reproducible with: 2020.1.0b13, 2020.1.0b16, 2020.2.0a18
Reproducible with:
iPhone 8+ (iOS 12.0)
iPhone XR (iOS 13.4.1)
iPad Air 2 (iOS 11.0.3)
iPad 9.7 6th gen (iOS 12.1)
Notes:
- When Metal API Validation and GPU Frame Capture are enabled, error is thrown to the Xcode console: 'validateFunctionArguments:3469: failed assertion `Vertex Function(xlatMtlMain): missing buffer binding at index 2 for UnityInstancing_PerDraw0[0].''
- When testing Open GL, warnings are thrown to the Xcode console: 'ERROR: Shader SimplestInstancedShader shader is not supported on this GPU (none of subshaders/fallbacks are suitable)'
- When entering Play Mode errors are thrown to the console: 'Metal: constant buffer state is invalid'
- Testing on Mac Standalone, the application just displays a black screen, warning in player.log: 'WARNING: RGB Compressed BC6H UFloat format is not supported, decompressing texture', 'Vertex shader missing buffer binding at index 2'
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
- Inconsistent ParticleSystemVertexStream.PercentageAlongTrail data range in Trail Texture Modes except "Stretch"
- The Graph Debug Window can be right clicked through and the Node Workspace is manipulated instead
- [Linux] Top left corner of the screen is unresponsive when the Editor recompiles
- [Android] [Vulkan] Cubes stuck on the first few frames of rotation and application flickering when an Overlay Camera is added to the Camera Stack with MSAA enabled
- Profiling information icon does not update for Light Mode
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b13