You´re right. The accumulation buffer flip policy is there only because it provides a "bare bones" fallback when everything else fails, usually due to a fairly old board and/or bad driver. For recent boards and drivers, the default flip policy works as expected, and even when it does not, the FBO policy, which is fairly snappy, usually works. I am going write a short discussion about flip policies on the pyprocessing wiki to make this clear.
Cheers, --Claudio On Oct 17, 3:01 pm, Tristam MacDonald <[email protected]> wrote: > 2009/10/17 Claudio Esperança <[email protected]> > > > > > From the log you sent, it looks like either your board does not > > support accumulation buffer (which is unlikely), or pyglet's > > get_best_config is unable to find a suitable context configuration > > that supports an accumulation buffer. I've seen one other message in > > pyglet-users discussion group about problems with this, but the > > solution is not clear. > > FYI, accelerated support for the accumulation buffer is very rare these > days. On pretty much all Macs, and a fair sprinkling of recent Windows > machines, requesting an accumulation buffer will cause software fallback. > > These days, one should be performing accumulation operations on a > framebuffer object, using shaders for the more complicated blending > operations. > -- > Tristam MacDonaldhttp://swiftcoder.wordpress.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
