3 ms·

The topological renumbering/renaming problem is THE killer bug that FreeCAD has got to fix. Until that bug is gone, FreeCAD has no future. Unfortunately, as I

by bsder 4y ago

The topological renumbering/renaming problem is THE killer bug that FreeCAD has got to fix. Until that bug is gone, FreeCAD has no future. Unfortunately, as I understand it, the only way to truly get rid of that is to entirely rewrite the geometry kernel. :(

mitthrowaway2 4y ago
It's been (mostly) solved in this dev branch: https://github.com/realthunder/FreeCAD/releases https://github.com/realthunder/FreeCAD/releases The team is working on a merge, but it's a big merge.
- app4soft 4y ago
  > It's been (mostly) solved in this dev branch To be clear, it is not a dev branch, but RealThunder's Link branch (FreeCADLink is a fork of FreeCAD). For topology naming, here is dev branch[0,1] [0] https://github.com/FreeCAD/FreeCAD/tree/development/toponaming https://github.com/FreeCAD/FreeCAD/tree/development/toponami... [1] https://github.com/FreeCAD/FreeCAD-Bundle/releases/tag/topo-naming https://github.com/FreeCAD/FreeCAD-Bundle/releases/tag/topo-...
bb88 4y ago
Yeah, that bug is killer. I use F360 now, mostly because I'd make one change and the topology changed, and it wasn't clear how to fix it always. Though the one feature I miss from Fusion 360 is the thread plugin. It's not perfect but the custom thread profiles were way more powerful than F360.
2muchcoffeeman 4y ago
I guess it will never rival F360 or any professional packages. But if you’re like me and designing relatively simple things for 3D printing, it’s perfectly capable. You just need to be made aware from the beginning and understand how to structure your project.
RobotToaster 4y ago
I hate to say it, but I'm doubtful anything based on openCASCADE will ever have much of a future, it seems to have a lot of fundamental problems. I'm surprised nothing has been done with the BRL-CAD kernel.

3 ms·

The topological renumbering/renaming problem is THE killer bug that FreeCAD has got to fix. Until that bug is gone, FreeCAD has no future. Unfortunately, as I

by bsder 4y ago

mitthrowaway2 4y ago
It's been (mostly) solved in this dev branch: https://github.com/realthunder/FreeCAD/releases https://github.com/realthunder/FreeCAD/releases The team is working on a merge, but it's a big merge.
- app4soft 4y ago
  > It's been (mostly) solved in this dev branch To be clear, it is not a dev branch, but RealThunder's Link branch (FreeCADLink is a fork of FreeCAD). For topology naming, here is dev branch[0,1] [0] https://github.com/FreeCAD/FreeCAD/tree/development/toponaming https://github.com/FreeCAD/FreeCAD/tree/development/toponami... [1] https://github.com/FreeCAD/FreeCAD-Bundle/releases/tag/topo-naming https://github.com/FreeCAD/FreeCAD-Bundle/releases/tag/topo-...
bb88 4y ago
Yeah, that bug is killer. I use F360 now, mostly because I'd make one change and the topology changed, and it wasn't clear how to fix it always. Though the one feature I miss from Fusion 360 is the thread plugin. It's not perfect but the custom thread profiles were way more powerful than F360.
2muchcoffeeman 4y ago
I guess it will never rival F360 or any professional packages. But if you’re like me and designing relatively simple things for 3D printing, it’s perfectly capable. You just need to be made aware from the beginning and understand how to structure your project.
RobotToaster 4y ago
I hate to say it, but I'm doubtful anything based on openCASCADE will ever have much of a future, it seems to have a lot of fundamental problems. I'm surprised nothing has been done with the BRL-CAD kernel.