A model node in a Reference model 2005-05-04 - By Oz Adi
Back
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@(protected)
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@(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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859 (See http://iso-8859.ora-code.com)-1">
<META content="MSHTML 6.00.2900.2627" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>thanks!</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>there's no special reason for it.. I just wanted
it
to be more organised...</FONT></DIV>
<DIV><FONT face=Arial size=2>but I guess I would give it up.. :)</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Oz.</FONT></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT:
#000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">-- -- Original Message -- -- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=3dbernard@(protected) href="mailto:3dbernard@(protected)">Bernard
Lebel</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=XSI@(protected)
href="mailto:XSI@(protected)">XSI@(protected)</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, May 04, 2005 4:58
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: A model node in a Reference
model</DIV>
<DIV><BR></DIV>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="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204
,204) 1px solid">
<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
onclick="return top.js.OpenExtLink(window,event,this)"
href="http://www.coolcalb.com"
target=_blank>www.coolcalb.com</A></FONT></DIV>
<DIV> </DIV></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML>
|
|
