Search Issue Tracker
Won't Fix
Won't Fix in 6.0.X
Votes
0
Found in [Package]
5.2.3
6.0.4
Issue ID
PBLD-204
Regression
No
ProBuilder Boolean feature does not correctly subtract inner Mesh and causes artifacts when using a Cylinder Shape with modified Sides Count
Reproduction steps:
1. Open the attached "ProBuilderBoolean.zip" project
2. Go to Edit > Preferences > ProBuilder and enable "Experimental Features Enabled"
3. Go to Tools > ProBuilder > Experimental > Boolean Tool
4. Drag "Cylinder_2" GameObject in the first slot and "Cylinder_1" in the second slot
5. Change the Operation to Subtraction
6. Press Apply
7. Move the newly created GameObject in the Scene to the side for better viewing
8. Observe the Mesh
Expected result: The Mesh has a hole cut in the middle or where the smaller mesh object was located
Actual result: Visible graphical artifacts are visible and no hole is cut
Reproducible with: 5.2.0, 5.2.3 (2022.3.57f1), 6.0.4 (6000.0.36f1, 6000.1.0b4, 6000.2.0a1)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note:
- Could only reproduce when the ProBuilder Cylinder GameObject has modified “Sides Count” property value
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
- A frame spike occurs when Physics Simulation Mode is switched from Script to FixedUpdate
- "WebAssembly Language Features" Header in the Player Settings has a smaller indentation
- No audio is played when Playbable Mixer is changed at runtime
- Editor hangs when painting Details containing 2D Mesh on Terrain
- No audio is played when TimelinePlayable has one output
Resolution Note:
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration we will not be addressing your issue at this time, as this is a feature that has not left experimental status and we are currently committed to resolving other higher-priority Editor issues.
Resolution Note (6.0.X):
Thank you for bringing this issue to our attention. Unfortunately, after careful consideration we will not be addressing your issue at this time, as this is a feature that has not left experimental status and we are currently committed to resolving other higher-priority Editor issues.