opengl-4

The Short Version (TL;DR) I have a Camera attached to a SceneNode and movement works fine as long as the SceneNode 's rotation/axes are aligned with the world's. However, when an object rotates to "look" in a different direction and is told to move "forward" it does not move along the new "forward" direction. Instead, it continues to move in the same direction it was facing before the rotation was applied. Details and Example I have a scene graph to manage a 3D scene. The graph is a tree of SceneNode objects, which know about their transformations relative to their parent and the world. As per

I understand that OpenGL 4 and 3 are fairly similar, especially 3.1 and 4.1. With both being essentially released together, it can be difficult to understand the rationale for OpenGL 4.0/4.1. In previous releases of OpenGL, minor version increments upward until substantial changes accumulated into a new major version. OpenGL 3.x and 4.x introduced backwards-incompatible API changes and then OpenGL 3.2 and 3.3 are said to be specifically branches of the 3 series which are not forward compatible while 3.1 is compatible with 4.1+ What key differences does OpenGL 4.1 offer compared with OpenGL 3.1

I want to render filled circles of a dynamically varying radius around a set of points whose 2D coordinates are stored in a VBO. So far I was using GL_POINT_SMOOTH, but having now shifted to OpenGL 4.0, this option is no longer available. I have seen a similar question here but that doesn't quite suit my need because the centres of the circles in that example are hard-coded in the fragment shader. How would I do this? At the moment, my vertex shader looks like this: #version 400 layout(location=0) in vec2 in_Position; layout(location=1) in vec4 in_Color; out vec4 ex_Color; uniform vec4 bounds;

OpenGL 4.3 and OpenGL ES 3.1 added several alternative functions for specifying vertex arrays: glVertexAttribFormat , glBindVertexBuffers , etc. But we already had functions for specifying vertex arrays. Namely glVertexAttribPointer . Why add new APIs that do the same thing as the old ones? How do the new APIs work? glVertexAttribPointer has two flaws, one of them semi-subjective, the other objective. The first flaw is its dependency on GL_ARRAY_BUFFER . This means that the behavior of glVertexAttribPointer is contingent on whatever was bound to GL_ARRAY_BUFFER at the time it was called. But