On Wed, Sep 17, 2008 at 12:49 AM, Lucio Torre <[EMAIL PROTECTED]> wrote:
>
> during pyweek i had some issues with pyglet.
> first, using framebuffer objs and vertex lists caused a memory error
> somewhere.
An example demonstrating the problem would be helpful. pyglet doesn't
know anything about FBO's, so you might be to blame for that one ;-)
> then, my machine gives segmentation fault 1 every 3 times while
> starting our game. it just happens on my machine. i think sound has
> something to do (ubuntu64bits)
>
Again, please post a complete non-working example.
> then, using pyglet.graphics draw gave me some issues of flicker and
> strange problems (sometimes it looked like a vertex was missing).
>
> i had the following code:
>
> pyglet.graphics.draw(4, GL_QUADS,
> ("v2f", np),
> ("t2f", [a,b,c,d,e,f,g,h[),
> ("c4B", [255,255,255,self.alpha]*4),
> )
Could be a problem with data getting garbage collected before the
driver is finished with it. (Looking at the code, that's almost
certainly the case). Could you post a complete example so I can
verify the fix?
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
-~----------~----~----~----~------~----~------~--~---
