Opengl 4.3 best ways to deal with vertex data

I wrap every object type into a class, just like in Direct3D. In OpenGL, everything is an unsigned integer. That is, in OpenGL, a context is just use to bundle the state changing functions, while in Direct3D, it wraps the immediate device context. As using multiple device contexts is not beneficial for performance, my devices only expose the вЂњimmediateвЂќ context. The device handles all resource creation, and the device context handles all state changes. I also follow the Direct3D split of a device and a device context. For extensions, I use glLoadGen which is by far the easiest and safest way to load OpenGL extensions I have found. In OpenGL, I go through the usual hoops: That is, I create an invisible window, query the extension functions on that, and then finally go on to create an OpenGL context that suits me. If you find a mistake, please drop me a line so I can fix it! Device creation & rendering contexts The hardest part for me during porting is to find out which OpenGL API corresponds to a specific Direct3D API call, and here is a write-down of what I found out & implemented in my rendering engine.

Welcome to my Direct3D to OpenGL mapping cheat-sheet, which will hopefully help you to get started with adding support for OpenGL to your renderer.

Opengl 4.3 best ways to deal with vertex data