Hi all, First off, Pyglet is brilliant - thanks to all contributors!
Now, I was wondering about the relative costs of the different ways of updating a vertex list. As an example, I am making a game where objects (read spaceships) move through 3D space and leave a fading trail behind them, as a HUD element. I have implemented this with a batched, indexed, vertex list which acts as a fifo -- new point comes in, old last point is replaced, indexes shift one place to the left. This means reading all indexes and storing them back, and updating one vertex in the list. Another way would be to keep a local, python list in the application, do the shifting in python and then just store everything back in the vertex list (which would not need to be indexed). These operations have to be done for each frame (so I am using '/ stream' as a hint). Does anyone have recommendations as to which method might be reasonably expected to work faster? Thanks Nikos --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
