![]() Please, notice that I use git version 0.r3069.ga7d297c-1 (from ) a newer version may behave much better. ![]() Things I miss most in Part/PartDesign workbenches is snapping. But then you loose parametric behaviour when changing some parameters in history. You can always make things better by copy/paste the last model (without history) into a new FreeCAD document. Here is an example of FreeCAD model which starts to be big with history (when its history is kept the file has 32MiB and is saving for about 10 seconds): When the history is kept then also not so big models can look big. It is not such a problem of the model itself as the fact that also the whole history how the model was built is kept. (I guess this is a common feature of big CADs.) It is good to save a lot (especially before deletions or changes in history) but saving gets really slow with bigger models. ![]() The way/history how your model was built is stored so if you need to modify some parameters in previous steps there is good chance you can change it in history and the later steps will rebuild appropriately. Some of the FreeCAD bugs/limitations are actually OpenCasCade bugs/limitations. If you know python you can work around the bugs (or detect that something is wrong) from the "python console". It is somewhat buggy so it can be hard to use if you do not know python. Here is an example of an OpenSCAD model which just starts to be more complicated:įreeCAD looks more like a real CAD. CGAL path will be ok with bigger models, but you cannot "debug" with it easily. The internal path gets very slow for more complicated models (about 5000 triangles, which corresponds to about 400 lines of OpenSCAD script). One is internal (debug) and the other is CGAL. It is good for simple things which need to be highlly parametric. You write a script which builds your part. OpenSCAD is more like a scripting language. ![]()
0 Comments
Leave a Reply. |