True cross referencing to avoid doubled up geometry & components
I have been trialling this extension for the last couple of weeks. Its awesome in its current form with the batch save out/reload. Its a total game changer for me in my day to day modelling with SU.
Can I suggest the following way it may be improved/completed?
Situation:
Tom and Harry have two working models for a particular job. (You may be asking yourself where Dick is in all of this? Conveniently for Dick, He is on vacation during this job with no component browser headaches either).
- site map
- building
Lets say that concurrently, Tom is working on ‘site map’ and Harry is working on ‘building’.
Into his site map model, Tom imports the building model (in its current, ‘work in progress’ state). The building model is now a component called ‘building’ contained within the site map model. He continues to model around the building component without editing actually it.
Soon after, Harry imports the site map model into his building model but has done so after Tom already imported the building model into his site map model. Because the building model has only just been imported to the site map model (and is now a component within site map), this action has caused Harry to wind up with a double up of the building geometry - one lot that is native to his model (the original building), and the other lot that was re-imported as a component ‘building’, via Tom’s site map model.
Any subsequent reloading of each cross referenced model will continue to stack doubled geometry on top of itself causing a headache in the component browser etc.
Is it possible to add the following functionality to this extension?
Upon importing or reloading a model, the user is prompted to choose from a list, which of those incoming groups/components is actually excluded from the import. In the example above, Harry would have greater success if he had the option of excluding the component named ‘building’ from the import, thereby ensuring he doesn’t import a copy of his own model.
I can imagine the process would be rather like importing scenes using 'Eneroth View Memory’ or some such.
I know that the extension ‘Cross Reference Organiser’ does this in an automated fashion but it doesn’t seem to allow the user ‘check box’ style control over what components contained within the model to be imported are included/excluded during said import. It would also make sense to integrate this functionality into Eneroth Reference Manager given all its other fabulous features.
Thoughts? Tell me I’m the only one who has encountered Tom and Harry’s problem while modelling?
Finally, I want to reiterate that this extension is already extremely useful and IMHO should, in fact, be native to SU.