Re: glDeleteHandle of pfTextures

New Message Reply Date view Thread view Subject view Author view

From: Jenny Zhao (zhz++at++dandan.engr.sgi.com)
Date: 04/06/2000 14:48:27


On Apr 6, 2:34pm, Angus Dorbie wrote:
> Subject: Re: glDeleteHandle of pfTextures
> I think I may have been mistaken about what happens on applying a
> pfTexture with a deleted gl handle, we're looking into it & will let you
> know if the handle is recreated.
>
> Make sure you have a null pointer though, you still have to subload
> again to avoid the sudden download hit.
>
> Your observation about the geostates is correct, but like I said that
> may be based on a flasehood from me.
>
> christopher.g.dorosky++at++lmco.com wrote:
> >
> > I don't understand.
> >
> > Does this mean that it is necessary to redo the geostates(that reference
> > that texture) or not? This could be a horrendous performance hit.
> > If not, how will the texture know where to go?
>
> >
> > If this is a sloppy approach, does performer provide a clean approach?
>
> This is a loaded question :-)
>
> If Performer offered an alternative I'd have told you about it by now.

Texture deletion is definitely a complicated problem in a multiprocessing
and multipipe application.
Chris, let's take this off-line and help you work out your issues.

If people are interested, we will post a summary in the future.

Thanks!

>
> CHeers,Angus.
>
>
> --
> For Performer+OpenGL tutorials http://www.dorbie.com/
>
> "In the middle of difficulty lies opportunity."
> --Albert Einstein
> -----------------------------------------------------------------------
> List Archives, FAQ, FTP: http://www.sgi.com/software/performer/
> Submissions: info-performer++at++sgi.com
> Admin. requests: info-performer-request++at++sgi.com
>-- End of excerpt from Angus Dorbie

-- 
Jenny Zhao        zhz++at++engr.sgi.com     650 933-5091	IRIS Performer Manager


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Thu Apr 06 2000 - 14:48:31 PDT

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