Re: A model node in a Reference model

["Oz Adi" <oz(at)broadcast.co.il>]

thanks!

 

there's no special reason for it.. I just wanted it to be more organised...

but I guess I would give it up.. :)

 

Oz.

----- Original Message -----

From: Bernard Lebel

To: XSI(at)Softimage.COM

Sent: Wednesday, May 04, 2005 4:58 PM

Subject: Re: A model node in a Reference model

As far as I know, I would say no-no. Like overrides on cluster materials, chances are that you will never run into problems. However when they strike, it's hard to go back and you are stuck with it.
Problems you *may* encounter include corrupted scenes, refresh problems, screwed mixers, etc.

There is also another important factor to consider: if your pipeline make use of scripts to handle some tasks, then nesting models may prevent scripts from doing their job. Scripts that access the model property of objects and similar built-in attributes may find themselves pointed to the wrong object.

Any reason why you'd absolutely want two rigs under the same model?


My two cents
Bernard

On 5/4/05, Oz Adi <oz(at)broadcast.co.il> wrote:

before I do stupid things..

 

I got two characters, each with it's rig, under a seperate model node, for each one.

above them, there are a few more objects, that needs to referenced too, and there's a model node as the parent.

 

I want to have both charatcers in the same reference model, but I want each to have it's own mixer.

This is why they are both under a third model node...

 

Is what I am doing a big no no.. or are there no problems nesting these models?

 

I've tested it with two spheres.. and it worked fine.. but maybe with more complicated stuff... ??

anyone had a bad experience with that???

 

cheers,

Oz.

www.coolcalb.com