@kde@kde you can also use #FreeCAD to draw up your house or anything else parametrically, and then export as STL and use #blender to make a movie of it/with it.
Big #FreeCAD news! Feature freeze for FreeCAD 1.0 is now on. If you have held back from trying development builds, please consider running weekly development builds starting this week and filing clear bug reports. The may give you ideas what to expect and look for, but also lots of testing has been focused on explicitly new behavior, so just using the new version for general use (of course saving early and often!) is likely to uncover a few stray problems here and there that would be great to fix before the big 1.0. 😁
I'm not one of the FreeCAD developers (my sole code contribution so far has been fixing a tooltip typo, and I've contributed to a couple Workbench extensions), but if you, like me, were previously scared off by the "no bug reports not first discussed in the forum" rule, that rule is gone. FreeCAD now take normal GitHub bug reports and even have someone dedicated to triage. Bug reporting for FreeCAD is now a good experience!
The renaming and the conversion table system offer new possibilities: It's now possible to not only use default names like Edge4 or Face6, but also custom names like TopFace. Although this is not yet used by FreeCAD tools, it offers very interesting possibilities, where subcomponents could be referenced not by their order in a list, but by more meaningful characteristics. This might lead to very interesting developments in the future.
Right now, as far as I know, semantic toplogical naming has been the province of CadQuery, which, though very interesting, is explicitly code-based. Bringing semantic topological naming to #FreeCAD would be awesome!
An exciting milestone for upstream #FreeCAD integration of the TNP mitigations designed by Realthunder and debuted in his LinkStage3 fork: New bug reports against upstream reproduce current LinkStage3 topological naming behavior.
The main phases of the #FreeCAD Topological Naming Problem Mitigation Project are now complete: the PR activating the code was just merged and will appear in the latest Weekly Developer builds. https://forum.freecad.org/viewtopic.php?t=87791
A dubious idea I have about cutting curved dovetails so a box would look like an impossible dovetail box, but would in fact have the top open on an arc rather than a diagonal slide like most impossible dovetails.
The axis of rotation is the left corner, where there's a green line.
@smellsofbikes Addendum: Somewhat ironically, this was done in very latest #FreeCAD (as of a couple hours ago) with the TNP mitigations enabled (FC_USE_TNP_FIX defined), but this particular model is, I think, fully robust against topological ambiguity even without the mitigation, since I tried to define everything against fixed datums, nothing relative to geometrical elements.
How long has #FreeCAD had the TechDraw dimension repair tool? Have I been replacing instead of repairing dimensions for a long time needlessly? Will the TNP mitigations make it into TechDraw and make dimension repair infrequently needed?
I just spent an hour putting together a detailed bug report on a 100% repeatable SIGSEGV in a local build of #FreeCAD from a few hours ago, and before hitting submit, I pulled the latest code and rebuilt it.
I kind of love how people post that FreeCAD is unlearnable and unusable and then on the same page of my timeline are posts about amazing projects made with FreeCAD.
I'm not pointing fingers or drawing any conclusions other than it's a funny situation.
Use whatever software works for you.
@trevorflowers My impression is that the loudest complainers are people that have never used modern CAD and don’t understand the common methodologies across software. They don’t realize that some potential problems exist no matter what you use. I have the benefit of decades of CAD experience and learning from my mistakes to help me be proficient with #freecad. It’s a great tool getting better all the time.
I've finally built #FreeCAD for myself, with the TNP mitigation enabled. Now every time I see something cool in the @FreeCAD WIP Wednesday posts I can play with it without waiting for a new weekly build. ☺
Here's the 3d printed housing and battery contacts completed. Was visiting my daughter a few weeks back and knew she could get the housing printed so I quickly whipped up a design in #freecad and sent it over to her.
The battery contacts are 1mm thick brass plate that I cut and filed to the correct shape based on a cardboard template. They turned out pretty nice looking.
I decided to try building #FreeCAD from source. I used a F39 toolbox on my #Fedora 40 #Silverblue and installed the prereqs; most from packages, but pyside2 from pip (inside the toolbox) since it hasn't been packaged in Fedora for years. The segfault I'm getting from libshiboken isn't illuminating to me. I could imagine a missing dependency on a package causing a segfault, or maybe no one is building FreeCAD on Fedora and it just doesn't work on F39. 🤔
Not clear that I'm close enough to the beaten path for this to be worth a bug report, though. Quite likely PEBCAK...
Feeling relatively clear today so thought I'd get a few of the wife's requested prints designed but for some reason #FreeCAD just wouldn't start so went looking for alternatives and stumbled upon #dune3d and OMG what a banging new #CAD tool, it's a very fast core clearly built around keyboard shortcuts but has a lovely context menu you bring up with space and for designing simple parts has absolutely everything I need today. I am very impressed. #3dprinting#design#partdesign
I'm a novice on Lattice2, so I'd appreciate testing of all the functionality of the workbench both on recent development builds and on stable FreeCAD. I want to make sure that the fix is complete and correct on both stable and development versions before suggesting that it is ready to merge.
If you use git to install workbenches, you can do something like this if you want to test and help:
cd .local/share/FreeCAD/Mod/lattice2<br></br>git remote add johnsonm git@github.com:johnsonm/Lattice2.git<br></br>git fetch johnsonm<br></br>git checkout johnsonm/mkj-attachment-support<br></br>
Feel free to comment on the pull request itself or here, I'll see it either way.