Awesome work! It seems like a hard problem
Ondsel is also increasingly good. They've released a new version recently: https://ondsel.com/blog/ondsel-es-2024-2/
Their website login-wall downloads for whatever reason, so go to github: https://github.com/Ondsel-Development/FreeCAD/releases
I've got no qualms with anything Ondsel is doing, except that their "releases" are based off of the dev versions of FreeCAD, which are still in active development where things are rapidly changing and are poorly tested as a whole package. This leads to the situation where, for example, very basic sketches will cause the most recent Ondsel version to puke in odd ways, but it's a problem that's already been fixed in the FreeCAD dev builds.
So certainly give Ondsel a try; there a lot to like, and they're adding some much needed features to FreeCAD, but until their releases are based off FreeCAD stable, treat it like the unstable dev build it is.
I pretty much only use the Part Design, Sketcher and Spreadsheet workbenches. Those mostly work OK together. I don’t dare branch out because of poor interoperability between benches; I sometimes use the Part bench as well but it’s so fiddly because you had to take it through two internal format changes to make it work in Part Design.
Hoping that one of the many open source CAD projects can supplant it eventually.
I highly recommend the cadmium folks just soak themselves in onshape’s UX.
Well, what else can you expect from the very same guy who came up with SolidWorks in the 1990s? :)
To illustrate why... There's a certain "artistic" FOSS project (before you ask — not GIMP) where the community, incl. former lead dev basically say this:
- UX is bullshit, it's just opinions (verbatim quote)
- No two people agree on what is the right way, so anyone willing to improve UX in this project will have to fight everybody else, don't hold your hopes high (almost a verbatim quote)
- We don't like drama in this community, so we tend to just accept patches that change UI (you'd think this contradicts the previous statement, but somehow the impossible is possible)
They'd also mock a person who wrote a very elaborate first impressions blog post about the software, claiming she is an idiot who didn't bother learning the software.
I don't think the FreeCAD community was ever this bad, but there certainly was a strong element of chaos before. Things are considerably better today. There's a design working group working its way through various incosistencies, for one. It's a long-term project, no doubt about it, they are slowly getting there.
Another consideration for many is a good integrated CAM. This is where Autodesk Fusion, much as I dislike the company and the software, is unbeatable today.
My ask for a free CAD software would really be for someone to go through and take the robustness and speed of Creo and combine it with the user friendliness of Solidworks, even if it were to have a fairly limited feature-set to start.
1) Watch and do one tutorial that gets you 80% of the way there.
2) Try to stumble together the rest of the way.
3) Find out the fundamental tutorial doesn’t set up my project in a way that allows me to finish the 20%.
4) Watch the whole project fall apart as I try to modify one of the previous steps.
5) Repeat.
Does the order typical matter that much in CAD? I went all in on this thinking it was a simple object and how hard can FreeCAD be. Turns out, very hard.
The Mango Jelly Solutions videos, the Joko engineering videos, the Adventures In Creation videos and thehardwareguy's videos are excellent.
There is no doubt that understanding how to mitigate TNP is important, though. Many of the videos do not go into this each time (which will be good once the issue is mitigated, very soon, but is obviously an issue at the moment).
The fundamental issue I see with bad Youtube tutorials is people skipping from Part Design to other workbenches without understanding that they are not wholly interchangeable. That is, all Part Design Body objects are Parts, but not all Parts are Part Design Body objects. Part Design is a subset.
There is at least one excellent video by Mango Jelly Solutions going into the detail of why you should choose one over the other.
But the guts of it is that Part Design does have an ordered flow -- it's a sequence of steps from a simple to a complete object, executed one after the other and implicitly booleaned together. So it has additive features and subtractive features.
Whereas in a non-Part-Design workflow, you are in charge of when something is cut from something else; there's no subtractive tooling, only boolean tools. More CSG-ish.
A good grasp of FreeCAD involves understanding Part Design's relatively special guided flow, and that outside of it is a more open-ended approach.
The RealThunder developments to Part Design after TNP was fixed do go a long way towards making this less relevant (Part Design can work with multiple bodies rather than being focussed on a single body, and you can "wrap" non-Part-Design objects in a Part Design Body object more freely without using a macro). And that way you get to use Part Design much more like Fusion 360.
But there are definitely FreeCAD proponents who would say that Part Design is training wheels for what is really going on, and that there's no substitute for many general concepts inside Part Design. The latter is true; also the implicit booleans in Part Design make some of the PD operations slower.
Yes, it does matter. I discovered this through my own self learning with OpenSCAD, FreeCAD and OnShape. I actually prefer the workflow of FreeCAD to OnShape for a lot of tasks.
FreeCAD isn't that hard, cad isn't that hard. Especially for any developer with some level of XP in breaking down a complex problem domain into smaller composable parts.
I feel it’s similar to having learnt Photoshop (7) and then struggle to use GIMP. I keep looking for tools that aren’t there, expect panels to show certain details and they come up short.
It reinforces for me how valuable usability and interface design is for power user tools. But also, how important training materials are, and how loyal a user will be once they are accustomed to completing a workflow with their tool of choice.