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
- UI Toolkit Editor Window Creator becomes deformed and stretched when the “Enter” key is pressed
- “Assertion failed on expression: 'IsFinite(distanceForSort)’” is spammed in the Console when changing Trail GameObject position to a very high number
- VFX Graph Node documentation icon is pixelated
- [macOS] Pop-up windows are misaligned on macOS Tahoe 26.0
- Cutout box is covered in a shadow when the object that houses the cutout is casting shadows
Add comment