Search Issue Tracker
By Design
By Design in 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.3.5f1
6000.4.0b5
6000.5.0a5
Issue ID
UUM-132732
Regression
No
“d3d12: trying to draw without an active vertex or fragment program.” error is thrown after assigning Materials to certain Elements in UI Builder
Reproduction steps:
1. Create a new project
2. Create > UI Toolkit > UI Document
3. Double-click UI Document to open UI Builder
4. Drag Button Element to the Hierarchy
5. Assign any Material in the Material section of the Inspector (e.g. “Default-ParticleSystem”)
6. Observe the Console
Actual result: “d3d12: trying to draw without an active vertex or fragment program.” error is thrown
Expected result: No warnings or errors are thrown
Reproducible with: 6000.3.5f1, 6000.4.0b5, 6000.5.0a5
Couldn’t reproduce with: 6000.0.66f1 (Due to Material section not existing)
Reproduced on: Windows 11, macOS Sequoia 26.2 (M4)
Note:
- Issue is not reproducible more than once on the same project
- “Missing vertex input: normal, dummy data will be provided” error is thrown when assigning “Default-Diffuse”, “Default-Material”, “Default-Terrain-Diffuse”, “Default-Terrain-Specular” and “Default-Terrain-Standart” Materials in macOS
- “Metal: cannot write to unused constant buffer.” Error is thrown after assigning “Default-ParticleSystem” Material in macOS
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
UI Toolkit expects a UI shader. In the future we will try to add extra indications to make it clearer, instead of trying to render with an incompatible shader. If you need help creating a compatible shader, see this manual page:
https://docs.unity3d.com/Manual/ui-systems/get-started-with-ui-shader-graph.html
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.
Resolution Note (6000.5.X):
Thank you for reporting a bug to Unity.
After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow.
UI Toolkit expects a UI shader. In the future we will try to add extra indications to make it clearer, instead of trying to render with an incompatible shader. If you need help creating a compatible shader, see this manual page:
https://docs.unity3d.com/Manual/ui-systems/get-started-with-ui-shader-graph.html
We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements.