On Thu, Sep 18, 2008 at 1:35 AM, Lucio Torre <[EMAIL PROTECTED]> wrote:
> ok, i did it. took me forever. > the simple "copy the draw function out" didnt work. i removed > everything i could in the time i had, cocos included. > see: > http://code.google.com/p/pyglet/issues/detail?id=349 > I was able to reproduce this bug with the posted example. Rewriting the example to use a batch and instead update the added vertex list data does not cause the same visual artifacts - so the bug seems to indeed be with draw() function. On a side note, this makes me wonder why draw() for immediate rendering is part of the API and when it's even a good idea to use - since batched vertex lists are by far more optimal. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
