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-03       - By Pollack, Sean

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

Good idea, thanks!

-- --Original Message-- --
From: owner-xsi@(protected) [mailto:owner-xsi@(protected)]On Behalf Of
Benjamin Huber
Sent: Wednesday, March 02, 2005 4:42 PM
To: XSI@(protected)
Subject: RE: Instantiate - Bad?


We had a case once where generating thousands of instances of a fairly low-poly
(50 faces range) object would slow XSI
to a crawl. creating plain duplicates and merging them all in one huge object
solved the issue. aparently keeping track
of thousands of individual objects with trans/rot/scale information is more
computationally intensive than having one object
with tens of thousands of faces.

so, if that's possible in your case, merge your original object pieces into one
object, freeze it (thus getting rid of a whole
lot of transforms), and *then* generate the instances. or, even better, create
duplicates of your merged object and merge
all of them together. although, obviously, you won't be able to individually
animate the duplicates any more then. depends on
your scene.

hope that helps,

-ben
---
ben huber (x83291)
ilm digimatte
serious like ninjas
---

-- --Original Message-- --
From: owner-xsi@(protected) [mailto:owner-xsi@(protected)]On Behalf Of
Pollack, Sean
Sent: Wednesday, March 02, 2005 12: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>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859 (See http://iso-8859.ora-code.com)-1">
<TITLE>Instantiate - Bad?</TITLE>

<META content="MSHTML 6.00.2900.2523" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=979310615-03032005><FONT face=Arial color=#0000ff size=2>Good
idea, thanks!</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
 <DIV class=OutlookMessageHeader 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>Benjamin
 Huber<BR><B>Sent:</B> Wednesday, March 02, 2005 4:42 PM<BR><B>To:</B>
 XSI@(protected)<BR><B>Subject:</B> RE: Instantiate -
 Bad?<BR><BR></FONT></DIV>
 <DIV><SPAN class=507193421-02032005><FONT face=Arial color=#0000ff size=2>We
 had a case once where generating thousands of instances of a fairly low-poly
 (50 faces range) object would slow XSI</FONT></SPAN></DIV>
 <DIV><SPAN class=507193421-02032005><FONT face=Arial color=#0000ff size=2>to
a
 crawl. </FONT></SPAN><SPAN class=507193421-02032005><FONT face=Arial
 color=#0000ff size=2>creating plain duplicates and merging them all in one
 huge object solved the issue. </FONT></SPAN><SPAN
 class=507193421-02032005><FONT face=Arial color=#0000ff size=2>aparently
 keeping track</FONT></SPAN></DIV>
 <DIV><SPAN class=507193421-02032005><FONT face=Arial color=#0000ff size=2>of
 thousands </FONT></SPAN><SPAN class=507193421-02032005><FONT face=Arial
 color=#0000ff size=2>of individual objects with trans/rot/scale information
is
 more computationally intensive </FONT></SPAN><SPAN
 class=507193421-02032005><FONT face=Arial color=#0000ff size=2>than having
one
 object</FONT></SPAN></DIV>
 <DIV><SPAN class=507193421-02032005><FONT face=Arial color=#0000ff size=2
>with
 tens </FONT></SPAN><SPAN class=507193421-02032005><FONT face=Arial
 color=#0000ff size=2>of thousands of faces.</FONT></SPAN></DIV>
 <DIV><SPAN class=507193421-02032005><FONT face=Arial color=#0000ff
 size=2></FONT></SPAN>&nbsp;</DIV>
 <DIV><SPAN class=507193421-02032005><FONT face=Arial color=#0000ff size=2>so,
 if that's possible in your case, merge your original object pieces&nbsp;into
 one object, freeze it (thus getting rid of a whole</FONT></SPAN></DIV>
 <DIV><SPAN class=507193421-02032005><FONT face=Arial color=#0000ff size=2>lot
 of transforms), </FONT></SPAN><SPAN class=507193421-02032005><FONT face=Arial
 color=#0000ff size=2>and *then* generate the instances. or, even better,
 create duplicates of your merged object and merge</FONT></SPAN></DIV>
 <DIV><SPAN class=507193421-02032005><FONT face=Arial color=#0000ff size=2>all
 of them together. although, obviously, </FONT></SPAN><SPAN
 class=507193421-02032005><FONT face=Arial color=#0000ff size=2>you won't be
 able to individually animate the duplicates any more then. depends
 on</FONT></SPAN></DIV>
 <DIV><SPAN class=507193421-02032005><FONT face=Arial color=#0000ff size=2
>your
 scene.</FONT></SPAN></DIV>
 <DIV><SPAN class=507193421-02032005><FONT face=Arial color=#0000ff
 size=2></FONT></SPAN>&nbsp;</DIV>
 <DIV><SPAN class=507193421-02032005><FONT face=Arial color=#0000ff size=2
>hope
 that helps,</FONT></SPAN></DIV>
 <DIV><SPAN class=507193421-02032005><FONT face=Arial color=#0000ff
 size=2></FONT></SPAN>&nbsp;</DIV>
 <DIV><SPAN class=507193421-02032005><FONT face=Arial color=#0000ff
 size=2>-ben</FONT></SPAN></DIV>
 <DIV><SPAN class=507193421-02032005>
 <P><FONT face=Arial size=2>-<SPAN
 class=507193421-02032005>-</SPAN>-</FONT><BR><FONT face=Arial size=2>ben
huber
 (x83291)</FONT> <BR><FONT face=Arial size=2>ilm digimatte</FONT> <BR><FONT
 face=Arial size=2>serious like ninjas</FONT> <BR><FONT face=Arial
 size=2>---</FONT> </P></SPAN></DIV>
 <BLOCKQUOTE dir=ltr
 style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid;
MARGIN-RIGHT: 0px">
   <DIV class=OutlookMessageHeader 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 12: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></BLOCKQUOTE></BODY><
/HTML>