Search the Community
Showing results for tags 'sets'.
Found 1 result
Steve and I have been using poses in models to compose larger models -- even whole sets -- from smaller models. This is very useful to avoid creating multiple copies of mesh, as well as allowing an easy way of turning on and off various parts of the model. Here are the requirements that we had when the pose idea came up: Avoid having multiple copies of the same mesh. If there are 18 chairs in the set, there should not be 18 copies of the mesh in some model. Ideally, they need to be configurable for different situations. For example, we don't want a separate set for the coffee shop before it opens (less clutter) and after (more supplies, etc. laying around and on shelves). You need to be able to turn things on and off. The sets and large models need to be reusable. That is, you can create a new choreography, drag in a model, maybe change a couple of pose values, and be ready to animation. However, we have run into two show stoppers for this technique, which we outlined in this post. Because of that, we may need to resort to a plan B. Which we don't have! So I wanted to ask everyone: How do you create large sets or large models? Agep mentioned he did the Nidaros Cathedral by doing it "in an action (action objects), so when in the chor I simply drag and drop the action onto the basemodel", and "I sometimes merges two or more models when they are finished, so they are total ends at 30-60K". John Bigboote said of his SOCCER STADIUM: "it is assembled in an action... many parts are reused dozens of times- [ ... ]. I keep my splining real minimal, I keep expecting A:M to 'hit a wall' and be unable to accept any more, but it keeps allowing more and more models to be added via the action." However, on his MANHATTAN post, he said: "No duplicator wizard used, just good old copy and paste and heavy usage of action objects." Any other ideas, or clarifications on those existing ideas? Or problems you've run into? Thanks! Chris