render to texture question

yes, you can request a double buffered pbuffer (infact, I think you can request a double buffered pbuffer and upto 9 AUX buffers as well)

and no, you cant render to a texture and read from it as a texture source at the same time, at best it will be undefined, at worse Bad Things Will Happen (tm).

Keep in mind, that in its current state you dont really render to a texture, you render to a pbuffer and then for all intents and purposes alias a pbuffer to a texture ID to access it like a texture and frankly there isnt a sane way todo it.

btw, atm a glCopyTexSubImage2D call might be faster than using a pbuffer, as using a pbuffer requires a context switch which are expensive. Now, the new framebuffer object extension should remove that overhead nicely once one of the IHVs writes a driver which contains it [wink], but for now unless you need a framebuffer large than your window I'd stick with copying a texture.

We should start a petition for ATI and nvidia to make them damned framebuffer_object's :-p

-Dan

heh, well they are working on them, however NV wont release until they have them working and fully tested and ATI have a kinda pipeline going on with drivers as they are all WHQL certified, so when something comes out even if they wrote it right away you'd have a lead time of a couple of months before you get it.

Current thinking is that March would be the best bet for a driver release from at least ATI or NV, so its a case of wait and hope really [smile]