Mihai wrote:
Quote:
In architecture the workflow is different. We are taught to work and think in 2D (at least I was)
I think the only reason for that is computers weren't powerful enough back then. I can't think of any professions more suitable to work in 3D than architecture and industrial design. They have adapted, architects not. Why?
In fact we architects think in 3D but show things in 2d cause it is much easier. There's no need to define every detail in a building just say "this kind of detail goes there". For example: if engineers and architects had to to make drawings of an artichoke the former would make a detailed drawing including every leaf of the artichoke and the latter would draw a stem and an egg-like shape filled with a line pattern representing the leaves. And that's fine because architects and engineers work in different scales and need different level of detail to show things.
Quote:
-certain amount of snobbism in this profession. What the older generation doesn't understand is classified as a gimmick.
- architecture software HAS to be overly complicated and silly, otherwise it's not "pro" (tied to first reason)
Those are old school architects IMO. Nowadays architects are more humble for many reasons.
Quote:
- cost of construction. Use the most inefficient, crap materials that make you sick and consume lots of power to keep warm/cool, even though there are plenty of better alternatives, which aren't much more expensive. So then as Brian says, any change that will cost them anything, is out the window. Usually.
That's true, most of the times there is no time or money to make a 3D representation of your project. Economical conditions are set by the clients and very few are willing to expend more than the minimum needed.
Quote:
This is just offered as one concrete example, with the point being: this plugin wasn't so much built in AutoCAD because that was the best environment, but because it was basically the only viable environment, when it was originated. So it really is much the same situation as with IE: there is a lot of business infrastructure that depends on AutoCAD. There may be better solutions now, but by the time they appeared, too much was already invested.
Eventually, I'd like to find the time to write a substitute for it, definitely in Rhino, but that is a pretty big undertaking, so for the foreseeable future, we'll continue to need AutoCAD.
Good point JD