Neil, Setting the environment variable to disable-atlas does make the problem go away.
I'd like to see if we can get root cause on this issue. If we can pin it on something in the OpenGL driver, I can log it in QUAD and see if we can get it fixed in the next version of the IEGD driver. (If it is in fact an IEGD problem.) Regards, Chris On Wed, Jul 14, 2010 at 3:16 AM, Neil Roberts <[email protected]> wrote: > Chris Healy <[email protected]> wrote: > > > In my clutter application, some of my images are not showing up. > > (Just blank space instead of the image.) This started occurring after > > the following commit: > > > > cogl-atlas-texture: Try to do texture blits using an FBO > > Hrmm.. that's surprising. The atlas code does check for when the fbo > failed and it should fall back to use cogl_texture_get_data to migrate > the textures. However on GLES cogl_texture_get_data has a complicated > fallback to render the texture to the framebuffer and use > glReadPixels. This fallback has been broken for a while but it should > now be fixed in Clutter master. Perhaps you were hitting the broken > fallback path? If that's the case it would be good to know why it's > failing to set up an fbo with your driver however. > > > Is there an easy way of temporarily disabling this functionality to > > test out my theory without removing the code? (environment variable > > or API call) > > You can disable the atlas by setting the following environment variable: > > COGL_DEBUG=disable-atlas > > Regards, > - Neil >
_______________________________________________ clutter-app-devel-list mailing list [email protected] http://lists.clutter-project.org/listinfo/clutter-app-devel-list
