Search Issue Tracker
Fixed
Fixed in 5.2.X, 6.0.X
Votes
0
Found in [Package]
5.2.3
6.0.4
Issue ID
PBLD-199
Regression
No
[ProBuilder] NullReferenceException when using the Cut Tool
Reproduction steps:
1. Open the attached “ProBuilderError.zip” project
2. Open the “Sample Scene”
3. Select the “Cube” GameObject from the Hierarchy
4. In the Scene view tools change Active context to ProBuilder (Click the very top widget with an orange grid and a pencil)
5. Select the “Cut Tool”
6. Add a few cut points and connect the path
7. Observe the Console
Expected result: No errors
Actual result: “NullReferenceException: Object reference not set to an instance of an object” error
Reproducible with: 5.0.7 (2022.1.0b1), 5.2.3 (2021.3.47f1, 2022.3.56f1), 6.0.4 (6000.0.35f1, 6000.1.0b2)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- Might need to repeat the 6th step a few times for the issue to appear
- Pressing CTRL+Z after the error, causes even more errors and exceptions to be thrown, like “GUI Error: You are pushing more GUIClips than you are popping. Make sure they are balanced.” and “IndexOutOfRangeException: Index was outside the bounds of the array.”. After that, the ProBuilder context appears to be non-interactable and gets stuck spamming errors, therefore project needs to be reopened
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
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
- Group Node name text is way smaller in the renaming state than the actual display size
Resolution Note (fix version 6.0.X):
Fixes an issue where placing two vertices on the same edge with Cut Tool would throw a null reference exception.