2 hours ago
- last edited
14m ago
by
Laszlo Nagy
Hello everyone, this is my first post on the forum.
I am currently working on a new Archicad 28 template and exploring an alternative approach using Design Options. I would like to know if anyone has tried something similar or has experience with this setup.
I am experimenting with using Design Options as a way to control the visibility and working context of 2D documentation elements, in addition to their use for design alternatives.
Instead of managing multiple discipline-specific layers or relying on detailed layer combinations, I am testing a simpler layer structure:
The discipline separation is handled through Design Options. I created a group called “Template Documentation”, where:
All 2D documentation elements are assigned to a specific option, and their visibility is controlled through the Design Options settings in the View Map.
In daily use, I keep the Design Options palette always visible, and I switch context by double-clicking the relevant option. I also optionally use “Edit Only Default” to reduce the risk of accidental modifications outside the active context.
The intention is to evaluate whether this approach may simplify layer management and improve control of multi-discipline documentation inside a single model.
Has anyone explored a similar approach, and if so, how does it behave in terms of scalability, team workflows, or maintenance over time? Are there any limitations or issues that typically appear when using Design Options in this way?
Operating system used: Windows 10 - Build 19045.6466
2 hours ago
I have also been exploring a different approach to Design Options.
In projects with large sites containing multiple buildings, I assign each building to a separate Design Option. This allows me to quickly turn specific buildings on or off simply by activating the corresponding Design Option. I find this particularly useful when exporting IFC files by building, as well as when generating isolated 2D documentation for each one (floor plans, elevations, sections, etc.).
This approach can also be applied to projects where the intervention is limited to wet areas. In such cases, each wet core can be assigned to its own Design Option, providing precise control over visibility both within the software and in the resulting documentation.
36m ago
I definitely recognize that design options are underutilized in among my projects and my various clients templates and workflows. I have, however, seen cases where they become overly complicated and used for divers ends, and it complicates the project to a degree that we often need to have team meetings to reverse engineer what has been done.
lately, I've been exploring how to leverage design options within hotlinks to review building layout/placement on a site... it's effective, but a bit cumbersome at times.