Working with external components
-
Hi -
We are working on a Sketchup model of an existing building and exploring several concepts for making additions. Each concept is being made into a component, then we are using right-click > 'save as' to save the components to external files. So, we have a file called 'base model' and others called 'concept A', 'concept B', etc.
There are several of us working on the project, and we want to be able to open the individual components to work on them. The problem is that we need to be able to see each concept in the context of the 'base model', but do not want to that base information to become part of the 'concept X' component. Doing so would create something akin to an AutoCAD 'cyclical reference'. Does that make sense?
Basically, we want individuals in the office to be able to work on separate concepts in reference to the base model information.
Thanks -
-
Hi,
First of all, although this is not the answer to your problem or question, have a look at TIG's X-ref manager plugin - in such a working environment, it may be useful:
http://forums.sketchucation.com/viewtopic.php?f=323&t=7329Now I see what you are doing but cannot see what the problem exactly is.
-
I'd have the 'site' as a model - with nothing inserted into it.
I'd have several site-option models: these would each have the 'site' inserted as a site-component.
If you change the 'site' in its original model file you can then reload the site-component in any of the site-option models and it updates.
If you change the site-component within a site-option model do not export it back out and overwrite the original 'site' UNLESS this change affects every option [at which point all option users must reload it to be in step] - if it's an option specific change then you must leave as it is in the site-option model and then remember never to update it from the external 'site' model again - you could of course then export an option version of the site if required.
For each site-option you'll have a number of building models etc which are also external model files.
You'd insert them into the appropriate option-site model as components.
If you edit any of these in their original model files you can reload them into the appropriate site-option model.
If you change the component within a site-option model AND it is a permanent change then export it back and overwrite the original [you could always make a backup copy of the earlier version first, in case you want to 'revert' later on].
You cannot have the site inserted into a building model because a reload of it into another model will bring the site with it - however, you can change building component within the site-option model and export it, them reload into another file...
At its extreme you could have a site-option model for each site option version for each building [the other building would be inserted for context but never edited] - you edit the ONE building component and export it - a central site-option model would have all such building models inserted as components and reloading them will update all into this central site-option...
All of this is pretty complex and needs to have a written document so users understand what they are doing and can do - unfortunately it's impossible to legislate for someone accidentally updating the wrong component in the wrong model and exporting it, overwriting something and reloading it elsewhere....
Setting it up this way separates both the 'site' and the 'building' models for the options but needs some pre-planning...
Advertisement