On Mon, Jan 21, 2008, Ian Romanick wrote: > | It does work reasonably well. No framebuffer object yet but a shared > | context and 3 clients, two draw each their mesh and a third swaps the > | buffers regularly. Lots of interesting synchronization problems ahead :) > | Right now I only use a semaphore to lock the context. > > Couple bits of advice...right now framebuffer objects are, technically, > sharable. It's painful for drivers, and the ARB is aware of this > problem. The best bet is that FBOs will *not* be sharable in the next > version of OpenGL, but textures (naturally) and renderbuffers will be. > This is certainly the option that I prefer. > > My advice is to just share the textures and renderbuffers that make up > the FBO, and create a fresh FBO in each context.
Thanks, note that in my case I plan to share FBOs between processes, but not between contexts. There is only one context, owned by the X server, and the clients share this indirect context, in which they each create one FBO. Is this case also painful to the driver? -- Johan Bilien <[EMAIL PROTECTED]> ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
