Neil, Here's some additional information about my experience:
tag 1.1.4 does not exhibit this failure tag 1.2.10 exhibits this failure I have an example application that renders 10 parallel bars on the screen. All 10 bars are loaded from the same png. With the offending code, consistently, the first 5 bars will not be populated. (Just black space.) You mentioned that the fallback should be fixed in Clutter master. Is there a code submit post v1.2.10 that you are thinking of that would address this? You stated that perhaps I was hitting the broken path and that you would like to know why it was failing. Is there some debugging code you'd like me to run to help identify what the root cause is? >From what I understand, disabling "atlas" will be a performance hit? (Can you explain what this functionality is doing? I'm not familiar with "atlas") I will try the environment variable when I go in today and provide feedback. I am also willing to perform any other tests that might help me not have to disable the atlas functionality as performance is critical to us. 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
