Search Issue Tracker
Fixed in 5.0.4
Votes
1
Found in [Package]
5.0.4
Issue ID
1389434
Regression
No
Editor crashes when using ProBuilders Boolean operations
Reproduction steps:
1. Open users attached project
2. Open Scenes/TestScene 1/TestScene scene
3. Press Tools > ProBuilder > Experimental > Boolean (CSG) Tool
4. Drag the Abandoned Building > Cube from the Hierarchy window to the left side of the Boolean window
5. Drag the Abandoned Building > Cube Substract from the Hierarchy window to the right side of the Boolean window
6. Set Operation to Subtraction in the Boolean window
7. Press Apply in the Boolean window
Expected result: Boolean operation completes successfully
Actual result: Editor crashes
Reproducible with: 4.5.2 (2020.3.24f1), 5.0.3 (2020.3.24f1, 2021.2.5f1), 5.0.4 (2022.1.0b1)
Could not test with: 2019.4.33f1 (could not downgrade the project)
Notes:
-Reproducible with both Windows and MacOS
-Editor crashes when doing any of the Boolean operations
-Editor crashes with no stack trace
Comments (2)
-
HunterAhlquist
Jun 20, 2022 21:24
Still having this issue with package version 4.5.2
-
ko-de
Apr 12, 2022 19:45
Boolean-Substraction keeps crashing with 5.0.4.
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
- "Browse" button for Xcode in the "Build Profiles" window is too big
- USS styles fail to inherit correctly when contentContainer is overridden in a custom control
- Copying and pasting Animator Transitions leads to unexpected behaviour
- "ShaderGraph" misses a space in the "Project Settings" section
- UI Builder inspector’s checkbox fields can be activated when clicking anywhere in the value field
Resolution Note (fix version 5.0.4):
The Fogbugz ticket says that this was discovered in ProBuilder 5.0.4, but the Editor logs are telling me that this project was running ProBuilder 5.0.3.
ProBuilder 5.0.4 contains a fix for a boolean operation crash. I was not able to reproduce the described crash in this ticket using 5.0.4, but 5.0.3 _did_ reproduce the issue.