Forums - Framebuffer texture not preserved if larger than 256x256

1 post / 0 new
or Register
Framebuffer texture not preserved if larger than 256x256
jorgediogo
Join Date: 31 Jan 13
Posts: 1
Posted: Thu, 2013-01-31 03:55
Top

Hi,

I came across this problem on a Nexus One with an Adreno 200, running Android 2.3.6. This has been tested in other Android devices without problems including an HTC Desire S with an Adreno 205 chip.

If a framebuffer with a texture larger than 256x256 is created and used as an offscreen texture (in order to be updated across multiple frames), its contents appear trashed on each new frame.

The code is plain vanilla OpenGL ES2.0 code for creating a color-only framebuffer and blitting there. I do not call glClear() after the glBindFramebuffer() for the framebuffer or it would erase the frame which is not desired - the idea is to accumulate into the texture across frames.

I found that textures of any size smaller than 256x256 work without problems: their contents are preserved across frames.

Do you know if this is a known behavior of the chip? Is there any workaround for this problem?

Thanks for any info - not being able to use offscreen accumulation textures is quite a problem for this project...

Best Regards, Jorge

  • Up0
  • Down0

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.