Boolean Exact and Self produce artifacts and wrong operation order with operand that has intersecting elements #81999

New Issue

Alex · 2020-10-23T11:43:21+02:00

Alex commented

2020-10-23 11:43:21 +02:00

System Information
Intel Core 2 Quad, 8 Gb RAM, NVidia GeForce GTX 960 2GB
Windows 7 x64

Blender Version
Broken: 2.91, 2.92
Worked: earlier version of 2.91

Short description of error
Opening a new report: Boolean Exact and Exact Self fails to properly handle operands that have intersecting geometry. This problem was introduced recently because earlier versions of 2.91 worked fine, I can't pinpoint when that happened but perhaps this problem was introduced with an Operand Type option.

Exact steps for others to reproduce the error

Open provided file and observe two cases – in the first case Boolean produces artifacts instead of subtraction and in the second case Boolean produces wrong operation order.

BooleanExactSelf_Artifacts_WrongOrder.blend

**System Information** Intel Core 2 Quad, 8 Gb RAM, NVidia GeForce GTX 960 2GB Windows 7 x64 **Blender Version** Broken: 2.91, 2.92 Worked: earlier version of 2.91 **Short description of error** Opening a new report: Boolean Exact and Exact Self fails to properly handle operands that have intersecting geometry. This problem was introduced recently because earlier versions of 2.91 worked fine, I can't pinpoint when that happened but perhaps this problem was introduced with an Operand Type option. **Exact steps for others to reproduce the error** 1. Open provided file and observe two cases – in the first case Boolean produces artifacts instead of subtraction and in the second case Boolean produces wrong operation order. ![New_Boolean_Wrong_Difference3.JPG](https://archive.blender.org/developer/F9047096/New_Boolean_Wrong_Difference3.JPG) [BooleanExactSelf_Artifacts_WrongOrder.blend](https://archive.blender.org/developer/F9047103/BooleanExactSelf_Artifacts_WrongOrder.blend)

Alex commented

2020-10-23 11:43:21 +02:00

Added subscriber: @SpectreFirst

Germano Cavalcante commented

2020-10-23 21:53:25 +02:00

Added subscribers: @howardt, @mano-wii

Germano Cavalcante commented

2020-10-23 21:53:25 +02:00

I can confirm that the result was different in a build from 2020-09-15

But even in it, I would not say that the result is correct.

And I'm not sure if the result with self is wrong. It is the same in both modes (Exact and Fast).

I can confirm that the result was different in a build from 2020-09-15 ![image.png](https://archive.blender.org/developer/F9055048/image.png) But even in it, I would not say that the result is correct. And I'm not sure if the result with self is wrong. It is the same in both modes (Exact and Fast).

Howard Trickey self-assigned this 2020-10-24 20:38:39 +02:00

Howard Trickey commented

2020-10-24 20:38:39 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Howard Trickey commented

2020-10-24 20:38:39 +02:00

Yes, I confirm that the Exact Self answer is not what it should be, and I will now work on fixing it.

The Exact (without Self) is kind of in "all bets are off" territory, so the fact that it gives a bad answer is not a bug.

Yes, I confirm that the Exact Self answer is not what it should be, and I will now work on fixing it. The Exact (without Self) is kind of in "all bets are off" territory, so the fact that it gives a bad answer is not a bug.

blender-admin commented

2020-10-24 23:36:38 +02:00

This issue was referenced by 1c653a0315

This issue was referenced by 1c653a0315b04269a2e7385efad6a033ddad2420

Howard Trickey commented

2020-10-24 23:40:47 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Howard Trickey closed this issue

2020-10-24 23:40:47 +02:00

Howard Trickey commented

2020-10-24 23:42:23 +02:00

I fixed this. Thanks for the nice simple example! Made debugging a lot easier than it might have been.