> > I don't even know _what_ error you were getting on the "vertex" part. > Please try to be a _little_ more helpful with your bug reports. They > are appreciated, but not when I don't have a clue as to what you're > trying to report.
ok, next time i wont even mention things that i dont have the time to give a full report. i do think its your loss, but your choice. >> lets do the other way around. what should i get to test it? i know how >> i can reproduce this inside the game, but i dont know what will happen >> if i start to cut other parts. if it still fails, ill try to get an >> example. > > I imagine you should be able to copy the draw call out of your game > into a bare pyglet program, possibly with some simple hardcoded data > to replace your scene data. If that doesn't reproduce the bug, throw > it in a loop to increase memory pressure. Failing that, point me to > the whole source (usually it takes me longer to isolate the bug than > you, as you know your way around your own code base better than I). > 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 even included the images just to be sure. the vertices dont move, and i dont clear the screen so you can see the trace of errors. if you change a line from False to True it will do the same drawing using glBegin/glEnd, but without errors. Lucio. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
