News for hackers. Stuff that matters.
Re:The first release candidate of FreeCAD 1.0 is out by throwgfgfd25 on Wednesday September 11, 2024 @05:36PM (#41515552)
UX work is ongoing.

Stability is good in the latest dev builds on the Mac, though 0.21.2 is the least crashy I've seen it.

But if you mean stability in terms of model stability/robustness when changing things, that's improved a lot with the topological naming mitigations.

It's still not perfect, and I still think FreeCAD is a lifestyle choice. But I enjoy working in it a lot more.

The Mango Jelly Solutions videos on Youtube are very, very worth a watch if you feel inclined to have another go; they have been the best thing for getting my mind into how FreeCAD works as a package (in the sense that it is a "package" at all -- it's really still a collection of overlapping, macro-programmable toolsets gathered around a kernel).

Re:The first release candidate of FreeCAD 1.0 is out by tpmoney on Wednesday September 11, 2024 @09:17PM (#41516727)
I want to second the recommendation for Mango Jelly Solutions videos. I've tried FreeCAD on and off for years and those videos are the first ones that finally helped me wrap my head around some things and be able to use it for a real project.
Re:The first release candidate of FreeCAD 1.0 is out by mort96 on Thursday September 12, 2024 @02:46AM (#41518194)
The thing I don't get is, it's over 20 years old. Surely if those th8ngs were ever going to improve they'd have done so over the past 20 years?
Re:The first release candidate of FreeCAD 1.0 is out by tecleandor on Thursday September 12, 2024 @04:08AM (#41518613)
Blender changed, FreeCAD can. Just the topology naming fix is a HUGE change that lots of people could have said a couple years ago that it would never be fixed.
Re:The first release candidate of FreeCAD 1.0 is out by throwgfgfd25 on Thursday September 12, 2024 @07:08AM (#41519479)
CAD is never made quickly, I think.

But FreeCAD was just not that sort of project. It's a C++ and Python wrapper around a CAD kernel, supporting a set of tools -- some frustrating tools, some quite powerful or niche, like the ThreadProfile workbench or the guitar workbench -- and it has never bothered the highly technical community of users much to unify things.

They weren't really trying to make a major competitor to commercial CAD: they were trying to have the tools that they individually needed and collaborate on the problems they had in common.

The balance has markedly shifted since 0.18 and now there is that focus, and significant commercial impetus. In the time I have used it -- about three years on and off -- it has clearly become more of a focus to make a complete product.

Re:The first release candidate of FreeCAD 1.0 is out by justinclift on Thursday September 12, 2024 @06:37PM (#41526360)
For anyone else wondering, TNP seems to mean "Topological naming problem":

https://wiki.freecad.org/Topological_naming_problem

Re:The first release candidate of FreeCAD 1.0 is out by throwgfgfd25 on Friday September 13, 2024 @07:21AM (#41530126)
Yes! Sorry. It's mentioned in the comments here but it should have occurred to me to expand on it.

TNP is really a research-grade problem that all CAD packages have to mitigate -- you can I think still run into issues that stem from face/vertex naming in all CAD packages if you really push them, and there are pathological cases where the solution is only to be consistent in arbitrary choices.

But mainline FreeCAD had no solution for this. A solid proof-of-concept implementation has existed in RealThunder's fork (which was originally used for Assembly 3 development) but since the solution touches an awful lot of the code it was never ported across and got increasingly difficult to port. There was reluctance to just switch wholesale to his fork because it contains some somewhat contentious developments, and it has taken some very deliberate, considered rethinking of the organisation of mainline FreeCAD releases to get the TNP code ported, which it now is.

There are still TNP issues, and there are still things one should not hope to rely on in FreeCAD -- like building on faces generated by chamfers, drafts or thicknesses.

I also think what risks being lost is the wisdom of sometimes deliberately choosing to build some features of a part from the base planes rather than a generated face; it reduces the complexity of dependencies and allows much freer re-working.