Search Issue Tracker
By Design
By Design in 2023.2.X
Votes
0
Found in
2020.3.45f1
2021.3.18f1
2022.2.7f1
2023.1.0b3
2023.2.0a2
Issue ID
UUM-26900
Regression
No
Error is thrown when enabling a Keyword on a Shader
How to reproduce:
1. Open the attached Project "shaderTest" and load the Scene "New Scene"
2. Enter Play Mode
3. Observe the Console
Expected result: No Errors are thrown in the Console
Actual result: The following Error is thrown:
"Metal: Vertex or Fragment Shader "Universal Render Pipeline/Lit" requires a ComputeBuffer at index 0 to be bound, but none provided. Skipping draw calls to avoid crashing."
Reproducible with: 2020.3.45f1, 2021.3.18f1, 2022.2.7f1, 2023.1.0b3, 2023.2.0a2
Reproduced on:
- MacOS Editor (Intel)
Could not test on:
- Windows (The Project contains a Plugin that does not work on Windows)
Notes:
- The Keyword that is being enabled is reserved by a Plugin in the Project using this Interface: https://docs.unity3d.com/Manual/LowLevelNativePluginShaderCompilerAccess.html
- Issue appears to only reproduce with URP Shaders and does not reproduce with the Standard 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
- Localization Group Rules bypasses Locale logic when SharedGroup asset provided
- UI Toolkit World UI Text Field unfocuses immediately when clicking on it using XR Controller
- Crash on CallWindowProcW when entering Play mode for the second time and running the Editor in the background while using System.Windows.Forms functions
- 2D Freeform Light shadows disappear when light center is offset from shape bounds
- Crash on MarkAllDependencies when opening scenes with Assets from the YarnSpinner package
Resolution Note:
The plugin needs to be compiled into a .dll in order for it to work.
Resolution Note (2023.2.X):
The plugin needs to be compiled into a .dll in order for it to work.