On Thu, Aug 27, 2009 at 6:54 AM, claudio canepa<[email protected]> wrote: > > > On Wed, Aug 26, 2009 at 3:56 PM, Tristam MacDonald <[email protected]> > wrote: >> >> I don't hit *any* of the paths you provided print statements for. >> -- >> Tristam MacDonald >> http://swiftcoder.wordpress.com/ >> >> > > Thanks for the tests! > Then in yours systems pyglet wasn't trying to use glMultiDrawElements, so > runs the same code as if in my system I put the workaround in effect. > > To any one trying the Richard Thomas script, please try also to run it using > the modified pyglet/graphics/vertexdomain.py ( no console prints means 'not > using glMultiDraw' ). > That will tell if only the combination using glMultiDraw and buffer is not > VBO fails. > > note to future: why modern hardware as Tristam ati radeon 4870 would not use > glMultiDrawElements ?
Hello everyone I had a quick look at this issue. The problem is that pyglet is passing offsets into a VBO to glMultiDrawElements, which is not permitted -- these arrays have to be in ordinary vertex arrays. This is why disabling VBOs in pyglet is a workaround for the problem. Committed fixes (always copying the vertex data into a C array) for trunk (r2524) and maintenance (r2523). Cheers Alex. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
