Re: Performer Display Lists
John Rohlf (jrohlf++at++tubes)
Fri, 10 Mar 95 18:01:20 PST
>
> > The main reason that I am asking, is because it appears to work, even
> > when configured for the 3 process (PFMP_APP_CULL_DRAW) model and other
> > process models where the APP and CULL are separated. I am calling the
> > display listable commands right after pfFrame().
>
> My mistake. My function was inadvertently installed as a cull callback,
> rather than being in the APP process.
>
> > While I'm on the subject of Performer Display Lists, how is the
> > multibuffering in Performer's display lists handled? I read in the
> > SIGGRAPH '94 paper by John Rohlf and Jim Helman how that 3 display
> > lists are kept in LOCK mode to insure frame accuracy. Does this imply
> > 3 pfDispLists are created by libpf, or that libpr's display list
> > mechanism has some built-in way of handling the multibuffering?
>
> I'm still curious about how performer handles multibuffering of display
> lists..
There are just 3 separate pfDispLists which the CULL and DRAW use
to communicate. We have an open bug to capture libpr commands in the
APP and frame-accurately render them. I'm not sure this will make it
into 2.0 though.
This archive was generated by hypermail 2.0b2
on Mon Aug 10 1998 - 17:51:03 PDT