Search Issue Tracker
By Design
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
- Editor crash on "PPtr<Shader>::operator Shader*() const" when checking in changes with a very long comment in Unity Version Control window
- [Ubuntu] Toolbar and menu items for Version Control lack spaces in text on Linux
- Unity Version Control window Pending Changes tab’s Item checkbox is unresponsive when clicked and the item list is empty
- Audio stuttering occurs when heavy processing is performed while OnAudioFilterRead is in use
- Inconsistent Node search results in VFX Graph
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.