Djordje wrote:
The real question is:
Why do people that do use Archicad for longish time don't use it as intended?
Reality?
I was also disappointed by 11, but - if the reality is that you are considered an uber user if you don't draft your sections, then 11 is just what everyone needs. Or most do.
............
May the Force be with us ...
Hi Djordje,
First of all, my respect for your commitments and knowledge shearing within ArchiCad community (regardless been paid or not by Graphisoft).
Although this is only my second post, I have to admit that my experience with 3D model based architectural CAD goes back to 1989 and Architrion software, then it was Microstation TriForma1996-1999 and since than ArchiCad (6.5 thru 10).
I am one of those project/design architects that (since 1989) carried 3D model all the way thru construction drawing phase (regardless of architectural or management size and complexity).
This introduction has too many words for I just tried to say about me being experienced user and that there are rules I recognized throughout practicing architecture by means of Virtual Building CAD Environment (hardware, software and humanware).
Few of those rules/realities are (I am sure this list will be added):
- VIRTUAL BUILDING MODEL is not building description but DEFINITION (therefore you don’t model everything but building elements required for definition at any resolution you decided is sufficient or software/hardware/humanware is capable.
- BUILDING DEFINITION, by itself, is not INSTRUCTION how to build a building.
- INSTRUCTIONS are expressed thru Words, 2D Drawings, Applicable Building Code, Standard References…….and images!! (something for our friend Dwight as long as WYSIWG)
- MAKE IT SIMPLE, STUPID principle is very applicable, when it comes to instructions/documents we are creating in process of EXTRACTING information from Virtual Building Model or ADDING such an information to it (detail drawing, note or similar)
- HUMANWARE is 95% 2D, and is very important to recruit those guys when it comes to production. My software has to talk to them so they can contribute to the instructions what and how to build (AC11).
- ……………………………………..
This is obviously not detailed or definite list. PLEASE ADD TO IT.
Few facts about ArchiCad that I appreciated:
- Graphisoft thru ArchiCad development sustained vision of Virtual Building for over two decades (very few CAD had that approach back 20 years ago), and I hope this merge will insure healthy future.
- ArchiCad evolved way more than AutoCAD thru that period
- ArchiCad thru its CONCEPT is committed to support process of architectural design development which is all about what if and coordination of those changes that occurs in our documentation. (although we have reason to be disappointed for certain feature is not yet there and we have to use work around)
- ……………………………………………………
Few facts about us:
- Very few of us, maybe 10%, is using this software to its capacity (either for nature of projects or our own limitations).
- None of us is using all available ArchiCad features, yet at same time “we” insist on those missing and assume that every one will be using it.
- We are often forgetting that our clients and authorities approving our designs will see only our printed documents and won’t have slightest idea of ArchiCad or any other software features that are sold to us as exciting way of making ARCHITECTURE happen.
One opinion at the end: Annual subscription and more incremental upgrades to software is more productive and easier to adopt. Graphisoft has to establish clear bug free upgrades paths from previous versions so we can at any time open all our projects with most recent version (not easy task to Graphisoft but very important for operability of any architectural practice)
