On Aug 24, 5:07 am, mclovin <[email protected]> wrote: > Anyways, I am just horribly dissappointed by Pyglet. I used it for > about a year and always just excused some of its performance lags > because it was a scripting language. but a scripting language in a > browser kicks Pyglet's *$$
It's not pyglets fault really. 1) ctypes FFI calls are slow 2) Chrome JS isn't really a "script" language, it gets compiled down to x86/x64 machine code However, 7500 particles is not so much. Doing the draw loop in C I get to 20'000 particles @ 60FPS. See http://codeflow.org/particles.tgz, which in essence is void quad_draw(Quad* quad){ glPushMatrix(); glTranslatef(quad->x, quad->y, 0); glRotatef(quad->rotation, 0, 0, 1); glScalef(quad->size, quad->size, 0); glBegin(GL_QUADS); glTexCoord2i(0, 0); glVertex2i(0, 0); glTexCoord2i(1, 0); glVertex2i(1, 0); glTexCoord2i(1, 1); glVertex2i(1, 1); glTexCoord2i(0, 1); glVertex2i(0, 1); glEnd(); glPopMatrix(); } over and over again. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
