There is somehow no major changes on how we deal with information within Archicad. I remember to follow your smart advices and workflows 10 years ago... and we are still on similar stand points.
I think that if you follow those fundamental workflows then the software works reasonably well with you, not against you. A conversation I had with someone at the time suggested I had successfully built workflows to counter the deficiencies in the software. Essentially workarounds. I think the processes worked a decade ago and continue to work now. And I am shocked to not see more people following my methods yet. They don’t understand the benefits of how it all translates when you work in IFC yet.
@@SkewedBIM Agree. The lack of a massive adoption when sharing (open) structured data yet is probably one of the reasons... i.m.o. The only thing I stopped using was the placeholder *.att for the Attribute Index number since the introduced Index renumbering feature some versions ago.
@@daviddelgadovendrell I have stuck with it because it is hard to change a heap of attributes in one go. Plus they all tie to my specification which I don't understand why more people are doing that yet.
It would be interesting to test to if your Airtable data and our Dataverse data can be shared easily between systems. Do you use M365 or Google or OpenOffice?
I have all of my other stuff running through 365. This was an experiment I set up a few months back because I wanted to kill off emails for design changes. In an ideal scenario this would be a process that aligned with BCF protocols so that these issues could then be added to a BIM process. But these days the collaboration platforms are too expensive at the small end of town.
![I.N "HALLUCINATION" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/n5B5q1Hwt_U/mqdefault.jpg)
![Noob To Max With DRAGON REWORK In Blox Fruits [FULL MOVIE]](http://i.ytimg.com/vi/LnBMOinoOvA/mqdefault.jpg)
There is somehow no major changes on how we deal with information within Archicad. I remember to follow your smart advices and workflows 10 years ago... and we are still on similar stand points.
I think that if you follow those fundamental workflows then the software works reasonably well with you, not against you. A conversation I had with someone at the time suggested I had successfully built workflows to counter the deficiencies in the software. Essentially workarounds. I think the processes worked a decade ago and continue to work now. And I am shocked to not see more people following my methods yet. They don’t understand the benefits of how it all translates when you work in IFC yet.
@@SkewedBIM Agree. The lack of a massive adoption when sharing (open) structured data yet is probably one of the reasons... i.m.o. The only thing I stopped using was the placeholder *.att for the Attribute Index number since the introduced Index renumbering feature some versions ago.
@@daviddelgadovendrell I have stuck with it because it is hard to change a heap of attributes in one go. Plus they all tie to my specification which I don't understand why more people are doing that yet.
It would be interesting to test to if your Airtable data and our Dataverse data can be shared easily between systems. Do you use M365 or Google or OpenOffice?
I have all of my other stuff running through 365. This was an experiment I set up a few months back because I wanted to kill off emails for design changes. In an ideal scenario this would be a process that aligned with BCF protocols so that these issues could then be added to a BIM process. But these days the collaboration platforms are too expensive at the small end of town.