Jonathan Morton wrote:
>
> >The challenge with back and depth buffers is being able to allocate
> >additional space on the fly (when a window is resized for example). We
> >chose a static allocation method over shutting down the application
> >after it's already been running. If a good mechanism can be devised for
> >addressing that failure case, then it would be possible to consider
> >private back and depth buffers for multiple 3D windows.
>
> How about, "if there isn't enough VRAM, fall back to software
> rendering"? That's what Apple's implementation does, or at least
> used to.
Software renderers and HW renderers don't always generate the same
results. Some extensions are only available in one or the other. Also,
you'll hit a performance cliff.
-- /\
Jens Owen / \/\ _
[EMAIL PROTECTED] / \ \ \ Steamboat Springs, Colorado
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -
http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
