On Mar 8, 10:07 pm, Richard Jones <[EMAIL PROTECTED]> wrote: > On Sun, 9 Mar 2008, Ben Sizer wrote: > > > Even a very trivial implementation of > > glBegin/2 triangles/glEnd per sprite should still do far better than > > 13fps with under 300 sprites. > > Not when you're running Python code through ctypes.
This doesn't change the fact that there's nothing intrinsically wrong with blit(). It may not be the fastest performer available, but for most people it will suffice. All I'm worried about is giving people the false impression that they can't expect blit() to perform reasonably, when it's clear that if you just run with the -O flag set, it'll more than likely be fine. (I get about 120fps with 250 blits per frame.) -- Ben Sizer --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
