Mailing List
Home
Forum Home
Softimage
Carrara
trueSpace
Dir3d-l
Maya - a powerful 3D animation and visual effects software
Macromedia Flash Development
Subjects
Cameras
scaleDown command
black out solved
Aircraft Tutorial
Mathematical XYZ ?
Its done This vs That
Its done first week
recommendations for screen video captures?
3DExplorer "Oddity "
New Director
ProTeam renewals
Fuel 's new websites (X post)
Blue peter create a make toy
targeting groups question
XPost: Shockwave 3D game ( sort of )
RES: RES: RES: Fish Modeling
Emitting particles from object intersection
Fuel 's new websites (X post)
Texturing
Big Break Contest Videos
New Plugins
Models and Texture on my updated site
Error Installing Patch tS6 6
Plasma?
Looking for Inspiration
Weird EMail Q
It 's done first week ?
Cherry not cranberry
New game
Camera Animation Problem
Particle plugins?
 
Instantiate - Bad?

Instantiate - Bad?

2005-03-02       - By Wayne Williams

 Back
Reply:     1     2     3     4     5     6     7     8     9     10  

Hey Sean,
I'm not sure if the unfrozen hierarchies of the parent objects are
propogated to the instances but if that is the case perhaps a freeze of
the parent objects to clear up their history stack might speed things up
a bit. Again, unsure about this. Anyone?

  -- --Original Message-- --
  From: owner-xsi@(protected) [mailto:owner-xsi@(protected)]
On Behalf Of Pollack, Sean
  Sent: Wednesday, March 02, 2005 3:40 PM
  To: XSI@(protected)
  Subject: Instantiate - Bad?
 
 


  I haven't found all the landmines yet in XSI and hit a bunch in
a recent job.

  Is instantiating a model with lots of pieces a bad idea?
  Seems like my performance is in the toilet.

  If there is a lot of geometry to reuse, is it recommended to go
with referencing and let it be at that and steer clear of instances?

  S


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2523" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=070580221-02032005><FONT face=Arial color=#0000ff size=2>Hey
Sean,</FONT></SPAN></DIV>
<DIV><SPAN class=070580221-02032005><FONT face=Arial color=#0000ff size=2>I'm
not sure if the unfrozen hierarchies of the parent objects are propogated to
the
instances but if that is the case perhaps a freeze of the parent objects to
clear up their history stack might speed things up a bit. Again, unsure about
this. Anyone?</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
 <DIV></DIV>
 <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
 face=Tahoma size=2>-- --Original Message-- --<BR><B>From:</B>
 owner-xsi@(protected) [mailto:owner-xsi@(protected)] <B>On Behalf Of
 </B>Pollack, Sean<BR><B>Sent:</B> Wednesday, March 02, 2005 3:40
 PM<BR><B>To:</B> XSI@(protected)<BR><B>Subject:</B> Instantiate -
 Bad?<BR><BR></FONT></DIV><!-- Converted from text/rtf format --><BR>
 <P><FONT face=Arial size=2>I haven't found all the landmines yet in XSI and
 hit a bunch in a recent job.</FONT> </P>
 <P><FONT face=Arial size=2>Is instantiating a model with lots of pieces a bad
 idea?</FONT> <BR><FONT face=Arial size=2>Seems like my performance is in the
 toilet.</FONT> </P>
 <P><FONT face=Arial size=2>If there is a lot of geometry to reuse, is it
 recommended to go with referencing and let it be at that and steer clear of
 instances?</FONT></P>
 <P><FONT face=Arial size=2>S</FONT> </P></BLOCKQUOTE></BODY></HTML>