Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve have a rendering setup in which I write to a Frame Buffer object attached to a texture and the rendering itself also uses the texture I’m rendering to.
Is this generally a good idea? Could there be some strange issues involved here I’m perhaps not aware of?
This will result in undefined behavior, which means it may break with any future driver version, and behave differently on different hardware. To be on the safe side, you should never render into a texture which is currently bound (i.e. which could be possibly read and written to at the same time — this is the problem actually). Try making a copy of the texture, and render into that instead.
Take a look at the spec, specifially section 4.4.3 ‘Rendering When an Image of a Bound Texture Object is Also Attached to the Framebuffer’