no, you are right.  i just finished (for now) converting my xwing files
to plain pov and uploaded them to the star wars pov site.  they should
be up soon.  in the package is an image with six xwings, all with
different squad colors and numbers and with different dirt, wings open
or closed, canopy open or closed, etc.  like most include files, there
are variables that the user declares and then includes the inc. 
however, i used two meshes and those are included only once in the
user's scene file.  i found that parsing after the first model was only
about 4 or 5 seconds.  so the slowdown is due to my meshes and patches.

Jamie Davison wrote:
> 
> \On Sat, 15 Jul 2000 14:38:51 +0200, Zeger Knaepen wrote...
> > > > Oh, yeah...  The stats:
> > > >
> > > > 2619 frame level objects
> > > > Peak memory used: 9602538 bytes
> > > > Time For Parse: 3s
> > > > Time For Trace: 4h 40m 14s
> > > > GUI-priority: Highest
> > > > Render-priority: Lowest
> > > > On a PIII 450 with 64 MB RAM under W98SE
> > >
> > >
> > > how did you get your parse time so low with so many objects in the
> > > scene?  are there any meshes or patches?  my current object count is
> > All CSG.  No height_fields, no isosurfaces.  I don't know how it can be
> > parsed so fast.  I don't really care, actually :-)
> >
> > > over 1300.  you've got double that but mine takes 15 sec to parse.
> > > hmmmm...
> > Strange...  Maybe becaused I used a lot of loops and some macros (for the
> > armor plating)?
> 
> The difference in parse time could easily be due to the fact that Ryan
> has used patches for the main hull of the X-Wing.  Depending on the
> subdivision settings used, patch objects can take ages to parse (I speak
> from experience :)
> 
> I could be wrong, of course <grin>
> 
> Bye for now,
>      Jamie.

Post a reply to this message