Search Issue Tracker
Fixed
Fixed in 6000.2.5f1, 6000.3.0b2, 6000.4.0a1
Votes
0
Found in
6000.2.2f1
6000.3.0b2
6000.4.0a1
Issue ID
UUM-116433
Regression
No
WebGPU errors when point primitives are rendered
*Steps to reproduce:*
# Render geometry set to render as points
#
#
*Actual results:*
Error saying depthBiasSlopeScale must be 0 for point primitives
*Expected results:*
Points rendered
*Reproducible with versions:*
*Not reproducible with versions:*
*Can’t test with versions:*
*Tested on (OS):*
*Notes:*
*
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note (fix version 6000.4.0a1):
Fixed WebGPU depthBiasSlopeScale error rendering point primitives
Resolution Note (fix version 6000.3.0b2):
Fix WebGPU issue rendering point primitives
Resolution Note (fix version 6000.2.5f1):
Fix WebGPU issue rendering point primitives