> I've also tried to pin-point where the coredump occures and it turns > out to be in pyglet.graphics.vertexdomain.IndexedVertexDomain.draw on > the first glDrawElements > because the arguments are (4, 42, 5125, 0). Having indices being 0 is > certainly not the right thing ! :-) > I still need to figure out why the self.index_buffer.ptr is 0.
Turns out that IndexedVertexDomain.index_buffer is a MappableVertexBufferObject in my case and its ptr attribute is inherited straight from AbstractBuffer and never touched. Instead it touches another attribute, data_ptr. As VertexArray, who also inherit from AbstractBuffer, uses the ptr attribute, I thought that changing the implementation to use ptr instead of data_ptr would fix the problem. It does produce a reasonable value (as I now get glDrawElements(4, 42, 5125, 27308448)) but that didn't fix the crash. :-( Any ideas about how to continue debugging this would be appreciated. Cheers, Olivier -- 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.
