I’ve used a variety of CAD and it just really didn’t click. I know it’s open source, so not going to be as UX oriented, but still.
I would love to be proved wrong. If there’s something I’m missing please share.
I’ve used a variety of CAD and it just really didn’t click. I know it’s open source, so not going to be as UX oriented, but still.
I would love to be proved wrong. If there’s something I’m missing please share.
I keep wishing that FreeCAD had the UI polish of Blender, and ask myself if Blender can do enough of the CAD workflows that it makes sense to learn Blender instead of FreeCAD.
I keep reading that technically speaking, mesh-based modelers are woefully insufficient for CAD tasks. But then I see videos like this, which suggest that Blender can handle most modeling tasks, with the main exception of bevels and chamfers: https://www.youtube.com/watch?v=n5SehCbhxFs
Can a lathe turn a polygon? Can a drill drill a polygonal hole? Maybe you can machine a polygon on a fancy CNC lathe, but you certainly wouldn’t do so for a turbine shaft.
Also for less precise things, say construction, you care about dimensions. Select an arc to get it’s radius for instance.
This is why design for traditional construction techniques best done in boundary representations: https://en.m.wikipedia.org/wiki/Boundary_representation
I will concede that one can easily create nasty insoluble problems with boundary representations if not familiar with the limitations of splines, but this only really is a problem with curvy things like ship’s hulls and aircraft.
However, I'm hunting for a better way to create 3d models via code (Blender Python?) because 'extrude_along_path'->SolidPython->OpenSCAD->stl export simply could not handle my model.
Also, as it's natively Python, you have all sorts of library support, up to and including things like numpy.
The future dream mCAD for me is something where extrusions and fillets and other 3d stuff is code, but sketches are GUI edited.
Without constraints, you're still doing a lot of stuff directly rather than declaratively, and without a GUI you're mostly limited to geometry you can imagine, because doing anything by trial and error in OpenSCAD takes forever.
The whole thing feels very open loop, like it's meant to be "imagine it>reason about it> code it" rather than "vauge idea > iteration > verify"
I could see it being useful in some cases for high level professional designers though.