On Mar 7, 3:06 am, "Richard Jones" <[EMAIL PROTECTED]> wrote: > blit() is definitely not designed for high performance. The new graphics > batch and related sprite functionality in pyglet 1.1 *is*.
How is blit() implemented? Even a very trivial implementation of glBegin/2 triangles/glEnd per sprite should still do far better than 13fps with under 300 sprites. I'd be wary about putting performance concerns into the documentation when this is unlikely to be the source of the problem. It looks like this was just the error-checking anyway. -- 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 -~----------~----~----~----~------~----~------~--~---
