USER FORUM
(you are viewing a thread; or go back to list of threads)
To phkahler - About Boolean fail with no boolean #907 (by Eustache Scram)
I don't have a GitHub account, then I try to give you some information from here ;)
I redraw the part - using solvespace 3.0~2e1f5324 (latest from notesalexp) on Debian Buster (chord tolerance : 0.01 ) - avoiding the vertical or horizontal axe to draw the fist slot ! See "Test.slvs" in the attached zip file
The problem you have (and I also have when I open your file) then disappear even if I change the distance between the copies or if I change the chord tolerance.
I also have nurbs problems that are solved using the same method : dontt draw the part to extrude on vertical or horizontal axes. See the file "Bug.slvs" in the attached zip file (you can change the angle in g004 tho see ...)
I redraw the part - using solvespace 3.0~2e1f5324 (latest from notesalexp) on Debian Buster (chord tolerance : 0.01 ) - avoiding the vertical or horizontal axe to draw the fist slot ! See "Test.slvs" in the attached zip file
The problem you have (and I also have when I open your file) then disappear even if I change the distance between the copies or if I change the chord tolerance.
I also have nurbs problems that are solved using the same method : dontt draw the part to extrude on vertical or horizontal axes. See the file "Bug.slvs" in the attached zip file (you can change the angle in g004 tho see ...)
(no subject) (by Paul)
Thanks for taking a look. I'll try some of your variations when I get a chance to look at it again.
I suspect there is more than one issue triggered by my sketch. There is probably something going on with the rotate group used to close the contour - we have at least one other NURBS issue involving a rotate group. But there must be something else going on as well, because the proximity of the copies should not change anything in that sketch, but it does.
I chose the orientation that way because it allows use of V and Y constraints, which simplifies the drawing a lot. Workarounds are short-term solutions and can also provide hints about what is going wrong, so thanks for the feedback.
OH BTW I strongly recommend not setting chord tolerance to 0.01 percent. That is going to reduce performance quite a bit compared to using the default 0.1 percent.
I suspect there is more than one issue triggered by my sketch. There is probably something going on with the rotate group used to close the contour - we have at least one other NURBS issue involving a rotate group. But there must be something else going on as well, because the proximity of the copies should not change anything in that sketch, but it does.
I chose the orientation that way because it allows use of V and Y constraints, which simplifies the drawing a lot. Workarounds are short-term solutions and can also provide hints about what is going wrong, so thanks for the feedback.
OH BTW I strongly recommend not setting chord tolerance to 0.01 percent. That is going to reduce performance quite a bit compared to using the default 0.1 percent.
Post a reply to this comment: