Categories:
-
3d 96 articles
-
animations 16 articles
-
architecture 47 articles
-
blender 98 articles
-
bédé 19 articles
-
techdrawing 24 articles
-
freecad 189 articles
-
gaming 1 articles
-
idsampa 8 articles
-
inthepress 8 articles
-
linux 57 articles
-
music 1 articles
-
nativeifc 30 articles
-
opensource 266 articles
-
orange 4 articles
-
photo 16 articles
-
projects 35 articles
-
receitas 176 articles
-
saopaulo 18 articles
-
sketches 163 articles
-
talks 25 articles
-
techdrawing 24 articles
-
textes 7 articles
-
trilhas 3 articles
-
urbanoids 1 articles
-
video 47 articles
-
webdesign 7 articles
-
works 151 articles
Archives:
-
2007 22 articles
-
2008 32 articles
-
2009 66 articles
-
2010 74 articles
-
2011 74 articles
-
2012 47 articles
-
2013 31 articles
-
2014 38 articles
-
2015 28 articles
-
2016 36 articles
-
2017 41 articles
-
2018 46 articles
-
2019 59 articles
-
2020 18 articles
-
2021 20 articles
-
2022 7 articles
-
2023 25 articles
-
2024 14 articles
A bit of FreeCAD BIM work
This afternoon I did some BIM work in FreeCAD for a house project I'm doing with Ryan. We're using this as a test platform for IFC roundtripping between Revit and FreeCAD. So far the results are mixed, lots of information get lost on the way obviously, but on the other hand I'm secretly pretty happy to see FreeCAD capable of communicating fluently with Revit already.
We already identified many bottlenecks, a major one being how FreeCAD imports IFC files, it basically transforms everything into dumb solids, which, when exported back to IFC, become faceted Breps, which Revit treats as non-editable. FreeCAD's native Arch objects, on the other hand, are in most case built of standard extrusions, and therefore stay editable in Revit. Thomas from ifcopenshell, which is the IFC importer/exporter we use in FreeCAD, is also thinking about the problem, no doubt we'll come with a solution any day soon.
In the meantime, modeling directly in FreeCAD, although slow (way slower than I would do in Blender), is already pretty reliable (not a single crash, everything nicely undoable, modifiable, fixable, etc) and enjoyable (fairly easy to look at your model the way you want to see it). It's not something I do often, I prefer the speed of Blender to raise the geometry, then I use FreeCAD to turn it into serious stuff, but here I specifically wanted to use the native Arch objects.
The speed of the workflow is of course a delicate matter, that can't be solved overnight, but now that we reached a certain maturity and stability with the Arch module, it'll be the time to begin to study more efficient ways to use it.