Hi, I don’t know how much of this is usefull because of super_buffers, but I’ve been thinking about something to implement in my engine (a layer), that I guess it would be nice to see as an extension: texture_buffers
OK, since buffers and textures are all the same, I tought why to have buffers and textures? And not just textures? For example, a GL_RGBA8 would be a 32bit RGBA frame buffer… And a LUM8 or ALPHA8 could work as a stencil buffer and so on (more texture formats would have to be created)
Now, the thing is, imediatly after doing this:
everything would be written to the texture (mip map level 0). If the texture was RGBA4 then it would be like drawing to a 16bit RGBA frame buffer. And if the texture was 1024x768, the viewport would also automaticly change to 1024x768.
After that command, everything would draw to that texture, without a depth/stencil buffer.
For that you would have to:
Of course, there would be some limitations because of viewport size and such… Another thing you could do is:
I assume that clearing (glClear, glClearDepth) would work on the textures…
For example, rendering to a mip map of a texture:
glBindTBufferMip(GL_COLOR, texIDCubeFaceY, 1);
Of course, most hardware would not support a stencil of LUM16 or whatever, but that could be like an extension string, letting us know of what combinations were possible…
I prefer this kind of API than the super_buffers… Of course the superbuffers is more powerfull, but a bit more “deselegant”…