Justin Marchiel
2006-05-03, 06:18 PM
We are in the prelim stages of a project where we have a building with 3 identical wings. I want to show options of how the wings can be assembled on the site. I have documented the "typical wing" and used groups for the typical suites.
Now to assemble the options for the wing configurations, i am thinking that it might be esiest to link the typical wing into a new project and copy it around and create design options as required. The reason for this is i dont want to create a group of the typical wing and then set it into the design options (from what i have read there seems to be a lot of slow downs with groups inside groups, and then i would have this wing group in several options, so it could really slow down when updating the wing group).
Does my idea of linking into a new project sound feasable? On a glance it seems to work well, but i am wondering about potential downfalls. We are in the skematic stage to i dont mind assembling the wings back into one project further down the road.
Thanks
Justin
Now to assemble the options for the wing configurations, i am thinking that it might be esiest to link the typical wing into a new project and copy it around and create design options as required. The reason for this is i dont want to create a group of the typical wing and then set it into the design options (from what i have read there seems to be a lot of slow downs with groups inside groups, and then i would have this wing group in several options, so it could really slow down when updating the wing group).
Does my idea of linking into a new project sound feasable? On a glance it seems to work well, but i am wondering about potential downfalls. We are in the skematic stage to i dont mind assembling the wings back into one project further down the road.
Thanks
Justin