The resolution: working with real #datadrivendesign, connecting the right tools for the job: #gdl with #illustrator automation and Airtable, for centralizing the data that will drive **absolutely everything** and keep it outside the Archicad files for shared management and quality control. I hope it serves as inspiration for other fascinating case studies.Īs a synthesis: an undecisive client, an incredibly large amount of information to provide, a very repetitive set of tasks, and a very short time to the deadline. This is not a light one, so please grab a coffee and fill the tank with patience, because this example, can be extrapolated to many other different cases whenever we have a structured set of data aiming to govern a #bimmodel. Thanks to the team: Jaehyuk Kim, Melissa Chan, and Grzegorz Wilk for sitting down and describing one of the most different and fascinating workflows that we, in enzyme., have recently worked on.
This article took a while to put together. Here is the short video, and another longer video showing the full process in our YouTube page. Thanks again to everyone that offered help already! We are very close to release the #beta, stay tuned for the announcement! This could be a masterplan with simple volumes that when you click one of them opens another file with several zones as the apartments, and then another link to the detailed apartment model… bim files) but now linking elements in different BIMx files. The demo, by Grzegorz Wilk, showing a workflow between #Archicad, #grasshopper and #bimx making possible the creation of a custom link between one and many elements, displaying in BIMx a custom #actionable #interface created from grasshoper that would enable the concept of multi-level BIM (previously demonstrated by Wojciech Radaczyński with. Following up last week’s announcement, We would like to share a short teaser video about some of the functions implemented in the #ArchicadAPI #grasshopper #plugin.
0 kommentar(er)
