kRogue: BTW, the workaround could be to use glClearBuffer() on a framebuffer attachment - albeit it's not cool but does essentially what you ask for. I can't help but feel that naming a function glClearBuffer{Sub}Data in the presence of glClearBuffer wasn't the wisest decision to make. Again, to the knowing developer it's not a problem but when seeing it the first time you start thinking.