Re: Dynamic Object paging
Jason Williams (jason++at++cerebus.cambridge.com)
Wed, 26 Mar 1997 09:50:26 -0500
On Mar 25, 4:17pm, Elizabeth Smith wrote:
> Subject: Re: Dynamic Object paging
> On Mar 14, 9:00pm, Jason Williams wrote:
> > Subject: Dynamic Object paging
> >
> >
> > We have a situation, where we need to support potentially thousands of
> dynamic
> > objects which will come and go from our scene. We wanted to subclass
various
> > pfNode types to represent our dynamic objects. The question is, since
> pfNodes
> > need to have seperate memory copies maintained, would there be alot of
> overhead
> > when using a huge number pfNode types which are created and deleted fairly
> > often?. What if they weren't in the scene graph but the geometry was
culled
> > and drawn by a different method, but the pfNodes are used to create the
gsets
> > in seperate cull and draw processing? Should we abandon the pf class
objects
> > altogether for representing our dynamic objects in favor of pr defined
> objects?
> >
> >
> > Thanks in advanced,
> >
> > Jason Williams.
> >
> >
>
> Hi,
>
> Has anyone told you about Paradigm's Performer-based product
> Vega? Vega can handle the sort of problem you describe. Although I don't
> know your specific application, it may be that the Vega modules
> Vega DIS and Vega LADBM (large area database management)
> are relevant. Or just the basic Vega package may give
> you what you need.
>
> Have a look at our web pages: http://www.paradigmsim.com
> in particular the page
>
> http://www.paradigmsim.com:80/vega.html
>
>
> Vega users can still drop down to Performer level
> programming as well as OpenGL/IRISGL if necessary.
>
> If you think you might be interested or have specific questions,
> please get back in touch with me.
>
>
> --Elizabeth Smith
> Vega Engineering Manager
>
Thanks Elizibeth,
I have used Vega quite extensivly, however Vega uses Performer node
types directly to accomplish the dynamic motion of objects. We would then have
the same problem with Vega, as with performer. I have extensive experience
with Performer as well. We intend on creating our own capability based on top
of Performer, such that we can tune it ourselves. It is not a question of what
API to use, Performer is the API we are using. It is a question whether the pf
library class types are efficient when there are potentially 10,000 objects,
because pf objects need to copy themselves between app, cull, and frame, or
whether we need to use are own pr class objects.
Jason Williams.
Cambridge Research.
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
Submissions: info-performer++at++sgi.com
Admin. requests: info-performer-request++at++sgi.com
This archive was generated by hypermail 2.0b2
on Mon Aug 10 1998 - 17:54:57 PDT