Modeling
About Archicad's design tools, element connections, modeling concepts, etc.

Help me win the ArchiCad vs AutoCad office debate

Anonymous
Not applicable
I joined a development corporation that until I arrived had no architecture department. I showed my skills and background and thanks to my knowledge of ArchiCad and the Chairman's intense pleasure in seeing things so quickly in 3D, got the job. 2 months later they bring on another architect, one who has done a few projects for this company in the past. He does not computer draft well, but the little he can do is in AutoCad. He's been framing a debate of one vs. the other since he arrived and while I openly offer to translate all the files I work on into his archaic and simplistic program, its like I'm talking to a brick wall. The debate is about to hit a major head and despite my ability to create much faster drawings and without additional time or expense place everything into 3D and have presentation images ready at the drop of a hat, he's playing the "industry standard" card. I point out that the DWG file format is the standard, not the program, but the company execs don't know the difference. I need more fodder for my argument. At this point I'm ready to walk away and pursue another route as this issue highlights more than just a drafting issue. And with a project as large as we are taking on, I can't imagine starting off on the wrong foot and always being 5 steps behind. Somehow the logical argument isn't having the effect I'd prefer. Any suggestions?
20 REPLIES 20
Djordje
Virtuoso
Scott wrote:
Autodesk is now recommending transfer between Arch Desktop and Revit using IFC. Arch Desktop items keep their 'intelligence' through IFC when brought into Revit, something that even the "almighty" DWG cannot do.
This is a welcome change ... or a recognition or the reality?

"Almighty" Like it
Djordje



ArchiCAD since 4.55 ... 1995
HP Omen