On Feb 26, 9:58 pm, DR0ID <[email protected]> wrote: > I think it is just black at initialization. You need some random values > in the initial texture to work. (Vista and some other OS/newer driver > seem to null the texture memory, so no random values are present as in > older/other systems/drivers).
Yeah but the point kinda is that if you can't attach multiple (possibly non RGBA) textures to a framebuffer, stack and restore nested opengl state (also of programs, framebuffers, textures etc.) and wrap this up in a convenient and short semantic and syntax, the going gets kinda though very soon. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
