Archived issue #0032510
Problems with BRepAlgoAPI_Fuse when uniting multiple bodies
Description
Please refer detailed description, sample STEP files and images at my post on the forum:
https://dev.opencascade.org/content/problems-brepalgoapifuse-when-uniting-multiple-bodies#comment-22308
https://dev.opencascade.org/content/problems-brepalgoapifuse-when-uniting-multiple-bodies#comment-22308
Steps to reproduce
1. Create 4 cylinders along body diagonals of a cube using BRepPrimAPI_MakeCylinder
2. Create a sphere at center of cube BRepPrimAPI_MakeSphere
3. Try to fuse them all together in any combination by appending them in TopTools_ListOfShape arguments and TopTools_ListOfShape lists. Create union using BRepAlgoAPI_Fuse.
4. Write the fused STEP file using STEPControl_Writer
5. Open it in a STEP file CAD viewer software like FreeCAD, NX or something else.
6. You can see the union is totally gibberish and weird.
In place of step 1, you can also try the following: open the cylinder and sphere files I have attached in the forum post, read them using OCCT STEP file Reader and use the extracted TopoDS_Shapes instead for the following steps.
2. Create a sphere at center of cube BRepPrimAPI_MakeSphere
3. Try to fuse them all together in any combination by appending them in TopTools_ListOfShape arguments and TopTools_ListOfShape lists. Create union using BRepAlgoAPI_Fuse.
4. Write the fused STEP file using STEPControl_Writer
5. Open it in a STEP file CAD viewer software like FreeCAD, NX or something else.
6. You can see the union is totally gibberish and weird.
In place of step 1, you can also try the following: open the cylinder and sphere files I have attached in the forum post, read them using OCCT STEP file Reader and use the extracted TopoDS_Shapes instead for the following steps.
Additional information
Boolean operations typically always give issues.
Public activity
7 archived notes
Participants are labeled by their role within this record.
Don't know the right person in OCCT to assign to, since Eugene Zaliznyak expressed interest on my forum post, I have assigned to them. You can change it to whoever is the best person as per your system.
> Don't know the right person in OCCT to assign to
Mantis suggests a default assignee person based on selected Category (which should be msv in case of [OCCT] OCCT:Modeling Algorithms).
It is better do not change this field during bug creation to avoid maintainer of the Component accidentally missing new bug - and change it after creation if needed.
Mantis suggests a default assignee person based on selected Category (which should be msv in case of [OCCT] OCCT:Modeling Algorithms).
It is better do not change this field during bug creation to avoid maintainer of the Component accidentally missing new bug - and change it after creation if needed.
Please also specify "Product Version" with the OCCT version, where problem has been reproduced.
Sure, thanks for the note KGV. The OCCT version is:
opencascade: stable 7.5.1 (bottled)
I got this output from running "brew info opencascade" on Mac terminal
What do you mean by "Product version"? How can I check that?
opencascade: stable 7.5.1 (bottled)
I got this output from running "brew info opencascade" on Mac terminal
What do you mean by "Product version"? How can I check that?
> What do you mean by "Product version"? How can I check that?
This is a field in Mantis to fill in.
This is a field in Mantis to fill in.
Hi KGV, I don't see an option to edit the bug submission so that I can fill in product version. I have still not understand what product's version does "product version" refer to? I know OCCT version but not sure what do you mean by "product" here. Can you give an example?
> I have still not understand what product's version does "product version" refer to?
> I know OCCT version but not sure what do you mean by "product" here
"Product Version" is an input field in Mantis within Issue details, and corresponds to OCCT version (there is a list of known versions).
It should appear at bug creation time and should be editable after registration.
If not - then I guess there might be some Mantis configuration issues for a user with "reporter" role.
> I know OCCT version but not sure what do you mean by "product" here
"Product Version" is an input field in Mantis within Issue details, and corresponds to OCCT version (there is a list of known versions).
It should appear at bug creation time and should be editable after registration.
If not - then I guess there might be some Mantis configuration issues for a user with "reporter" role.