Re: PBuffers

New Message Reply Date view Thread view Subject view Author view

Rob Jenkins (robj++at++quid)
Wed, 5 Nov 1997 10:33:17 -0800


I dumped some thoughts on potential problems using pbuffers ( including the
BadAlloc error ) a while ago, it's in the archives for 08/97

The link for the archives is off the performer web page.

Cheers
Rob

On Nov 5, 11:32am, Mario Veraart wrote:
> Subject: Re: PBuffers
> >
> > I saw from the info-performer alias that some have been attempting to
> > render into a Pbuffer with performer. Have you gotten it to work?
> >
> > I've been having a little difficulty getting this to work myself. I've
> > been able to get performer to render into a motif window. But if I
> > switch that to a pbuffer, it dies in a call to XGetWindowAttributes
> > which is called from pfWindow::open.
> >
> > In your implementation, did you just do this:
> >
> > pipeWindow->setWSDrawable(0, p_buffer_drawable);
> >
> > This is all I did for the motif case but have the above problem when
> > trying to do this with a pbuffer.
> >
> > Are there other things you can suggest I check into?
> >
> > Thanks for any help,
> >
> > Wade
> >
>
> I have found a mail concerning pbuffers that contains a few URLs
>
> Mario
> -----------------------------
> Subject: Re: PixelBuffer on RE2 With irix6.4
> From: brianp++at++ra.avid.com
> Date: Fri, 16 May 1997 08:44:45 -0500
> To: Yann Argotti <Yann.Argotti++at++imag.fr>
> Reply-To: brianp++at++ra.avid.com
> Sender: brianp++at++ra.avid.com
> Cc: info-performer++at++sgi.com
>
> On May 15, 2:35pm, Yann Argotti wrote:
>
> > I want to make offcreen Rendering with an Onyx Re2 (2xR10000, 1 Gbytes
> for RAM
> > and irix 6.4). PixelBuffer solution appears the good way for that.
> >
> > My problem is that, when I create PBuffer with glXCreateGLXPbufferSGIX
> > (an OpenGL instruction), a "BadAlloc" error (ie: insufficient resources
> > for operation) stops the programme.
> >
> > I just try to create a PBuffer of 2x3 pixels, with a red, green, blue
> size
> > of 4, depth size of 23, in a single buffer mode and aPBuffer drawable
> type.
> > glXChooseFBConfigSGIX function gives me 3 suitable FBconfigs (I decide
> to use
> > the first one (the best) where GLX_MAX_PBUFFER_WIDTH_SGIX is 2048 and
> > GLX_MAX_PBUFFER_HEIGHT_SGIX is 1120).
> >
> > Also, I suppose having enought ressources to allocate this little
> PBuffer
> > and the solution, to solve current problem, is not very clear.
> > Is it a bug from me, from OpenGL or from Hardware ??
>
>
> As part of the SIGGRAPH '97 course on OpenGL and Window System Integration
> which I'm doing with Mark Kilgard one of the subjects I investigated was
> off-screen rendering methods, including pbuffers.
>
> Pbuffers are a pain to use. I think I finally figured them out though.
> Check out my notes on the subject at
> http://www.ssec.wisc.edu/~brianp/sig97/offscrn.htm
> See the "SGI Pbuffers" section.
>
> It explains the "BadAlloc" problem.
>
> Then, grab http://www.ssec.wisc.edu/~brianp/sig97/pbuffer.trz which contains
> pbuffer utility code and a demo program.
>
> Hope this helps.
>
> -Brian
>
> --
> --------------------------------------------------------------------
> Brian Paul Avid Technology Madison, WI brianp++at++elastic.avid.com
>
> =======================================================================
> List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com
>-- End of excerpt from Mario Veraart

-- 
________________________________________________________________
Rob Jenkins mailto:robj++at++sgi.com
Silicon Graphics, Mtn View, California, USA
=======================================================================
List Archives, FAQ, FTP:  http://www.sgi.com/Technology/Performer/
            Submissions:  info-performer++at++sgi.com
        Admin. requests:  info-performer-request++at++sgi.com

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:56:12 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.