A model node in a Reference model 2005-05-04 - By Bernard Lebel
Back
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@(protected)> 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 <http://www.coolcalb.com>
>
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.<br>
Problems you *may* encounter include corrupted scenes, refresh problems,
screwed mixers, etc.<br>
<br>
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.<br>
<br>
Any reason why you'd absolutely want two rigs under the same model?<br>
<br>
<br>
My two cents<br>
Bernard<br>
<br><br><div><span class="gmail_quote">On 5/4/05, <b class="gmail_sendername"
>Oz Adi</b> <<a href="mailto:oz@(protected)">oz@(protected)</a>>
wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb
(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><font face="Arial" size="2">before I do stupid things..</font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">I got two characters, each with it's rig,
under a seperate model node, for each one.</font></div>
<div><font face="Arial" size="2">above them, there are a few more objects, that
needs to referenced too, and there's a model node as the parent.</font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">I want to have both charatcers in the same
reference model, but I want each to have it's own mixer.</font></div>
<div><font face="Arial" size="2">This is why they are both under a third model
node...</font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">Is what I am doing a big no no.. or are there
no
problems nesting these models?</font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">I've tested it with two spheres.. and it
worked
fine.. but maybe with more complicated stuff... ??</font></div>
<div><font face="Arial" size="2">anyone had a bad experience with
that???</font></div>
<div><font face="Arial" size="2"></font> </div>
<div><font face="Arial" size="2">cheers,</font></div>
<div><font face="Arial" size="2">Oz.</font></div>
<div><font face="Arial" size="2"><a href="http://www.coolcalb.com" target="
_blank" onclick="return top.js.OpenExtLink(window,event,this)">www.coolcalb.com<
/a></font></div>
<div> </div>
</blockquote></div><br>
|
|
