 | | | Instantiate - Bad? | Instantiate - Bad? 2005-03-03 - By Piotr Twardo
Back
Instantiate - Bad?A bit OT...
They should really improve the performance of managing large object count
scenes, XSI will crawl even with 3000 of 6 poly cubes, the poly count is not as
important here. I had a serious problem when I imported thousands of curves
from rhino (IGES). When they were imported as eps (single object) the
performance increase was incredible.
Peter
-- -- Original Message -- --
From: Benjamin Huber
To: XSI@(protected)
Sent: Wednesday, March 02, 2005 10:41 PM
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><TITLE>Instantiate - Bad?</TITLE>
<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.2180" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>A bit OT...</FONT></DIV>
<DIV><FONT face=Arial size=2>They should really improve the performance of
managing large object count scenes, XSI will crawl even with 3000 of 6 poly
cubes, the poly count is not as important here. I had a serious problem
when I imported thousands of curves from rhino (IGES). When they were imported
as eps (single object) the performance increase was incredible.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Peter</FONT></DIV>
<BLOCKQUOTE dir=ltr
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=bhuber@(protected) href="mailto:bhuber@(protected)">Benjamin Huber</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, March 02, 2005 10:41
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> RE: Instantiate - Bad?</DIV>
<DIV><BR></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> </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 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> </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> </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>
|
|
|