I'd like to understand what workflows modelers are using to concurrently work on several different parts of a large simulation environment across multiple different modelers and then bringing the parts back together into a single model. We use a concept of "master" where one modeler is in possession of the master model, while others may be writing/testing some logic for a given area, or setting up visual environments, etc., etc. Then once those sub tasks are done, code is copy pasted into master, and the model evolves. Now, with conveyors, my process has some challenges currently. Ctrl+C, Ctrl+v works fine for the raw geometry (most of the time), but photo eyes, stations, DP's and such don't like this approach. They will exist in the tree, but the view will not draw them, and system console rest errors will ensue. Inserting the objects into a container object seems to work ok, but I'm not sure how they would act when removing them from the container once they get to the destination model (master). .t tree files don't seem to work well for conveyors with all of the DP's, etc. either.
It seems as though project timelines continue to decrease and model sizes continue to increase, so I think if a better more streamlined approach exists to consistently and predictably get sizable chunks of logic plumbed objects from one environment into another, I'd certainly be interested in understanding it. Any feedback welcomed, thanks!
Jim
