63
Exploring the available CAD software
(faulty.equipment)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Sep 2023
63 points (100.0% liked)
3DPrinting
15277 readers
182 users here now
3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.
The r/functionalprint community is now located at: !functionalprint@kbin.social or !functionalprint@fedia.io
There are CAD communities available at: !cad@lemmy.world or !freecad@lemmy.ml
Rules
-
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia. Code of Conduct.
-
Be respectful, especially when disagreeing. Everyone should feel welcome here.
-
No porn (NSFW prints are acceptable but must be marked NSFW)
-
No Ads / Spamming / Guerrilla Marketing
-
Do not create links to reddit
-
If you see an issue please flag it
-
No guns
-
No injury gore posts
If you need an easy way to host pictures, https://catbox.moe may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is 
Moderation policy: Light, mostly invisible
founded 1 year ago
MODERATORS
I really don't understand FreeCAD. I have used SolidWorks, Inventor, Fusion360 and OnShape for personal use and we use Siemens NX at work. I'm not an expert at any of them, but I get the job done. My colleagues and I often joke how unwieldy, slow and difficult NX is, but it's nothing compared to FreeCAD. It's just so different and unintuitive.
Even when applying good design practices when creating your models, everything will collapse into a giant mess once you try and change/remove an earlier feature. Or possibly I am taking a wrong approach since it's so different.
The FreeCAD devs know this, and criticisms about how it's so different from other CAD programs isn't allowed on their forums (I understand their reasoning for this rule though). I really just don't understand why the devs of the only free open source CAD program feel the need to do everything so different than anything else that's out there. It's not even like they need to find their niche to fill, it would be wildly more popular if it was more in line with commercial CAD programs.
I can't remember ever reading about someone liking the program but I often read people struggling with and complaining about it.
In my limited experience that's true in solidworks too, because every feature is built on the last one. So if you want to modify a feature that's halfway up the hierarchy, you make a new feature to do it instead. That way it doesn't break the model and you also preserve the design history of the part.
That's the accepted and expected behavior, because preserving design history is important.
I don't agree with you and this is pretty much frowned upon at the company I work at. As long as you follow good design principles, minor changes to features would trickle down without much issue. Sometimes things indeed break but they shouldn't be too hard to solve. It's not a good habit to keep adding, changing and removing bits to the same area with new features as if you are carving a statue; the history will become unmanageable at some point. Especially in a professional setting where someone else might need to work on your design it would make sense to have a logical build up of your model. For a hobbyist this doesn't matter that much and I can see how your argument for preserving history makes sense to you.
But an example of my frustration: With most CAD programs, sketches are usually put on faces and if you make a change elsewhere, the sketch will still be attached to that same face. With FreeCad, sketches seem to be assigned to a face number. This means that if you make a change earlier in the model that adds or removes a different face, your sketch will no longer be attached to the same face it was before because it has a different identifier. At least that's my experience, but maybe I was doing wrong. It's certainly not as I expected it to work.
This is the topological naming problem and should be solved in an upcoming version pretty soon (within a few months hopefully)