Is it true that large architecture is all about project management?
The ecology of Autodesk suites certainly suggest this. In the 2013 building suite celebrates their primary software, Revit. The sell of the product is its collaborative tools which allow for version control, clash detection. It is a 'coordinated and consistent model-based approach'.
Here is my frustration: underlying the model-based approach is a limited palette of techniques and components. I've found the process of modelling to be counter-intuitive to "sketching". Sitting in the cockpit of revit is like steering a lumbering behemoth.
This inspires deep envy when I contrast my revit experience to the modelling environment of Mudbox or Maya. The model tweaks and responds at a speed that flows well with the creative process.
I suspect the family-part-assembly technique will help this - if only I can figure it out!
The ecology of Autodesk suites certainly suggest this. In the 2013 building suite celebrates their primary software, Revit. The sell of the product is its collaborative tools which allow for version control, clash detection. It is a 'coordinated and consistent model-based approach'.
Here is my frustration: underlying the model-based approach is a limited palette of techniques and components. I've found the process of modelling to be counter-intuitive to "sketching". Sitting in the cockpit of revit is like steering a lumbering behemoth.
This inspires deep envy when I contrast my revit experience to the modelling environment of Mudbox or Maya. The model tweaks and responds at a speed that flows well with the creative process.
I suspect the family-part-assembly technique will help this - if only I can figure it out!