Fillets are added to edges, edges can be formed both by a single feature (say an extruded 2d shape) or through the interaction of two or more other features (think of two extrusions 90deg to each other interacting and forming an edge). They can also link together or become unlinked via changes.
Referencing these edges, and keeping track of that reference through changes to the parameters is fundamental to parametric cad. It's one of the areas that OpenCascade struggles with.
A fillet breaking when a parameter update changes the topology is just a specific example of the topological naming problem. I don't think that's specific to OpenCascade. In fact, just thinking it through, I wouldn't be at all surprised if 2) above is the same thing: the fillet itself changes the object topology enough that the basis edges for the fillet get lost. If so that's a Freecad thing rather than an OpenCascade thing.
Maybe someone who's worked in that area can comment, it might be one of those things that gets better in 0.21.
I will follow up on the open-source idea when we start discussing the next vote.
Interesting, whats in it for them doing that? Also, considering JT which, as far as i know, is already an ISO standard?
Maybe it is intended as a marketing feature "Our exchange file is an ISO standard but the CATIA one is not".
Although BRL-CAD is powerful, it is still a collection of tools, not a solid application, which makes it pretty hard to use and to comprehend for a regular CAD user (designer). From their website:
BRL-CAD is a suite of more than 400 tools and utilities. The suite of applications are intentionally designed to perform a succinct task so that they can be chained together, scripted, and expanded upon in order to provide powerful flexibility.
I think someone has to develop a decent GUI for this package to make an alternative to FreeCAD.
Is there even open literature (books, papers, anything) for someone to understand what a modern kernel would look like?
I don’t doubt it would be a formidable challenge to develop one, but is the shape-of-it/api and interface of it well understood, or is this knowledge siloed away in a few companies?
Initially for one of the inner corners I had selected 2/3 edges for filleting. This caused fillet to bug out and some of vertices be position in completely wrong position far from where they should be resulting in visibly broken self intersection geometry in the are of that corner. Once I selected all 3 edges as asked in the drawing for exercise fillet was fine. But I don't see why it should have failed if the intention was to create model with 2/3 corner edges filleted. In other parts of model corners with such fillets worked fine.
Second problem was once I changed the angles and dimensions from phase 1 to phase 2. (I slightly cheated by not handling the bottom part properly but that's more of my failure read the drawing). After changing angle and dimensions fillets broke, and I had to reselect which edges are supposed to have them. (The topological naming problem). Which is slightly weird because the topology of model shouldn't have changed from those dimensions changes, but maybe there was a slight change in how boss intersects with bend, thus changing topology. In which case having to redo fillets is annoying, but slightly more understandable.
Third issue was that in the second phase it failed to solve fillets when radius was greater than 1.1mm (drawing asks for 2mm). Not sure why would it fail. I would understand if I asked something crazy like 10mm which would result in some degenerate geometry. But with 2mm it should still be sufficiently far from where it causes weird intersections. Again my best guess is the area with inner corner at the base of boss. There is short edge where outer cylinder of boss connects to bent corner instead of flat part.
This is false. See https://dev.opencascade.org/doc/overview/html/occt_user_guid...
Fundamentally the issue comes down to a complete lack of capable 3D Parametric CAD Kernels [0]. These are the Linux kernel to a Linux distribution. They are the central core that implements the fundamental geometric structures and operations.
The article comments on the difficulty with filleting (putting a radius on an edge), this is a fundamental operation any cad user would be doing many time a day.
FreeCAD is built on top of the OpenCascade [1] geometric kernel, it has a legacy back to the 80s like most kernels, and is by far the most capable open source kernel. However, it lacks stable support for may geometric operations, including filleting.
The only way we will see industrial level quality open source parametric CAD is with either a new modern kernel (I don't believe OpenCascade can be brought up to level), or if one of the other closed source kernels goes open source. A new kernel will be many 100s years of person work to produce.
OnSpace (mentioned in the article) uses the Parasolid Kernel [2], the same kernel used by SolidWorks and many other packages. If you want to build a commercial cad package it by far the best option.
0: https://en.m.wikipedia.org/wiki/Geometric_modeling_kernel
1: https://en.m.wikipedia.org/wiki/Open_Cascade_Technology
2: https://en.m.wikipedia.org/wiki/Parasolid