On Tue, Sep 16, 2008 at 11:20 AM, Alex Holkner <[EMAIL PROTECTED]> wrote:
> 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 ;-)
its possible, but why would i get the error on the vertex part?
> Again, please post a complete non-working example.
the thing with this is that i cant. we have 5k lines of code, we
probably did write 10k lines and erased most of them later. i just
wanted to inform on some experiences. getting to reproduce this in a
small form could take forever. maybe the report would trigger
something that would help you.
ill try to get this, but i cant promise.
>
>> 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?
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.
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
-~----------~----~----~----~------~----~------~--~---
