Let's say that I have two threads.
Both of them generates and binds to a vbo separately.
If I join and run these threads the behavior will be undefined obviously.
Because one may generate the vbo and one may Bind the vbo.
So how do AAA games like doom resolve this problem.
I chose that game because it most likely to be run in multiple threads. Thank you
There are a number of ways to handle this cleanly, but the simplest way is to use an API that's actually designed to work well with multithreading.
That means not using OpenGL, because OpenGL's global state, implied context, and bind-to-modify makes it work poorly with multithreading.
Most AAA games actually don't use OpenGL so this isn't a problem for them.
If you must use OpenGL there are of course solutions, including using wglShareLists (or equivalent) to share objects between contexts (and then being very very careful about how threads use objects), or restricting all GL calls to a single thread.
