that's the beauty of it: you choose! ;) in this example, I was trying a similar case as was discussed with cubes so in this case, it would be stupid to build first loads of cubes and then merge them in this particular case, you would, if you would use my demo code, simply alter the uv's of the source cube during the loop and offset its position. See this test more as a stress test rather than what you would usually do.
John for instance, he makes a city add to a container --> pass the whole micmac to the merge class. Thats the most common use of it. if you would use PathDuplicator, and pass a tree, and a container, you could pass this container to the class and name it MyForest... Fabrice On May 11, 2011, at 6:02 PM, rjgtav wrote: > Well, was checking your example, and i have a question. Why do you apply the > merge so many times? Wasnt it supposed to merge only one time? Or do you need > to merge again each time you move/rotate an already merged object?
