Judging by the feedback from our friends in the Revt camp it would appear that Revit has moved ahead of ArchiCAD in a some areas that we have discussed hear and elsewhere on the wishlist: flexible windowing, the ability for each view to retain unique visibility settings, built-in RCP and demo plan functions, to name a few. Clearly ArchiCAD will need to address these issues to stay in the game. My thoughts on how Graphisoft should proceed, based on my own view of the ArchiCAD way, and the great conceptual foundation we have laid in this thread, as follows:
Flexible windowing:
ArchiCAD is already strong here, multiple plan views being the most notable missing link. The ability to crop plans like we do with S/Es would also be nice and could be easily implemented depending on how the plan is originally defined.
Unique settings for each view:
The front end for this is well established. We already save quickviews which comprise a defined set of visibility parameters. The difference would be that each open window would remember it’s settings even after moving to another window with different settings and then coming back. This would necessitate some new code. More importantly it begs more questions about structure and workflow. Does each view (sheet) get it’s own window? For example if two views are derived from the same S/E do we want to be able to open each in it’s own window? And do we want real-time change propagation like Revit, always, never, on a window by window basis?
RCPs:
If plan views were defined like S/Es then the view direction could be up as easily as down.
Demo Plans:
Do we need more than the current tool set to deal with this, is this broken or lacking?
Plans in general:
A number of people here have made a strong case for keeping the schematic nature of plans as opposed to adopting a 3D top view approach. I fully agree. A plan is a diagramatic rather than literal view of the project.
But I would submit that with the introduction of multiple plan views the current Story paradigm becomes obsolete. The great value of Stories is in dividing the model vertically, obviating the need for layers to distinguish objects on each level. It essentially creates multiple horizontal sections within one window. With each plan now having it’s own distinct window this becomes unnecessary. We don’t need it for sections, why would we need it for plans?
But this means we need a way to define plans that is better than Stories. Here again we need simply draw from the established and well working functions we already have, in this case the S/E tool. With the S/E tool we have the ability to set the bounds (crop), direction (RCP v floor plan), depth, and distant area attributes (ghost story) of the view.
Now it’s true that a plan is not just a horizontal section but a specially modified one. So we will need either a new section type availabe within the S/E tool, or simply a new tool, the Plan tool.
Taking this one step further I can imagine enhancing the 3D environment so both S/Es and plans can be defined in 3D by dragging and resizing visible cutting planes. Through tool settings we could choose in which other views section markers would appear. Of course they would remain fully editable in those windows.
It sounds complicated but with careful implementation it need not be. If done right it would be great.
Regards,
Geoff Briggs
I & I Design, Seattle, USA
AC7-27, M1 Mac, OS 14.x