Bool tool slice does not always give correct slicing result. #108953

Closed
opened 2023-06-14 00:07:27 +02:00 by anson-liu · 3 comments

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41

Blender Version
Broken: version: 2.93.18, branch: master, commit date: 2023-05-22 12:04, hash: cb886aba06d5.
Broken: version: 3.5.1
Worked: version: 2.90.1, branch: master, commit date: 2020-09-23 06:43, hash: rB3e85bb34d0d7

Short description of error
Boolean slicing does not work correctly after Blender version 2.90.1. The slice which is a boolean difference that keeps both sides of the boolean is triggered through the Blender included Bool Tool addon and the bool tool addon code has not had any real changes since 2020-09-23 the date of last working Blender version 2.90.1 commit.

The "slice" code in the Bool Tool addon is at object_boolean_tools.py#L504 and does not appear to have any implementation changes since 2020 so I think Blender 2.93.18 and later had a breaking change in how boolean intersection and differences are handled. The addon calls a boolean difference and a boolean intersect operation. Based on the behavior and screenshot below, I think the Blender returned objects from difference and intersect have changed since 2.90.1.

The incorrect slice operation example is in the screenshot below. Slicing with a curve that was converted to a mesh results in one side of the sliced object staying and the other half turning into a thin intersection piece with the mesh. No UI console errors are shown.

incorrect

The correct result that works in Blender v2.90.1 is in the screenshot below. The slice operation outputs two objects which are the two sides of the sliced object.

correct

Exact steps for others to reproduce the error

  1. Enable Bool Tool addon
  2. Add a path, move it into place to bisect the object, extrude it, convert it to mesh
  3. Select path that is now a mesh
  4. Shift select the object to be sliced in the 3d view
  5. Use bool tool Slice under right sidebar > Edit >Bool Tool > Auto Boolean> Slice
  6. Wait a few seconds and see result of the slice if it is two sides of the sliced object (or not)

I have attached a test case blend file in 7z archive with a curve and converted mesh and test object to slice that succeeds in Blender 2.90.1 but not 2.93.18 or 3.5.1

I previously made a bug report on the blender addon repo blender/blender-addons#104690 but since the addon itself seems stable and has not changed since 2020, I thought making a bug report in the blender repo may more relevant. Thanks.

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41 **Blender Version** Broken: version: 2.93.18, branch: master, commit date: 2023-05-22 12:04, hash: `cb886aba06d5`. Broken: version: 3.5.1 Worked: version: 2.90.1, branch: master, commit date: 2020-09-23 06:43, hash: `rB3e85bb34d0d7` **Short description of error** Boolean slicing does not work correctly after Blender version 2.90.1. The slice which is a boolean difference that keeps both sides of the boolean is triggered through the Blender included Bool Tool addon and the bool tool addon code has not had any real changes since 2020-09-23 the date of last working Blender version 2.90.1 commit. The "slice" code in the Bool Tool addon is at [object_boolean_tools.py#L504](https://github.com/blender/blender-addons/blob/main/object_boolean_tools.py#L504) and does not appear to have any implementation changes since 2020 so I think Blender 2.93.18 and later had a breaking change in how boolean intersection and differences are handled. The addon calls a boolean difference and a boolean intersect operation. Based on the behavior and screenshot below, I think the Blender returned objects from difference and intersect have changed since 2.90.1. The incorrect slice operation example is in the screenshot below. Slicing with a curve that was converted to a mesh results in one side of the sliced object staying and the other half turning into a thin intersection piece with the mesh. No UI console errors are shown. ![incorrect](/attachments/51f7935a-7973-47f6-8331-bd8dfa87b500) The correct result that works in Blender v2.90.1 is in the screenshot below. The slice operation outputs two objects which are the two sides of the sliced object. ![correct](/attachments/f08aea8a-0fbc-445d-ade3-3d66567e8c2d) **Exact steps for others to reproduce the error** 1. Enable Bool Tool addon 2. Add a path, move it into place to bisect the object, extrude it, convert it to mesh 3. Select path that is now a mesh 4. Shift select the object to be sliced in the 3d view 5. Use bool tool Slice under right sidebar > Edit >Bool Tool > Auto Boolean> Slice 6. Wait a few seconds and see result of the slice if it is two sides of the sliced object (or not) I have attached a test case blend file in 7z archive with a curve and converted mesh and test object to slice that succeeds in Blender 2.90.1 but not 2.93.18 or 3.5.1 I previously made a bug report on the blender addon repo https://projects.blender.org/blender/blender-addons/issues/104690 but since the addon itself seems stable and has not changed since 2020, I thought making a bug report in the blender repo may more relevant. Thanks.
anson-liu added the
Type
Report
Status
Needs Triage
Priority
Normal
labels 2023-06-14 00:07:28 +02:00
YimingWu added the
Interest
Modeling
label 2023-06-14 04:38:25 +02:00
YimingWu changed title from Blender 2.93.18 thru 3.5.1 do not have correct boolean result to Bool tool slice does not delete the other side of the object. 2023-06-14 04:45:30 +02:00
Member

It's very likely introduced by the "Exact" boolean solver, which causes more problem than legacy "Fast" solver. Use "Brush Boolean > Slice" and change the resulting boolean modifier to "Fast" solves the problem. I'd say this is a known issue with boolean.

Fast Exact
图片 图片

Also tagging #106703 due to an icon confusion.

It's very likely introduced by the "Exact" boolean solver, which causes more problem than legacy "Fast" solver. Use "Brush Boolean > Slice" and change the resulting boolean modifier to "Fast" solves the problem. I'd say this is a known issue with boolean. | Fast | Exact | |---|---| | ![图片](/attachments/176e0609-62a1-4c57-a3d1-15fe8a451ea0) | ![图片](/attachments/a37533a3-8846-48f0-a734-2f4cf9ff8abb) | Also tagging #106703 due to an icon confusion.
YimingWu added
Module
Modeling
Status
Needs Info from Developers
and removed
Status
Needs Triage
labels 2023-06-14 04:55:59 +02:00
YimingWu changed title from Bool tool slice does not delete the other side of the object. to Bool tool slice does not always give correct slicing result. 2023-06-14 04:57:06 +02:00
Author

@ChengduLittleA Thanks, changing boolean from Exact to Fast solves the issue.
Now that I know how Bool Tool works, I'm confused how the first boolean intersection and difference operations with Fast mode keep the first and second halves of the object. Is this an unintended side effect of Fast mode?

I thought a boolean intersection should rightfully output the sliver of the model that the path passes thru and the boolean difference should output the model "cut" in two with a thin void where the path passes thru?

For anyone else out there using Bool Tool, you are better off manually adding the boolean modifiers done by Bool Tool due to the boolean defaulting to Exact instead of Fast causing long processing times for large models.
The steps to do the slice manually are:

  1. Create a copy of the object you want to slice
  2. Add a boolean intersection modifier on the first copy of the sliced object
  3. Set the boolean type to Intersection and method to Fast
  4. Set boolean cut object to your cutting path
  5. Add a boolean intersection modifier on the second copy of the sliced object
  6. Set the boolean type to Difference and method to Fast
  7. Set boolean cut object to your cutting path
@ChengduLittleA Thanks, changing boolean from Exact to Fast solves the issue. Now that I know how Bool Tool works, I'm confused how the first boolean intersection and difference operations with Fast mode keep the first and second halves of the object. Is this an unintended side effect of Fast mode? I thought a boolean intersection should rightfully output the sliver of the model that the path passes thru and the boolean difference should output the model "cut" in two with a thin void where the path passes thru? For anyone else out there using Bool Tool, you are better off manually adding the boolean modifiers done by Bool Tool due to the boolean defaulting to Exact instead of Fast causing long processing times for large models. The steps to do the slice manually are: 1. Create a copy of the object you want to slice 2. Add a boolean intersection modifier on the first copy of the sliced object 3. Set the boolean type to Intersection and method to Fast 4. Set boolean cut object to your cutting path 5. Add a boolean intersection modifier on the second copy of the sliced object 6. Set the boolean type to Difference and method to Fast 7. Set boolean cut object to your cutting path
Member

@anson-liu , that's just the inherit problem of the algorithm itself. In my understanding, "exact" mode converts position into integral values and in that process, you might get vertices that line up perfectly and lead to ambiguity of the representation of the hull, which then affects the output mesh. Ultimately there are better solutions available from recent year's research but they are not implemented into blender just yet.

Thanks for the advice for cutting using boolean :)

Will close this and mark it as a known issue.

@anson-liu , that's just the inherit problem of the algorithm itself. In my understanding, "exact" mode converts position into integral values and in that process, you might get vertices that line up perfectly and lead to ambiguity of the representation of the hull, which then affects the output mesh. Ultimately there _are_ better solutions available from recent year's research but they are not implemented into blender just yet. Thanks for the advice for cutting using boolean :) Will close this and mark it as a known issue.
Blender Bot added
Status
Archived
and removed
Status
Needs Info from Developers
labels 2023-06-24 04:25:00 +02:00
YimingWu added
Type
Known Issue
and removed
Type
Report
labels 2023-06-24 04:25:07 +02:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#108953
No description provided.