Hi, this is my blog, and also a guestbook. I publish stuff I do from time to time. Be welcome and feel at home, have a coffee and don't hesitate to drop me a line or two. All languages are highly welcome, especially the most exotic ones (nederlands, bij voorbeeld...).

Also, get me on twitter, facebook or google+.

Already 106 messages this year, showing only last 50. Click here to show all, or browse by tag: sketches, freecad, opensource, talks, trilhas, linux, works, architecture, projects, 3d, blender, detail, inthepress, animations, opensurce, firefoxos, bede, idsampa, photo, gaming, wordpress, webdesign, Architecture, orange, cooking, or search the 2017, 2016, 2015, 2014, 2013, 2012, 2011, 2010, 2009, 2008, .

First and foremost, your name:

And your message:

To publish it, just press this ...

permalink:  542   posted on 12.10.2018 12:14
From lukas alberts
Commenting post 275: Hi Yorick,
where can I see more of Electrical-planing with Freecad?
is it the BIM ready..means the e-plug is a ifc from some company or a exchangeable selfmade one. even the e-cable is ifc?
I need to go seriously into the design with FreeCAd. Looks like it is not long away to a professionel tool. Thanks for that.

permalink:  541   posted on 11.10.2018 18:07
From Patrick Depoix
A propos de tes aquarelles, félicitation Yorik, elles sont très charmantes.... et intéressantes architecturalement parlant. Je m'y adonne aussi le plus possible quand je voyage...A+ Patrick.

permalink:  540   posted on 11.10.2018 17:54
From Patrick Depoix
Commenting post 536: >>>By using reference files (I'm not sure the name is really good... Any other idea?) in FreeCAD
Yes Yorik, the stndard name is "assets", I mean, not?

permalink:  539   posted on 10.10.2018 16:10
From Olukwenda
Hi. I am just a fan who just wanted to say hi

permalink:  538   posted on 03.10.2018 18:09
From Yorik
Commenting post 537: Hi Rafael,
Very useful feedback, thanks!! I could indeed do a longer one from time to time...

permalink:  537   posted on 02.10.2018 17:59
From Rafael (bitacovir)
Commenting post 536: Great work Yorik. I just wanted to give my opinion about this 35min video. I do not think it was too long. In fact, I found very useful because I learned a lot seen a clear and correct workflow with BIM WB. All these tips, recommendations and explanations at each step showed that FreeCAD is a comfortable and comprehensible software to perform a BIM project. Many small but useful things that I didn't know. I think you can alternate short videos showing independent features with 30min videos showing these continuous workflows.

in categories  freecad  opensource  permalink:  536   posted on 02.10.2018 2:00
From Yorik

FreeCAD BIM development news - September 2018

Hi folks,

Time for one more of our monthly posts about the development of BIM tools for FreeCAD. This month unfortunately, since I was taking some holiday, travelling (and sketching) for the biggest part of the month, I have less new stuff than usual to show. To compensate, I tried a longer and more detailed video. Looking back at it, I think this is a bit too long, though, so next time I'll get back to a shorter format.

As usual, many thanks to everybody who is backing me up on Patreon, Liberapay, or donated directly to my Paypal account, this is a really amazing experience, I hope you guys feel as thrilled as I do about the progresses we're doing here, each month we have a new layer of paint on the wall, and it begins to form a very solid and coherent compound. I sincerely think some parts of the job are now almost done (basically, BIM modelling itself) and already work as well or even better than many commercial BIM applications. What I am going to concentrate more and more on, in the next months, is the 2D output, ie. how to generate good quality drawings from our BIM models.

I have several threads to explore there, one being of course TechDraw, where we need to optimize things to be able to work with larger models, and integrate better the native TechDraw tools with BIM models, and another thread is the 3D view itself, in order to obtain a more "WYSIWYG" (What You See Is What You Get) workflow, that is, have the 3D view really give you good and useful 2D views of your model. Finally, see how we can tie both these threads. Our OpenInventor-based 3D view has several tools for offline rendering, that is, produce a "copy" of the 3D view that can be used for other purposes, such as saving an image. This could offer us a blind-fast way to generate 2D documents, and could be a very interesting path to explore too.

The video

This month the video is a generic tutorial that shows how to get started with BIM modelling in FreeCAD:

BIM workbench documentation

I've also started working on the documentation of the BIM workbench. As you know, the main effort behind the BIM workbench is to offer a good user experience. This is therefore a very important point. There is still some work to do, but it is there already and usable. It is also something I wanted to do to advocate other Addon workbench developers to use the FreeCAD wiki to write their documentation. The new Start workbench, that has landed in FreeCAD last month, will display links to specific workbench pages on the wiki, so this would be very useful.

past development news articles on github

I also gathered all the development news articles I wrote so far on the github page of the BIM workbench, inside the "wiki" section. Some might find them easier to find and read there than on my blog...

External references

The big, new feature that has landed this month in Arch (and therefore BIM) workbench is the new [External Reference] tool. It basically works like an Xref in AutoCAD, or File Link in Revit (I'm not sure how it's called in other apps...). To resume, it allows to include the contents of one file in another. If the contents of the first file change, what's included in the second file changes too.

Working with reference files has a lot of advantages: One person can work on a part of a model, while others can work on other parts, and everyone can keep working on a separate file. Or you can split big files into smaller, more manageable chunks.

In FreeCAD, it has also a big extra advantage: Like in most parametric modellers, having a lot of individual objects in your model document makes FreeCAD run significantly slower. The 3D view of FreeCAD is capable of rendering several millions of faces without much slowdown (yes we tested), and the OpenCasCade engine is actually very efficient at managing very complex geometry. The problem is the logic. Each new document object created inserts a load of relationships with other parts of FreeCAD, because there are many mechanisms that must run every time you touch an object. Often, these mechanisms need to scan all the objects of the model.

It is interesting to compare this with games. A couple of years ago, the biggest part of the CPU computing occuring when you were playing a modern, resource-intensive game, was to compute the 3D graphics. Now, in some recent games like Kingdom Come (my favourite of the moment), the Artificial Intelligence uses more computing power than the 3D rendering! This is because each character in the game has its own "program" running, all interacting with each other, creating exponentially long chains of computation. Basically the same happens in FreeCAD. Such is the price of parametricism, that you'll have to pay one day, mister Schumacher! (Architects joke, don't worry about it)

By using reference files (I'm not sure the name is really good... Any other idea?) in FreeCAD, you can include the whole content of one file (several objects) as one object in the host file. This reduces dramatically computing time, and allow us to work with increasingly bigger models.

When you create a reference object, you give it a path to another FreeCAD file, then you can choose one of the included shape-based objects inside the file. The implementation is very simple: The Reference object doesn't open the included file. It just unzips the stored brep data of the object you specified. Any object with a shapecan be included, including, and that's the interesting point, BuildingParts. As I explained last month, internally, the BuildingPart always keeps a shape that is a compound of all the shapes of its children. Compound shapes in FreeCAD are very cheap and fast to produce (no boolean operation involved). So you can group anything you want, a whole storey, a whole building, etc... inside a BuildingPart, then include that BuildingPart as one single object inside another model.

The referenced object is a fully valid shape object, that you can move, rotate, duplicate, clone, project in 2D, and snap to it like any other. At the moment, it will be exported to IFC as one monolithic IfcBuildingElementProxy object, that's something to work further on in the future.

If you follow FreeCAD's latest developments, you might be asking yourself why this was not based on Realthunder's Assembly3 branch, which provides about the same functionality? There are a couple of reasons to that, basically because I wanted to try a very simple implementation, while his is rather complex, and also the aim is different: The Assemby3 functionality aims at pretty complex models, with not so much geometry, but with complex hierarchies and relationships. In BIM, we are aiming at very large models with very little or no relationships at all between the included parts. In any case it can certainly be interesting to have both approaches in FreeCAD.

Further immediate development will be the retrieval of colors. At the moment only the shape of included objects is gathered by the reference tool, we need to make the BuildingPart store not only the shapes of its children, but also the face colors, like the Part Compound does. Then we can read that as well when we include an object from another file.

Next, I'll also add an option to have the BuildingPart also store an OpenInventor representation. This will allow us to load only that representation from the included file, not the shape itself. This "lightweight include" would give blind-fast imports, and would have virtually no limit in terms of model complexity. There are a couple of caveats to solve, that I already experimented with the "Hi-Res" mode of Arch objects (snapping and selecting and everything else based on element names doesn't work correctly), which is something realthunder has been able to solve much better in his branch, but there is no reason to not be able to make it work.

FreeCAD for Inventors book

Finally, Sliptonic, a long time FreeCAD developer and main brain behind the Path workbench, has written a new FreeCAD e-book called FreeCAD for Inventors. It is available for purchase on Amazon and Kobo. It uses the same basic structure of the FreeCAD manual, that is, a general walk through the different parts and workbenches of FreeCAD, with a series of pretty interesting exercises. Sliptonic has also paid close attention to the usual requests and difficulties reported by newcomers to FreeCAD, and tries to address them in the book. Definitely a very good entry path into FreeCAD, if you are new to it.

That's it for this month, next month I'll attend the Google Summer of Code Mentors summit in San Francisco (and spend a couple of days in Mexico City on the way back). I'll be sure to dutifully report here.



permalink:  535   posted on 29.09.2018 10:38
From Thanks!
Commenting post 321: Awesome work

in categories  sketches  permalink:  534   posted on 23.09.2018 3:22
From Yorik

Urban sketching in Salvador

The drawings I did during the wonderful national encounter of urban sketchers in Salvador da Bahia, Brazil

in categories  sketches  permalink:  533   posted on 23.09.2018 3:19
From Yorik
A couple of sketches made in Teresina, Piaui

in categories  sketches  permalink:  532   posted on 23.09.2018 3:18
From Yorik
Drawings I did last week in São Luis do Maranhão

in categories  sketches  permalink:  531   posted on 23.09.2018 3:17
From Yorik
Today's sketch at Goethe Institute in São Paulo, with USKSP

permalink:  530   posted on 21.09.2018 23:32
From Yorik
Commenting post 528: Ah, obrigado por avisar! Vou dar uma olhada.. Abraços

permalink:  529   posted on 21.09.2018 23:30
From Yorik
Commenting post 527: Interesting, do you have any link to share? Indeed FreeCAD is a complex and powerful application, and it's very modular (different paradigms can coexist). So it's pretty hard to build good interfaces for it...

permalink:  528   posted on 12.09.2018 19:09
From sergio dias
Olá Yorik, como vai?
há algum tempo percebi que a ferramenta "cut with plane" não está funcionando na versão para windows (64b), nem a versão estável e nem a 0.18x (que é a que eu tenho usado...) acho ela muito importante para corte de paredes especialmente sob telhados. Que tal, assim que for possível, você dar uma verificada? Obrigado pela atenção e pelo excelente trabalho em um software incrível.

permalink:  527   posted on 10.09.2018 4:59
From Ramayya
Commenting post 512: May I suggest that you look at Apple's Human Interface Guide Lines for OS X and iOS versions of your FreeCAD Contributions?

These guidelines are more human-oriented than others that currently used in FreeCAD. It is very easy to get lost in the very Complex and Powerful application such as FreeCAD.

permalink:  526   posted on 03.09.2018 16:48
From Yorik
Commenting post 525: Hi, it's Blender itself.

permalink:  525   posted on 03.09.2018 14:27
From bori
yorik may i ask, what editor type did you use in your " modeling architecture with precision in blender" ? the one where i can still see my flat cad plan even in perspective view.

permalink:  524   posted on 02.09.2018 23:43
From Yorik
Commenting post 523: I don't know unfortunately, the structural calculation was done by the company who installed the structure...

permalink:  523   posted on 02.09.2018 23:40
From Aya
Commenting post 80: Realy Excellent Project , I want to know the used programs in analysing the structure .

permalink:  522   posted on 02.09.2018 7:44
From alex
Commenting post 35: looking for architectural element for inkscape

permalink:  521   posted on 01.09.2018 21:14
From Yorik
Indeed.. Now both are solid and pretty different applications, best of two worlds

permalink:  520   posted on 01.09.2018 18:52
From Rafael (bitacovir)
Commenting post 519: I remember that friction with LibreCAD project. But I remember that time QCAD was a very poor project (as community and pro version) with very slow development. Now, I think we have a happy end to this story. With LibreCAD and QCAD as must improved CAD programs.

permalink:  519   posted on 01.09.2018 18:41
From Yorik
Commenting post 518: Several reasons.. One is that they support dark theme backgrounds (in LibreCAD I can't see the icons), another is the two-letter keyboard shortcuts that "bypass" the annoying tool sequence (polyline tool -> select which type of polyline -> select which type of snap, now finally you can draw), and a third one because the QCad author got very pissed at the time of the LibreCAD fork, and decided to stop publishing QCad as open-source, then he changed his mind and QCad became open-source again, and I like that the guy struggled against the odds and keeps firmly on the open-source path while trying to make a business of it too, that deserves some recognition too...

permalink:  518   posted on 01.09.2018 17:37
From Rafael (bitacovir)
Commenting post 517: Thanks for your hard work making FreeCAD BIM possible.
One question: Why are you using QCAD rather than LibreCAD?

in categories  freecad  opensource  permalink:  517   posted on 01.09.2018 4:49
From Yorik

FreeCAD BIM development news - August 2018

Hi there,

One month passes bloody fast, doesn't it? So here we are again, for one more report about what I've been coding this month in FreeCAD. Looking at the text below (I'm writing this intro after I wrote the contents) I think we actually have an interesting set of new features.

None of this open-source BIM journey would be possible without the help of everybody who contributes to my Patreon or Liberapay campaigns, and therefore allow me to spend a good amount of working hours per month on FreeCAD. Thanks a million to all of you, it is really making a difference for FreeCAD, we're well on our way to a good, open-source BIM application.

The house illustrated in this post is a famous house built by architect Vilanova Artigas in São Paulo and was modelled by Wilson Melo.

So let's have a look at this month's features, but first, here goes our monthly video:

The video: 2D drawing

In FreeCAD, like in most other BIM applications, many 3D objects are based on 2D objects: Walls are based on a line, columns and beams on a 2D profile, etc. In most cases, you are not forced to draw that 2D object yourself: You can draw a wall directly in the 3D view, or you can place a structural component by selecting a preset profile from a list. However, all these objects can also be made from a custom 2D object that you draw yourself. There are many ways to do that in FreeCAD, this video will give you a quick overview of the available options.


As announced last month, we are reaching the first goal I have defined on Patreon, which is, a place where we can discuss BIM ideas and features to be implemented in FreeCAD, and you guys can vote for them, and I would do my best to implement the most voted ones. I had a look at the different (open-source and not) solutions available to do that efficiently, but unfortunately the results of this search are not very good. Most "feature voting" applications are very old and unmaintained, or require a heavy web infrastructure to be put in place, and you will certainly agree that our time should be spent better than in maintaining heavy web infrastructures just for that purpose...

So I thought, why not simply use the Github issues system? It is possible to vote there, submit new ideas, etc. Most open-source projects hosted on Github use it. It might not be the ideal (given the fact that Github is now owned by Microsoft, etc..) but at least it's easy to use, anybody can add new ideas, vote for existing issues (give it a "thumbs up", etc.

I am starting to put some ideas on the BIM workbench Github page, have a look there under the "issues" tab, I'll add more in the coming weeks. Don't hesitate to add your own ideas there, or comment as much as you like on the existing ones.

Full groups hierarchy in IFC

I discovered a small but bright IFC trick recently that might not be "proper" IFC behaviour, but that is definitely improving our FreeCAD workflow a lot: Groups, in IFC, are handled by an object called IfcGroup. However, groups are not really part of the standard way to use IFC, which is to use spatial structures (Buildings, Storeys, Spaces, etc..). As far as I could see, they are just offered as an additional way to create relationships between objects, if anyone really wants to. You will rarely see an IFC file that contains groups. Revit and ArchiCAD, although both offer the functionality, don't use groups much.

In FreeCAD, however, groups are a very important feature. All the objects of your model are appearing in the tree view, so it is very important to organize them. Grouping is an extremely powerful way to organize your model, and, unlike other methods such as using storeys or layers, it is completely free from any "meaning". You, the user, decide how you want to organize your model. Will you group all your walls under a "Walls" group? will you make sub-groups for different types of walls? Will you not use the materials system at all, and instead group all your objects by material? The model is yours, the choice is yours. Also, every project is different, it makes little sense to force users into one kind of arrangement. An office tower model should definitely not be organized the same way as a house.

In FreeCAD, you can mix everything together: Have groups inside levels (which are now handled by the BuildingPart object), levels inside groups, groups of buildings, anything your wild imagination (or very concrete requirements) dictates. But this was all lost when exporting to IFC.

Now I discovered that IfcGroups are actually derived from the same base entity as other IFC grouping features such as Storeys or Buildings, and, as such, they share some functionality. More important, it is possible to stack groups as part of these other entity types.

So from now on, you can export your wild model structure to IFC, re-import it, it will come back exactly as it was. Most of our BIM competing applications might still not be able to cope with such a complex model structure, poor them, but hopefully they will do their homework at some point.

Forgive me for the quite exaggerated last sentence, but I couldn't resist

IfcElementAssembly support

Another IFC feature I've implemented in the last month, is support for IfcElementAssembly, which is the standard IFC way to define an element made of several other building elements. For example a truss system, or a bathroom unit. It is a bit like grouping, with the difference that the assembly is not just a group but a real, physical, manipulable object.

In FreeCAD, any BIM object can be an assembly of any kind of geometry or other BIM objects. You just need to add them to its "Additions" property. However, until now, if the host object was a wall, it will be exported as a wall.

Now, if you change the Ifc Role of any BIM object to Element Assembly, it will be exported as such. But even better, BuildingParts will also be exported as IfcElementAssembly when its Ifc Role is set as such. And it is much easier to add objects to a BuildingPart, as you can drag/drop objects into it in the tree view, and is a much more "intuitive" way to construct an assembly.

When importing an IFC file containing IfcElementAssembly entities, they will be rendered as a BuildingPart, so all their components will be available and manipulable.

On our way to a full roundtrippable IFC <-> FreeCAD workflow!


Finally we now have preliminary support for quantities. I say preliminary, although it works well already, because I'm still not sure about the future direction of this.

Basically, the IFC format supports defining objects by quantities. Together with the geometry of an object, for example a wall, you can also attach quantities to it, for example a height value of 3 meters, or a thickness value of 20 cm. This is all arbitrary, you can decide yourself what name you will give to these quantities (it it "thickness" or "width"? "largeur" maybe? or "??"?) and, even more problematic, you can make them lie (the "thickness" value you give is not the same thickness as the geometry you provide).

So it is complicated to trust these values. However, the point is not there. The idea is that an application that doesn't have geometry support, for example a spreadsheet application, would be able to open an IFC file and build a list of quantities of all the elements in the file, without the need to have very complex geometry tools to extract that information from the geometry.

The idea is brilliant of course. Imagine "opening" your IFC model in Excel?

So here is how it works in FreeCAD now. The IFC Elements Manager (sorry, the documentation is not there yet at the time of writing, will work on it in the coming days) of the BIM workbench now has gained a new tab that shows available quantities for BIM objects. So far, I only considered objects that had standard, universally recognizable quantities such as width or length. This will be developed further along the way.

For any of them, you can now mark if you want those quantities to be exported to IFC. That screen will also show a warning sign when such a value is zero, which probably indicate a problem somewhere that you should look at before exporting.

These quantities are then exported to IFC and attached to the corresponding object. When reading back an IFC file, the quantities are not read, as we prefer to get them from the geometry, which is more trustworthy. In the future, we could think of comparing what the geometry says with the given quantities (FreeCAD as a lie detector for IFC files?), but I can't think of much use for that.

Start center redesign

I had been busy with this for some time, and it's finally ready. The old start page, which appeared when you opened FreeCAD, was something a bit clumsy and not very usable nor interesting. Now we have something that is much more useful, both for newcomers and experienced users. There are three tabs, one for your files, one for documentation, and one to have a quick peek at the recent activity in the FreeCAD world (latest changes to the source code and latest posts on the forum), which is a feature many users liked in the previous version.

All of this is customizable, translatable and themable, and you can even replace the start page by any HTML file of your own. That can be useful for example in companies or schools so they can display additional content.

There is also a "notes" area, that you can enable in the Start preferences, where you can write text that is saved across FreeCAD sessions. This could be useful as a kind of "FreeCAD to-do list".

There are still some small hiccups depending on the platform, but we'll address them on the way. Don't be scared about the colors in the images above, I adapted the start page colors to my desktop theme (you can do that in Edit->Preferences->Start), but by default it looks like this:

New website

This was not done by me but by FreeCAD user AR795, with the help of many others, bu have you seen the gorgeous new FreeCAD website? Next we'll adapt the rest of the FreeCAD web universe (wiki, etc..) to the same aspect.

BIM Box tool

Until now, the BIM workbench featured, among its 3D tools, the standard Part Box tool. Using boxes is very practical in BIM, more than half of the geometry we create is usually made of these rectangular shapes, and the Part Box is a very simple and versatile tool that has 101 utilities. The way it is created, however, is often annoying: A 10mm x 10mm x 10mm box appears at the origin point when pressing the button, which requires several additional operations to move it to the correct location and set its length, width and height dimensions. Most of the time I was using a Draft Rectangle that I then extruded, which was faster.

Now I rescued an existing macro and turned it into a full new BIM Box command (sorry, no doc yet) command, that still creates a Part Box, but graphically in the 3D view. You give two points to define the base line (length), a third point to define the width, and a fourth to define the height. You can also enter length, width and height manually in the Task panel, but you still need to click the two first points to define the position and orientation of your box.

These boxes can be used as walls (just press the wall button with one selected), beams, columns or any other BIM object, or as a subtraction to any of them (select the box, CTRL+ select the host object, press the Remove button).

Section plane controls

The Section Plane tool has also gained a series of improvements. First, when you create one, if you have objects selected, for example a building, the section plane will automatically be placed at the center point of the building and resized to encompass it.

Then, by double-clicking the section plane to enter its edit mode, you now have several controls to flip it in other directions and resize it to fit. So it is now much easier and faster to create multiple views and sections.

Section plane caching

With Wandererfan, we are working on having proper support for Section Planes in TechDraw, which is the FreeCAD workbench used to produce ready-to-print sheets. At the moment, you must still use the TechDraw ArchView tool, which is the only one that supports Section Planes. However, that tool has many limitations, because it produces its view through SVG, and therefore looses many of the TechDraw features such as the ability to add hatches and dimensions.

But while proper support is not ready, I already experimented with caching. The contents of the TechDraw ArchView is now cached, and only recalculated if the objects seen by the section plane change. So you can now move, rescale, change thicknesses, etc... of ArchViews without redoing the heavyweight calculations, which makes it much faster.

This seems to work pretty well, so that might be a good idea to implement further in TechDraw later on.

Terrain macro

Finally, I built this little macro the other day that builds a whole Site object out of a series of contour lines, that you can for example import from a DXF file. Your contour lines can be organized in any way you want, grouped in different layers, and don't need to be connected into wires (they can be a series of simple lines). The macro solves it all.

Internally, it breaks everything into separate edges, re-joins everything into wires, turns the wires into b-splines, sorts them by elevation, then builds ruled surfaces between the contours, then builds a shell object out of the surfaces. Finally, that shell is used as the Terrain property of a site.

There will be many situations where it won't work correctly (for example the sorting by elevation will produce wrong results if there is more than one contour with a certain elevation), which we can adjust later on, until it is good enough to become a real FreeCAD tool.

But the results are quite good already, and of a much better quality than the point cloud-based method I used some time ago. Plus, it is easily editable by editing the b-splines.

That's it for this month, see you in September!

permalink:  516   posted on 31.08.2018 21:51
From Yorik
Commenting post 515: Hi Dave,

These are actually two different projects, born more or less at the same time, that some fatality made choose the same name... We had some contact with Mr. Koh already in the past, but the two projects are really very different and there was not much of a "common ground" where some sort of collaboration could take place... The only annoyance is sometimes we have to explain this "two different projects" thing (sometimes it is more embarrassing, some very serious websites did quite poor copy/paste journalism and got awfully confused between the two), but I guess otherwise it is not a problem for any of us, and all users of respective apps are used to the name, so it basically stayed that way until today...

permalink:  515   posted on 26.08.2018 14:26
From suncitydave - Dave Brown
I'm very impressed with freecad's capabilities - particularly that it can handle gravity and momentum. I found freecad on a website www.ar-cad.com/freecad which is authored by Aik-Siong Koh. What is his relationship to your freecad community? If your response shouldn't be expressed in public, just send me an email at (nospam)@suncitydave.org. Thank you very much. Dave

permalink:  514   posted on 23.08.2018 21:13
From Brian Carver
Commenting post 40: Interesting article. While I program in linux world professionally my home boxes are windows. I did use a combo of GIMP, sketchup and scribus and published a book that way.

I am very interested in BIM and freecad. It looks like for my future home that is the way to go.

permalink:  513   posted on 22.08.2018 2:49
From Ramayya
Since "FreeCAD" enterprise is becoming very large, hierarchical tree setup of the documentation makes it very difficult to traverse through the various webpages. Since these pages belong to various aspects of the project, may I suggest a Concept Map of the FreeCAD webpage be developed and be available as the second page of the "freecadweb".

"The discovery of structural form" by Kemp & Tenenbaum (2008), discusses their approach to support structure learning methods that closer to human abilities.

permalink:  512   posted on 01.08.2018 17:16
From Yorik
Commenting post 511: To be honest I didn't test it thoroughly yet (it's been on my todo list for ages...) but I've grown (like everybody else I guess) to like much what realthunder has been doing in FreeCAD, and I think generally his proposal is good and goes in the direction we all want. If it doesn't work exactly like I would like is not too important, those things get adjusted along the way.
So yeah... I need to have a better look at it.

permalink:  511   posted on 31.07.2018 24:00
From Maiden
Commenting post 510: What is your thought on realthunders Link implementation?

in categories  freecad  opensource  permalink:  510   posted on 31.07.2018 22:15
From Yorik

FreeCAD BIM development news - July 2018

Hi folks,

This is the monthly development post about the development of BIM functionalities of FreeCAD. This month we won't have a video here, because there is quite a lot of stuff to show already, but next month I'll resume making videos, and I'll try to begin to show real projects in them too (not sure how doable that is, as it might easily make videos pretty long, but we'll try).

As usual, thanks a million to everybody who makes all this journey possible by supporting me on Patreon or Liberapay. As you might have heard if you are using Liberapay, they currently have problems with their payment provider, and operations are suspended there at the moment. Many of you who are using Liberapay opted to empty their online wallet by distributing their remaining money between the projects you sponsor, so I got quite an unusual amount of money this month (around 700 EUR). I am keeping this money intact for now, maybe there would be something cool to do with it, I don't know yet.

As I wrote here last month, by combining what I earn on Patreon (about 700 USD/month) and Liberapay (around 90 USD/month), we are hitting the first goal I had set on Patreon (750 USD), which is to set a site, or forum, where you guys can propose and vote for ideas to be implemented and I would try my best to make them come true. I lacked time to organise this, so it will be for next month. But it's definitely coming!

The project illustrated in this post is by OpeningDesign

So on with the stuff I did this month. Basically not much fancy graphical stuff, bu heavy work on the IFC side of things:

Property Sets and BuildingParts fully implemented and supported in IFC import/export

Last month I starrted with this by implementing support for property sets in FreeCAD. Property sets are a feature of the IFC format, where properties of an objects can be grouped into sets. As you can add any number or type of custom properties to any IFC object, you can also group them into custom sets. But the IFC format also provides standard sets, for example walls have a Pset_Wall_Common property set, that contains usual wall properties such as "IsExternal" or "IsLoadBearing". IFC Property sets are now fully supported when importing an IFC file in FreeCAD, and when exporting a FreeCAD model to IFC.

The other big feature I had been working on last month, the new BuildingPart object, which is made to replace the current Building and Floor objects with something more robust and versatile, is now also supported by the IFC importer and exporter. Depending on the IFC role that you give to your BuildingPart object, being Building or Building Storey, it will behave that way in the IFC file.

IFC properties editor

As important as the support for it in IFC, is the ability to easily edit, add and remove properties to/from your BIM objects in FreeCAD. So in the BIM workbench, we now have a full property manager tool. That tool can be launched directly from the BIM Elements Manager in the "Manage" toolbar or menu of the BIM workbench, or directly from inside the Edit Mode panel of BIM/Arch objects. If the BIM workbench is not installed, that option is not available.

I'm not a big fan of that, "plugins" that spread out new functionality inside existing tools, I find that confusing and hard to discover, so the idea is not to go that way, and keep things clear between Arch and BIM workbenches and not begin to mix stuff between the two. But at the moment I'm still experimenting with all this, trying to find where it fits best, so consider these "intrusions" of the BIM workbench inside existing Arch tools just an experiment to see how it works best. If it consolidates into some "ground" functionality, it will go to Arch. If it's just an additional layer of UI work, it will stay in BIM.

The general idea is that you might want to use the Arch tools sporadically but you work mainly with other FreeCAD workbenches. Then you don't want to be bothered with BIM stuff. Or you are using FreeCAD mainly for BIM, then you want the full-fledged BIM workbench.

IfcGrid support

We already had several Axis tools in Arch/BIM, that can already cater reasonably well for your axes/alignment needs. However, they weren't very compatible with the way these work in IFC, where each axis is an independent object, grouped under an IfcGrid object that defines which ones are in the X, Y and Z directions. The IFC importer and exporters of FreeCAD now support all this transparently. In FreeCAD, axes can now be only one axis, so IFC grids can be imported as they are (several independent axes inside one grid/axes system), and on export, FreeCAD systems made of several axes will simply be decomposed into their individual axes.

IFC compression

This is not a very good title for this feature, but it sounded powerful Basically this is something that Revit does, that is fully supported by the IFC format. When you have two objects that share, for example, a same point (0,0,0) or a same colour, or a same property (Height = 3m), this information is stored only one in the IFC file, and used everywhere it is needed. This results in drastic file size reduction (30 or 40% everywhere I tested) because in IFC there are a LOT of those simple, basic pieces of information, but makes the file more annoying to read by human eyes, because if you are reading about an object at line 3500, you might need to scroll all the way up to line 15 to know the position of the object, and then half-way back at line 1500 to know its colour.

So this feature is now enabled by default, because in most cases you will want that compression, but can be unchecked in IFC preferences if you need a more human-readable file.

Not every IFC information can be compressed/reused that way at the moment, I just implemented some of the most common ones, but the list is easy to extend.

IFC shared profiles

This is coming from an old dicussion we had with Ryan Schultz and Jon Mirtschin, about how to store and retrieve parametric profiles in IFC. The idea is that several objects can be based on a same profile, a very simple way to convey some "model intelligence" inside an IFC file. You modify the profile, all objects based on it change.

It turns out the IFC format supports that in a pretty simple way, very similar to the previous topic here above, you simply use the same IFC profile entity in different extruded objects. So the IFC importer now implements this, when different FreeCAD objects are extrusions of a same 2D object, it will be saved that way in IFC, and restored that way too when reading the file back.

So with all of the above we can now begin to get pretty accurate "roundtrips" when working with IFC files in FreeCAD. That is, the file contents you get when opening an IFC file you just exported are 100% identical with the original file.

Of course the concept of 100% equality is debatable, you WILL find something that is different from the original file, that is inevitable due to the complexity of the IFC format. But my idea is that we can settle on a general agreement over what reasonably needs to be there in order for us to consider it identical. I would say basically the model tree must be identical, the geometry of all objects must be identical, and all BIM-related properties of all objects must be there and contain identical values.

I think in many cases we have that now fully working in FreeCAD. I'm proud to say that you won't find that in many other BIM aps out there, even the big players

Base profiles restored as draft wire

A very simple addition, when an IFC extruded object is imported into FreeCAD, if possible (ie. it is planar and doesn't contain curves), the base profile is now created as a Draft Wire, making it easier to edit.

It's a very small and simple change, but I think we can go a long way like this. "IFC doesn't contain model intelligence", you will often hear hard-core supporters - or vendors - of a certain well-known BIM platform say. But if you think of what makes this intelligence, or in other words what is it really that you do when working with said platform, I think 95% of it are simple things, the ability to click an object and change its extrusion length, duplicate it but still be able to edit a common property of both, etc. All this is well supported in IFC, and can probably be recovered and used in FreeCAD with pretty little changes like this, and we'll be able to make IFC model much more editable.

No more intermediate extrusion for structs and walls

Another very simple change: Until now, when importing IFC objects that were extrusions, a 2D profile object was created, then a Part Extrusion, then this was encapsulated inside an Arch/BIM object with the correct IFC type. Now, for Arch objects that can create an extrusion themselves (Walls and Structures, basically), the intermediate step is skipped, and the final object is using the profile directly, making the whole model tree a bit thinner.

Ability to abort IFC import + fixed progress bar

The progress bar of the IFC importer never worked well, because it was interrupted and reset all the time by the shape reader (which "stole" the progress bar). The shape reader can now run silently, and doesn't perturb us anymore, so the progress bar displayed during IFC import show realistic progress and remaining time estimation. Plus, its abort mechanism is now functioning, and you can abort the import anytime by pressing the Escape key.

For IFC export, the process is so fast that I think we don't need a progress bar at the moment

Materials hierarchy

We had some discussions about materials recently, and, since they are used everywhere in BIM, I thought they could be a good way to handle these characteristics and properties that you want to give to several objects at once. In fact, IFC doesn't give you much option to give extra properties to materials, you have to give these properties to each object that uses the material. But we can do better in FreeCAD, and allow materials to have any number of custom properties (that is implemented already). So materials become a kind of "host" for these properties, and on IFC import/export there would be transferred to/from individual objects transparently.

But that means that if you have two objects made of concrete, but one of their "common" properties has a different value, you need two different concrete materials. This will quickly become annoying. So we need a system to be able to have one concrete material, but with sub-materials, which would change only one value, but keep all the others from their parent.

This system existed already in FreeCAD materials, and is now reflected in the tree. You just need to specify which other material is a parent of this one. There is still a lot to implement (additional properties, the ability to remove a value so it takes its parent's corresponding value, support all this in IFC etc), but I think we are on the right track to get an easy and flexible system that won't overcomplicate the model tree.

Part Shapebuilder - Wire from Edges

A simple addition to the ShapeBuilder tool, an option to build a Wire from a selected set of Edges. It doesn't need to be closed or planar.

American Wide Flange profiles and profile edit panel

A new series of American Wide Flange steel profiles (W profiles) was added to the Structure tool, and the profile object, that is used structural objects when based on a "built-in" profile, was also upgraded. It now uses an own icon, and it has gained an edit mode panel where you can change the profile definition.

At the moment you can only change to another profile of the same type (H, rectangular, etc...) because I am not sure it is a good idea to permit cross-type changes, model-wise (it will need another object, which as consequences on your whole model hierarchy), but we need to study that point further.

Support of classification systems

This is another rather simple to implement but major improvement. Classification systems are common since quite some time in the construction world. Basically instead of your own description like "concrete pavement tile for exterior use", you would use a number from a classification system that has an " 01 Exterior pavements" categories, with a subcategory " 03 tiles" with different categories for " 05 concrete", " 06 stone", etc. So your number would look like 01 03 05. You get the idea.

That way, you can give your file around, and there is a much higher chance that everything will be correctly understood, even by people in different countries, as the whole system can be faithfully translated. This is not used much for small projects of course, but think of stadiums being built in other countries, you might see the interest there can be in such systems.

There are many classification systems in use around the world already. Most of them proprietary unfortunately (you have to pay to obtain them), some open and free, and most countries are also developing their own which might or might not be compatible with others. In other words, this is a jungle

In FreeCAD, materials already had a "Standard Code" property, which can hold any text value. Now, all BIM/Arch objects also have a "Standard Code" property. The idea would still be to use materials for that, but you would be able to override the material code for any individual object.

Last month I stumbled on this repository made available by Graphisoft with many of the most used standards available as xml files (an open format). So now in the BIM workbench we have a Classification Manager tool, that is able to read these xml files, and set the Standard Code property of a material or BIM object with any its values.

So far this is not exported to IFC (I still need to understand better how it works) but we have a fairly decent classification system in FreeCAD already!

Note that these xml files are provided there by Graphisoft on their own good will. We cannot include these files in FreeCAD because they don't have any license allowing us to do so, so the responsibility to download and use them is yours (how to do it is explained when you open the Classification Manager in FreeCAD). They might change their system or simply remove those files anytime. Some of these, however, such as GuBIM, are open-source, and also provided on the website of their author. So it's important to keep fighting for open standards that we can really rely on on the long term.

BIM copy and BIM clone

Finally another small experiment: In the BIM workbench, there is one new tool beside the Move tool (which is the pain old Draft Move tool): A copy tool. It is simply the same Move tool, but with its "copy" option turned on by default. I think it is pretty handy, so you can start it by another shortcut (C,P instead or M,V) and perform a copy instead of a move. One click or key press less.

And another one, the Clone tool in the BIM workbench now works differently than the original Draft Clone tool: Immediately after creating the clone, the Move command is launched so it works more like in other applications: you select an object, press the clone button, and drop the clone at some other location (since you rarely want the clone to stay at the same place of its original).

I am not sure yet if these changes should go to Draft or not. Tell me what you think!

So that's it for this month, once again thanks a lot if you are supporting this effort, one step closer to our dream BIM application!



in categories  sketches  permalink:  509   posted on 29.07.2018 3:09
From Yorik
Latest sketches at museu Vicente de Azevedo, Praça Benedito Calixto and Rua 7 de Abril in São Paulo

permalink:  508   posted on 17.07.2018 3:15
From Yorik
Commenting post 507: Dankon!

permalink:  507   posted on 16.07.2018 24:23
From Walbero
Koran dankon al vi kaj al ?iuj kunlaborantoj de FreeCAD pro la bonega laboro kiun vi faras!

permalink:  506   posted on 02.07.2018 24:41
From Yorik
Commenting post 505: Sérgio não consigo identificar assim qual é o problema... Você não quer postar no http://forum.freecadweb.org daí a gente vê melhor? Pode ser na seção em português, ela precisa de atividade Abraços

permalink:  505   posted on 02.07.2018 21:57
From sergio dias
Commenting post 502: na minha versão win (64b) não consegui gerar os cortes...

permalink:  504   posted on 02.07.2018 7:07
From sergio dias
Commenting post 502: Não consegui utilizar o novo sistema de grid dentro do painel BIM, conforme o seu video acima...ele não aparece. A ferramenta frame (que cria uma armação a partir de um objeto 2d e um caminho) não está funcionando também. Acabei de baixar a versão 0.1839999 para windows 64b de hoje (01/07/18)

permalink:  503   posted on 02.07.2018 5:37
From sergio dias
Commenting post 502: software incrível. cada vez melhor!

in categories  freecad  opensource  permalink:  502   posted on 02.07.2018 3:51
From Yorik

FreeCAD BIM development news - June 2018

Hi all,

Time for a new update on the development of BIM tools for FreeCAD. There is some exciting new stuff, most of it are things that I've been working for some time, that are now ready. As always, a big thank you to everybody who helped me this month through Patreon or Liberapay! We are very close to meet our first goal on Patreon. We would actually already be there if we sum up both platofrms, so next month I'll lower the goal accordingly and declare it achieved and set everything up accordingly!

So here go the new stuff of this month:

The video

This month's video is a presentation of the new BIM workbench, so in next videos we'll use it instead of Arch. As always, your comments are highly welcome (here or directly in youtube comments).

You will remember last time that I told you about the impressive series of FreeCAD-related videos made by Regis, you might also be interested in this other very nice series about BIM and open-source, with a very large part dedicated to FreeCAD, made by Nirbhay, another well-known member of the FreeCAD community. We begin to have pretty decent FreeCAD BIM learning material!


The BuildingPart object I have been working on during the last months is finally ready and is part of the Arch workbench already. It is meant to replace the Arch Floor tool. For the time being, the Floor button is still there in Arch, but it already produces a BuildingPart object with its IFC role set to "Building Storey".

The BuildingPart object is still based on a classical FreeCAD Group object. I played a lot with the idea of using an App::Part instead, because it looked interesting because of its ability to automatically move its contents when you move it, and also that you can make it "active" and automatically add contents to it.

However, I discovered that it was relatively easy to reimplement these two features in another object, and also met some particularities that made me decide against using the App::Part:

  1. The App::Part only allows its children to be part of this App::Part. They cannot belong to any other. This, summed with another particularity, which is that all descendents of an App::Part also become its direct children, makes it impossible to use, for example, a same profile to build two columns placed in two different App::Parts, since the profile will become a direct child of the App::Part. This is not of big importance when designing, for example, mechanical parts, but is very common in BIM.

  2. When you add objects to an App::Part, then move the App::Part, the Placements of the objects don't change. Only their visual appearance gets moved. So if you build a column on the ground floor, then move its containing App::Part 3 meters above, the internal coordinates of the column still indicate the ground floor. And when you remove the column from the App::Part, it pops back to its original location on the ground. This is all "fixable" of course, there are methods in place to obtain the "summed up" placement of the column + its App::Part, and you can add code when removing the column from its Part to deal with the change of location, but this all seemed to me like trying to patch up something that's not really made for that use case.

    For part design workflows, this is exactly what you want: Draw your elements at (0,0), then add the to the Part, then move the Part around. If you remove elements from the Part, you want them back to (0,0). You want their internal coordinates to reflect that. In BIM workflows, I think we prefer all our elements to have real-world coordinates. Tell me in the comments if you have a different opinion!

So the BuildingPart is basically a Group, like the old Arch Floor. But with a lot of enhancements:

  • It can display a "mark" in the 3D view that shows the origin point and optionally the label and level (its z coordinate) . If you move the BuildingPart in Z direction, the level updates. You can give an artificial offset value, so for example if the offset value is 700, but your level is at z = 30, the displayed level will be 730. This is useful to work with geographic coordinates and elevations. You can also select the BuildingPart by its mark in the 3D view.

  • It can be made "active" by double-clicking it, like an App::Part. When a BuildingPart is active, all new objects will be added to it automatically, like the App Part or PartDesign Body.

  • When moved/rotated, all its children that either have no "Move With Host" property, or have it turned on, will move/rotate together.

  • When moving an object out of a BuildingPart, it will keep its current position, not "pop back" to its original position (different from App::Part)

  • It can be cloned. Internally, the BuildingPart stored a Shape, which is a compound of all its direct children. This shape is used by the clone, also keeping individual face colors. This shape is also stored on disk when saving the file, I think you'll be able to guess where we're heading for next

  • It can take any IFC type, like other Arch objects. The idea behind the BuildingPart is not only to serve as a Floor/Level/Storey, but to group BIM elements in any other possibly useful way in a replicatable manner. One obvious use would be to make a typical storey of a tower, then replicate it for the other floors, but we can also think of other replicatable things like a toilet stall, a wikihouse component, etc.

  • It can set the height of included walls and structures automatically. The Arch Floor could do that already. If a height value is set for a BuildingPart, any wall or structure inside it, that has its Height value set to zero, will adopt the BuildingPart height.

  • It defines a working plane automatically. When double-clicking a working plane, in the tree view or the BIM views manager, the working plane will be placed on the XY plane of the BuildingPart. Later on, I'll also implement the same functions that the Draft WP proxy has, which is to be also able to restore a view angle, and show/hide other objects.

    So the idea here is that you would be able, for example, to double-click a BuildingPart which represents a level of a building, and set yourself automatically in top view above this level, hide all other levels, and set the working plane to the floor plane of this level, just like if you were working in a 2D plan. When deactivating that level, you would have everything turned back on, and pop back to the view you were at before activating.

    But I found it safer to go step by step, and let people play a bit with the BuildingPart first, before implementing more stuff.

Blender importer

This is another big thing I have been working on for many months. It stayed a long time on hold because we were waiting for FreeCAD to reach a good Python3 compatibility. This is now done thanks to the hard work of several FreeCAD developers, specifically looo and Werner (and a bit of myself too). The issue there is that Blender only uses Python3 while FreeCAD was still not fully ported to it, but Python2 and 3 modules are incompatible with each other.

The code of the importer currently lives in a gist, but as soon as I get some remaining issues fixed, I'll submit it as an official Blender addon.

You can already use the importer, it is pretty stable already, but you'll need to get your hands on (or compile yourself) a version of FreeCAD compiled with the same Python version you use in Blender. The minor version number must match too, so if for example Blender uses 3.6.1, FreeCAD must use also 3.6 (the third digit can be different)

After that, it's just a matter of saving the code from the gist as a .py file (for example io_import_fcstd.py) and place it in Blender's addon folder, then enable it in Blender's addons preferences. If your Python3-compiled verision of FreeCAD is in an unusual location, you might also need to set its location in the addon's preferences.

This is all still a bit uncomfortable, but with time this will get addressed properly. The important part is that it already works pretty reliably.

You will then get a new option in Blender's File->Import menu to directly import a FreeCAD file. You can set a scaling factor between FreeCAD's internal unit (millimeter) and Blender (at the moment I set the default to 0.001) which will import as one Blender unit = 1 meter, and set a couple of other handy options.

The importer will at the moment only handle Part and Mesh-based objects. That is, basically, no texts and dimensions. Groups are also not yet supported, and either are clones (each comes as a separate object). But the geometry comes pretty accurately. Curved faces will be triangulated, flat faces imported as ngons. Materials are also correctly handled and attributed, and materials have both Blender internal settings and cycle nodes (I stil need to implement a proper cycles transparency node for transparent materials).

There is also one feature that will be specially interesting in viz work: The ability to replace objects with similar names. FreeCAD holds an internal, unique name for each object. Blender doesn't have that feature, but has something similar, where an object holds a mesh that can have a different name.

So what happens now is that the Blender object name is set to the FreeCAD object label, while the mesh name takes the FreeCAD object unique name. This allows to match each FreeCAD object with a corresponding, unique Blender object. If you enable the appropriate option when importing a FreeCAD file, if a corresponding object is found in Blender, only its mesh will be updated, the current Blender materials will be kept (and reattributed per-face).

This allows you to work on a FreeCAD model, import it in Blender, makes some changes to materials in Blender, setup your scene, add more objects, etc... Then reimport your FreeCAD files, and keep the object positions and materials that you changed in Blender.

Arch objects now check their properties at file load

This is a small change, but that will be great for backwards and forwards compatibiliy between different versions of FreeCAD. Basically objects loaded from an older file will now have their properties updated when loaded in a newer version of FreeCAD, so they'll be albe to use all the new features.

In the same way, objects loaded from a file made with a newer version will be able to "auto-fix" to work with this version.

Walls can have their baseline as Draft lines

Walls can already use all kinds of 2D objects as their baseline, but by default, new walls will have their base line created as a sketch. This is not always the most interesting thing to do, in many cases a simple Draft line is more efficient, as it can be edited by Draft tools like Edit or Stretch, which support snapping. So now there is a preference option to make new walls create a Draft line instead of a sketch.

IFC Property Sets

This is still a work in progress and not ready for merging, but it's an interesting subject anyway. In IFC, objects can have custom properties. These properties can be grouped into property sets. At the moment, when reading an IFC file, FreeCAD will read and store all properties of an object, but not the property sets they belong to. So when reexporting the file, properties will loose their property set information.

I tried for some time a complicated way to handle these property sets, but recently found a much easier (json-based) way which will also serve for other things (speckle?). So this part can almost be considered as solved.

There is another interesting feature available in the IFC specification, which are pre-made, or standardized property sets. These define, for example, some common properties for walls, that all walls should have. Same for almost all IFC entity types.

These standard property sets are not mandatory. In fact I have very rarely seen an IFC file that uses them. But using them in FreeCAD would be a very good way to create more standardized IFC files. These property sets are not defined in the IFC schema, so I already coded a small utility to download these definitions from the net, and pack them in an xml file. This xml file will be bundled with FreeCAD, and the IFC property editor I'm working on will be able to use it, so we can easily, for example, add common property sets to our objects.

Dynamic window parameters

So far, once a window was created, it was possible to change its width and height via its properties editor. To change more advanced details such as frame thickness, you had to edit the window components parameters or the base sketch directly, which was tedious. Now, windows have two new properties: Frame and Offset. As with width and height, changing the frame or offset values will change the window accordingly.

If you wish to use this in your custom windows, it uses the same system as width and height: In the base sketch, if you define two length constraints (horizontal or vertical) and name them "Height" and "Width", they will be controlled by the host window's "height" and "width" properties. To have other length constraints controlled by the "Frame" property, just include "Frame" in their name, for example Frame04.

In the window parameters editor, you now have two new checkboxes to make use of the offset and frame properties.

This is not the end of the path of course, but slowly we'll get there to a friendlier window object...

Merge dupliate materials

By right-clicking a material group, you now have an option to merge duplicate materials. That is, materials with a same name but with 3 digits at the end. For example Concrete and Concrete001 will be merged. Any object that used Concrete001 will be changed to use Concrete instead. Very useful when importing susequent versions of IFC files.

BIM IFC elements manager now manages materials too

Now this dialog from the BIM Workbench also allows you to check what object uses what material, and make sure you have everything properly configured before exporting to IFC.

in categories  sketches  permalink:  501   posted on 01.07.2018 2:29
From Yorik
Today's sketches at Vila Mariua Zélia with USKSP.

permalink:  500   posted on 01.07.2018 2:27
From Yorik
Commenting post 499: Thanks for the link! I hadn't seen they had a linux version already. I just tested it now, this is very, very impressive... Basically what I wish Sketchup would be A Sketchup that saves solid models.

Two things, though:

- It is still very unstable, I can easily make it crash in less than a minute.
- It only saves DWG/DXF files. I think it might be time for FreeCAD to seriously attack SAT/SAB format...

permalink:  499   posted on 28.06.2018 20:45
From Ethan
Have you looked into the new bricscad shape software? They just released a linux version for free. I would be interested in your thoughts on the software.

permalink:  498   posted on 23.06.2018 1:52
From Berk O
Commenting post 97: wow. That is really inspiring. Thanks for post. i ll try

in categories  talks  permalink:  497   posted on 22.06.2018 22:34
From Yorik
Slides dos eventos recentes em São Paulo:

- Ferramentas programáveis - Participação na mesa "Fronteiras da tecnologia na cultura" na UFABC : https://yorik.uncreated.net/archive/talks/ufabc-2018.pdf

- BIM e estruturas prefabricadas: Adaptabilidade, interoperabilidade e formatos abertos: Palestra no 1° seminário Precast Concrete Technology : https://yorik.uncreated.net/archive/talks/pct-2018.pdf

permalink:  496   posted on 22.06.2018 22:28
From Yorik
Commenting post 495: Hm interesting idea... Adding to my TODO list

permalink:  495   posted on 20.06.2018 15:52
From Dion Moult
Commenting post 293: Great idea! However one of the most important features would be to view the model from the point of view from the sun. This is how we do all the solar compliance checks, especially for large developments.

in categories  sketches  permalink:  494   posted on 11.06.2018 2:18
From Yorik
More sketches...

in categories  sketches  permalink:  493   posted on 06.06.2018 3:20
From Yorik
Sketches of sunday at the Orthodox metropolitan cathedral of São Paulo. Pretty cool that they let us draw during the ceremony... Unfortunately they also kicked us out when it was done, so I finished these two at home...