# OpenGL Locking and updating VBOs from a separate thread.

## Recommended Posts

Hi,

I am fairly new to opengl so my question is, if I have to lock/update a vertex buffer object from a spearete thread what would be the way to go? More specifically do I have to create a new context and bind it to that thread? or can I manage with the original context bound to the updating thread? Given that I have made sure this buffer will not be used in the current draw call.

Thanks for any help.
-obhi

##### Share on other sites
Sorry for not doing much research!
Anybody looking for answers can look here:

##### Share on other sites
The magic word is glMapBuffer.
You call that in your main thread and the pointer it returns, you can keep it or send it to your other thread.

You should also read this part "Dynamic VBO"
and it is doable from 1 thread

http://www.opengl.org/wiki/VBO_-_more

##### Share on other sites
Passing the buffer pointer between the threads however is not the way i want to go.
Solely because the need to update the (backing) VBO is determined by the main thread while the renderer is already drawing the current updated data. So, the sync that will be necessary here (possibly by message passing) would make the whole process stall on each other. Not the way I would like it.

Thanks,
obhi

## Create an account

Register a new account

• ## Partner Spotlight

• ### Forum Statistics

• Total Topics
627686
• Total Posts
2978637
• ### Similar Content

• Both functions are available since 3.0, and I'm currently using glMapBuffer(), which works fine.
But, I was wondering if anyone has experienced advantage in using glMapBufferRange(), which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
• By xhcao
Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness.
• By cebugdev
hi guys,
are there any books, link online or any other resources that discusses on how to build special effects such as magic, lightning, etc. in OpenGL? i mean, yeah most of them are using particles but im looking for resources specifically on how to manipulate the particles to look like an effect that can be use for games,. i did fire particle before, and I want to learn how to do the other 'magic' as well.
Like are there one book or link(cant find in google) that atleast featured how to make different particle effects in OpenGL (or DirectX)? If there is no one stop shop for it, maybe ill just look for some tips on how to make a particle engine that is flexible enough to enable me to design different effects/magic
let me know if you guys have recommendations.
• By dud3
How do we rotate the camera around x axis 360 degrees, without having the strange effect as in my video below?
Mine behaves exactly the same way spherical coordinates would, I'm using euler angles.
Tried googling, but couldn't find a proper answer, guessing I don't know what exactly to google for, googled 'rotate 360 around x axis', got no proper answers.

References:
Code: https://pastebin.com/Hcshj3FQ
The video shows the difference between blender and my rotation:

• By Defend
I've had a Google around for this but haven't yet found some solid advice. There is a lot of "it depends", but I'm not sure on what.
My question is what's a good rule of thumb to follow when it comes to creating/using VBOs & VAOs? As in, when should I use multiple or when should I not? My understanding so far is that if I need a new VBO, then I need a new VAO. So when it comes to rendering multiple objects I can either:
* make lots of VAO/VBO pairs and flip through them to render different objects, or
* make one big VBO and jump around its memory to render different objects.
I also understand that if I need to render objects with different vertex attributes, then a new VAO is necessary in this case.
If that "it depends" really is quite variable, what's best for a beginner with OpenGL, assuming that better approaches can be learnt later with better understanding?

• 12
• 14
• 12
• 10
• 12