• FEATURED
• FEATURED
• FEATURED
• FEATURED
• FEATURED

View more

View more

View more

### Image of the Day Submit

IOTD | Top Screenshots

### The latest, straight to your Inbox.

Subscribe to GameDev.net Direct to receive the latest updates and exclusive content.

# glCopyBufferSubData?

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

6 replies to this topic

### #1ak09  Members

Posted 18 May 2013 - 01:26 AM

From the specification,

void *glCopyBufferSubData(enum readtarget, enum writetarget,
intptr readoffset, intptr writeoffset, sizeiptr size);


glCopyBufferSubData copies part of the data store attached to readtarget to the
data store attached to writetarget. The number of basic machine units indicated by size
is copied from the source, at offset readoffset to the destination at writeoffset,
also in basic machine units.

It's not very clear, however, what's the meaning if readoffset, writeoffset and size, and how should them be used.

        glBindFramebuffer(GL_COPY_READ_BUFFER, fboSrc);
glBindFramebuffer(GL_COPY_WRITE_BUFFER, fboDst);


Any clue?

### #2Sponji  Members

Posted 18 May 2013 - 03:57 AM

The manual says those are specified in basic machine units, which is most likely bytes, just like in other opengl functions. Have you tried passing zeros for offsets, and the size of your buffer in bytes for the size? It should copy the whole buffer.

Derp

### #3ak09  Members

Posted 18 May 2013 - 07:40 AM

The manual says those are specified in basic machine units, which is most likely bytes, just like in other opengl functions. Have you tried passing zeros for offsets, and the size of your buffer in bytes for the size? It should copy the whole buffer.

I tried every reasonable combination.
Maybe it's important to say that I'm trying to copy an FBO to another (because I don't know if this function can deal with FBO's).

### #4ak09  Members

Posted 18 May 2013 - 07:41 AM

Yeah, it seems that I can't. FBO is not a buffer object.

### #5mhagain  Members

Posted 18 May 2013 - 11:07 AM

For copying FBOs glBlitFramebuffer is provided - see http://www.opengl.org/sdk/docs/man3/xhtml/glBlitFramebuffer.xml.

You could also maybe look at GL_ARB_copy_image - the bad news is that it's a GL4.3 extension and so may not be available on all of your target hardware.  Otherwise you may be able to do something with round-tripping through a PBO:

// note - these two PBO binds are intentionally the same buffer object
glBindBuffer (GL_PIXEL_PACK_BUFFER, intermediatePBO);
glBindBuffer (GL_PIXEL_UNPACK_BUFFER, intermediatePBO);

// read from source texture to PBO
glBindTexture (GL_TEXTURE_2D, sourceTexture);
glGetTexImage (GL_TEXTURE_2D, 0, GL_BGRA, GL_UNSIGNED_INT_8_8_8_8_REV, (void *) 0);

// write from PBO to destination texture
glBindTexture (GL_TEXTURE_2D, destTexture);
glTexSubImage2D (GL_TEXTURE_2D, 0, 0, 0, 0, 0, width, height, GL_BGRA, GL_UNSIGNED_INT_8_8_8_8_REV, (void *) 0);


All going well, that should run the copy entirely on the GPU, but does have the downside of requiring intermediate storage and an extra copy.

Edited by mhagain, 18 May 2013 - 11:12 AM.

It appears that the gentleman thought C++ was extremely difficult and he was overjoyed that the machine was absorbing it; he understood that good C++ is difficult but the best C++ is well-nigh unintelligible.

### #6ak09  Members

Posted 19 May 2013 - 02:35 PM

Hi, mhagain, thanks for the reply.
Yeah, my hardware can't deal with that you mentioned.
For the moment I'm wondering how good or bad is my current approach of copying a texture binded by some FBO into another binded by another FBO.
The method consists in clearing the destination texture and drawing the first one to the second, so I can make the copy even if dealing with different sized textures.

### #7mhagain  Members

Posted 19 May 2013 - 05:18 PM

Are you quite sure that you don't have glBlitFramebuffer?  If you're using FBOs then glBlitFramebuffer is part of GL_ARB_framebuffer_object (which from a pevious post it seems certain that you are using) so it would be a driver bug if you didn't have it.  If you're using GL_EXT_framebuffer_object then you should also check for GL_EXT_framebuffer_blit and use that if available.  In both cases you can specify a filter parameter for dealing with different sizes, if necessary.

Also in both cases, the PBO method would definitely work as that's GL2.1 functionality, and FBOs belong to a higher GL_VERSION.  I'd definitely encourage you to double-check your hardware's capabilities as they're almost certain to be higher than you seem to think.

It appears that the gentleman thought C++ was extremely difficult and he was overjoyed that the machine was absorbing it; he understood that good C++ is difficult but the best C++ is well-nigh unintelligible.

Old topic!

Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.