Intersecting Holes (BOPAlgo_InvalidCurveOnSurface)
Forum rules
and Helpful information
and Helpful information
IMPORTANT: Please click here and read this first, before asking for help
Also, be nice to others! Read the FreeCAD code of conduct!
Also, be nice to others! Read the FreeCAD code of conduct!
Intersecting Holes (BOPAlgo_InvalidCurveOnSurface)
Hi,
does anyone know how to fix this issue? I have seen some posts about modifying the tolerances but I did not really understand them (maybe I was just looking at the wrong posts so far).
I have attached the example.
does anyone know how to fix this issue? I have seen some posts about modifying the tolerances but I did not really understand them (maybe I was just looking at the wrong posts so far).
I have attached the example.
- Attachments
-
- HoleInHole.FCStd
- (20.35 KiB) Downloaded 48 times
- papyblaise
- Veteran
- Posts: 7793
- Joined: Thu Jun 13, 2019 4:28 pm
- Location: France
Re: Intersecting Holes (BOPAlgo_InvalidCurveOnSurface)
what is the question
Re: Intersecting Holes (BOPAlgo_InvalidCurveOnSurface)
How to fix the BOPAlgo_InvalidCurveOnSurface issue.
- papyblaise
- Veteran
- Posts: 7793
- Joined: Thu Jun 13, 2019 4:28 pm
- Location: France
Re: Intersecting Holes (BOPAlgo_InvalidCurveOnSurface)
you need A , B or both
- Attachments
-
- B.PNG (21.23 KiB) Viewed 2717 times
-
- A.PNG (8.28 KiB) Viewed 2717 times
Re: Intersecting Holes (BOPAlgo_InvalidCurveOnSurface)
No issues or invalid geometry here.
Re: Intersecting Holes (BOPAlgo_InvalidCurveOnSurface)
Really no invalid geometry?
Part -> Check Geometry
----
OS: macOS 10.15
Word size of FreeCAD: 64-bit
Version: 0.20.26202 (Git)
Build type: Release
Branch: master
Hash: ca6d49d080dea0abc23d954743eca7c46f33469b
Python version: 3.9.7
Qt version: 5.12.9
Coin version: 4.0.0
OCC version: 7.5.3
Locale: C/Default (C)
Part -> Check Geometry
----
OS: macOS 10.15
Word size of FreeCAD: 64-bit
Version: 0.20.26202 (Git)
Build type: Release
Branch: master
Hash: ca6d49d080dea0abc23d954743eca7c46f33469b
Python version: 3.9.7
Qt version: 5.12.9
Coin version: 4.0.0
OCC version: 7.5.3
Locale: C/Default (C)
Re: Intersecting Holes (BOPAlgo_InvalidCurveOnSurface)
When I open the file there is only a single solid...with no history and the geo check produces the Invalid Curve messages.
No history = no fix, me thinks. Moral: never delete history. Or only delete history after making pre-delete copy of file.
No history = no fix, me thinks. Moral: never delete history. Or only delete history after making pre-delete copy of file.
Star Trek II: The Wrath of Khan: Spock: "...His pattern indicates two-dimensional thinking."
Re: Intersecting Holes (BOPAlgo_InvalidCurveOnSurface)
> When I open the file there is only a single solid...with no history and the geo check produces the Invalid Curve messages.
that's too easy to say, it happens with any intersected hole. I think a year ago I had a disastrous issue with intersected holes and freecad it destroyed the entire object.
It's very likely an OCCT issue (7.5.3 is used here).
However in that object it just complains about the invalid surface - so question is how to fix that when it has happened.
However for you attached you can find a file with a history (I just created it newly).
Refining and clearing the history is required for bigger projects at the moment with upstream FreeCAD due to BRP loading issues which happen when certain geometries are used (OCCT issue) but that's another topic.
that's too easy to say, it happens with any intersected hole. I think a year ago I had a disastrous issue with intersected holes and freecad it destroyed the entire object.
It's very likely an OCCT issue (7.5.3 is used here).
However in that object it just complains about the invalid surface - so question is how to fix that when it has happened.
However for you attached you can find a file with a history (I just created it newly).
Refining and clearing the history is required for bigger projects at the moment with upstream FreeCAD due to BRP loading issues which happen when certain geometries are used (OCCT issue) but that's another topic.
- Attachments
-
- intersectingHole2.FCStd
- (135.46 KiB) Downloaded 59 times
Re: Intersecting Holes (BOPAlgo_InvalidCurveOnSurface)
As I've said before, I don't think it is a particularly good workflow. But, again, that is a different topic.
But to the case in discussion..., when I create a similar model, the geo check seems to be ok on all 3 of the copy types I've created.
- Attachments
-
- intersectingHole-mac.FCStd
- (94.14 KiB) Downloaded 26 times
Star Trek II: The Wrath of Khan: Spock: "...His pattern indicates two-dimensional thinking."
Re: Intersecting Holes (BOPAlgo_InvalidCurveOnSurface)
keep working on the model a bit after refining and you'll be there.drmacro wrote: ↑Tue Nov 23, 2021 2:07 pmAs I've said before, I don't think it is a particularly good workflow. But, again, that is a different topic.
But to the case in discussion..., when I create a similar model, the geo check seems to be ok on all 3 of the copy types I've created.
Snip macro screenshot-434b89.png
It's no good workflow but upstream freecad cannot handle it better at the moment, other patches are needed. There's the FCStd too slow discussion in the forum which addresses the other issue.
And a little bit further it also needs investigation on the OCCT side (which is on my list at the moment and will happen once I have time for it).