6 replies to this topic

[phrogger]

I assume there is no way for a pixel shader to write to a texture despite the ability to read from multiple textures. So, what's the easiest way to get any type of output? I envision having to render to texture or a pbuffer and accessing the resultant texture/pbuffer as an array of data.

Any other ideas?

[anubis]

as soon as the new render target extension is in the drivers of ati and nvidia things get easier but right now using a pbuffer for a render to texture is the only choice you have. anyway, why do you need to do this ?

[DANNER]

You can use the classic method of rendering with your pixel shader to the back buffer and use copyTexSubImage to copy the backbuffer contents to a texture. This is probably easier than rendering using a pbuffer and copying it contents to the texture. The only time using the backbuffer will not work is if it's dimensions are less than the texture.

If you're going the pbuffer route, you may as well use the WGL_ARB_render_texture extension.

Hopefully the ARB super buffer extension will be resolved soon (and in a way that works well of course.)

[anubis]

well, WGL_ extensions bind you to windows...

[anubis]

i'd wait for this... http://www.opengl.org/resources/features/G...nder_target.txt

[DANNER]

anubis said:

i'd wait for this... http://www.opengl.org/resources/features/G...nder_target.txt

Yes...that one of many proposals that are being considered by the ARB super buffers working groups. This particular one had some problems with it and others are being considered now.

[anubis]

url ?
i'm kind of behind those things due to my lack of motivation :)