From: Christian Stock (cstock++at++unimelb.edu.au)
Date: 09/29/2003 19:08:32
Thanks very much for the replies.
No, I'm not loading in between drawFrame, I'm loading everything at
start-up in one go. I can't share any geometry either, and I'm certainly
running out of memory / swap space. I tried converting to pfb files also,
and while it's maybe a bit faster, it still is much to slow.
>I've seen something similar before.
>
>Performer tries to reuse Performer state (I know for sure from the pfb
>loader); but if there are user data attached to that state (texture,
>material or whatever), it will be seen as a separate object and not
>shared; also the list with all (unique) state objects seen (wich are
>used as potential future candidates for sharing) will grow larger and
>larger which explains the time increase.
I think this is actually exactly what's happening. This explains the
mysteriously high demand of memory and also the decreasing loading speed.
It even seems as if both the obj and pfb loader at least load the textures
for every object or file, although the textures should really be shared.
Does performer load textures / materials once per file or for each object
in every file (ie is the slowdown it file or object dependent)?
Also, is there a known quick fix?
I'll have a look at the performer file loaders myself now, but any help
would be very much appreciated.
Christian
This archive was generated by hypermail 2b29 : Mon Sep 29 2003 - 19:13:38 PDT