Search Issue Tracker
Fixed in 4.3.0
Votes
0
Found in [Package]
4.1.0
Issue ID
1194858
Regression
No
[ProBuilder] Bevel edges is generating NullReferenceException in the console
With default value and taking a Sphere or Torus shape.
1. Create one of these objects via the New Shape PB tool
2. Enter in Edge selection mode
3. Region select edges on the object or all of them
4. Browse for the Bevel tool in PB Window and press the button
Result: a NullReferenceException is generated in the console
Expected: The Bevel action is still computed and shows on the object
Note:
This seems to be caused by a too high value of Bevel here the value will actually makes edges intersect each other once computed.
In the case of the Torus shape, the exception will log in the console and we'll lose the material on the object
In the case of the Sphere shape, the object will appears unchanged but deselecting the edges and reselect all of them, we'll actually see the edges generated by the Bevel action. If we undo a couple of time, the object will eventually show the correct result.
This is reproducible also from the Bevel settings window, playing with very small value will produce the right effect but as soon as we pass a certain value where the edges will intersect each other, the error will occur.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Can’t delete gradient keys with Mac keyboard or context menu options
- Editor freezes for a few minutes when closing or switching a VFX window that was opened in a previous project
- UI Overlaps when switching Render Pipeline Asset for different Quality Levels in Quality Project Settings
- Ray Tracing Shader link to the documentation isn’t working
- Warning "BatchRendererGroups currently don't support override shaders" is spammed in Play mode when using H-Trace WSGI with BatchRenderGroups
Add comment