Page MenuHome

BMesh booleans (track todo's)
Open, NormalPublic

Description

This is created to keep track of TODO's for BMesh booleans.


also test F240062 from T46269

Details

Type
To Do

Related Objects

StatusAssignedTask
OpenNone
OpenNone
OpenNone
ResolvedCampbell Barton (campbellbarton)
OpenCampbell Barton (campbellbarton)
InvalidCampbell Barton (campbellbarton)
OpenNone
ResolvedCampbell Barton (campbellbarton)
OpenCampbell Barton (campbellbarton)
OpenNone
OpenNone
OpenCampbell Barton (campbellbarton)
OpenNone
ArchivedCampbell Barton (campbellbarton)
DuplicatePhilipp Oeser (lichtwerk)
OpenCampbell Barton (campbellbarton)
OpenCampbell Barton (campbellbarton)
OpenCampbell Barton (campbellbarton)
OpenCampbell Barton (campbellbarton)
OpenHoward Trickey (howardt)
OpenNone
ResolvedCampbell Barton (campbellbarton)
OpenNone

Event Timeline

Attached is an example scene that hopefully will help with debugging. It is a portion of the seating to a Roman arena. The mesh closest to origin uses boolean modifiers, while the other mesh is for reference from 3ds Max with the same setup. Currently (2.77a) stair steps are missing and some boolOps completely fail.

As mentioned in T49923, to easily keep track of an another case ( the cylinders are just duplicated, rotated and joined).

Another easy to repro failing case (2.79):

Create a box, duplicate, move dup a bit along x axis and scale down along y axis, create bmesh boolean union -> fails.
Overlap threshold dosen't help.

From latest tests, adding a vertex colors layers on "hole" does fix issue on parent, the same goes for uvs (at least 1st layer, not checked further with 2nd one).

I can see. I told them very early few years ago and they ignore me as well until you can see happen about Boolean error.
I knew it.