Archived issue #0033482
Modeling Algorithms - Bad result with BRepAlgoAPI_Common
Description
Hi !
BRepAlgoAPI_Common can give no result although there is clearly a big common part between 2 shapes (see attached picture)
BRepAlgoAPI_Common can give no result although there is clearly a big common part between 2 shapes (see attached picture)
Steps to reproduce
You can use Tool and Argument joined in "NotAttachment 1 (ZIP)"
Additional information
A very slight transformation in Z of one shape give the right result. You can check with Argument and Tool in "Attachment 1 (ZIP)".
It looks like the result is bad when the shapes are perfectly aligned in Z (see picture).
It seems that "curves" value in myDS can be wrong.
Behaviour between good case and bad case is different in getBoundPaves (hierarchy is PutBoundPaveOnCurve / MakeBlocks / ... / IntersectShapes) : vertex and point compared are sometimes too different.
It looks like the result is bad when the shapes are perfectly aligned in Z (see picture).
It seems that "curves" value in myDS can be wrong.
Behaviour between good case and bad case is different in getBoundPaves (hierarchy is PutBoundPaveOnCurve / MakeBlocks / ... / IntersectShapes) : vertex and point compared are sometimes too different.
Public activity
5 archived notes
Participants are labeled by their role within this record.
Dear Commenter 2. current problem can be solved by decreasing the tolerance for boolean operation (to 0.00001).
If it is not your case, we can continue investigate this problem.
If it is not your case, we can continue investigate this problem.
Dear Commenter 3, thanks a lot for your help. Indeed, this can be fixed by setting the tolerance to 0.00001 but it doesn't work with tolerance = 0 or tolerance = 0.0000001. The common part is big and I think it shouldn't depend on the tolerance. Maybe there's a "global" fix ?
Reminder sent to: Commenter 1
Hi Commenter 3, did you have time to check this issue and why a small change in the tolerance has a so big impact (and leads to wrong result) ?
Hi Commenter 3, did you have time to check this issue and why a small change in the tolerance has a so big impact (and leads to wrong result) ?
Hi, is there any update for this issue please ?
Merged into [archived branch], repository: archived repository reference
[revision removed]
Branch: archived repository reference
[revision removed]
Branch: archived repository reference
Related records