Search Issue Tracker
By Design
By Design in 2020.3.X
Votes
0
Found in
2020.3.46f1
Issue ID
UUM-31102
Regression
No
Metal shader error when using a StructuredBuffer
How to reproduce:
1. Download and open the attached project
2. Open "test scene" scene
3. Observe the console window
Expected outcome: No errors appear in the console window
Actual outcome "Metal: Vertex or Fragment Shader "Unlit/ShaderBug" requires a ComputeBuffer at index 0 to be bound, but none provided. Skipping draw calls to avoid crashing." error appears in the console window
Reproduced with: 2020.3.46f1, 2021.3.21f1, 2022.2.11f1, 2023.1.0b8, 2023.2.0a6
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
- An "RefreshInternalV2 is called before InitialRefresh" error is thrown when opening a project where a build profile with Player settings added is selected
- MeshCollider preview gizmo disappears from the Scene view when overriding the mesh asset using any 3D editing tool
- Tutorial project is not created when started from the Get set up tab
- Audio Listener Component expands when selected
- [iOS] Frame Debugger rendering output doesn't work with iOS builds
Resolution Note:
The error message is correct. The shader in the project declares a StructuredBuffer, but the project does not set a buffer. Use Material.SetBuffer to assign a buffer and the error message will go away.
Resolution Note (2020.3.X):
The error message is correct. The shader in the project declares a StructuredBuffer, but the project does not set a buffer. Use Material.SetBuffer to assign a buffer and the error message will go away.