• Advertisement
Sign in to follow this  

OpenGL Object Rotation on local axis in OpneGL

This topic is 4736 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hello, I am programming a littel simulator for R/C-Planes in OpenGL. I Have an Object (my plane) i want to rotate aroung the x- (pitch) an z-axis (roll). This makes 2 rotations. Illustration: www.roebbeling.de/3dstuff/perspec.jpg My Problem, when i do the first rotation (x-axis) the axis of the object are not rotated. so when i make the second rotation i cant roll tth plane. i rotate around the normal z-axis and not the rotated z-axis. You can download a testfile in C under: www.roebbeling.de/3dstuff/zagi.c I have read about rotation around an arbitrary axis by quaternions, but i cant figure out to do this with an object. That means i have to rotate every point in the object. Is there another way of doing this.

Share this post


Link to post
Share on other sites
Advertisement
You don't need to worry about rotation about an arbitary axis, just try doing your rotations before your translation.

The typical transformation order is Scales, then Rotations, then Translations. This is because rotations are relative to the given axis and scales are relative to the origrin. You may have seen it written as TRSx = x', but that isn't as clear as (T(R(Sx))) = x'

(man, that's the last time I try even simple ascii art. Apologies to the mods if they see all of those edits I made)

Share this post


Link to post
Share on other sites
Quote:

My Problem, when i do the first rotation (x-axis) the axis of the object are not rotated. so when i make the second rotation i cant roll tth plane. i rotate around the normal z-axis and not the rotated z-axis.

Change the order of rotations. You want R=Rx*Rz.
There's 2 ways to think of rotations (or better coord systems). If you think left to right, ie Rx -> Rz (in OpenGL, Direct3D it's the reverse) then think in terms of local coord system of the plane - that is you're rotating the plane's coord system around its local x-axis and then rotating it about its local z-axis which has changed. If you think right to left, ie, Rz -> Rx (its still R=Rx*Rz but you're *thinking* in a different direction) then you're rotating the plane around the global coord system which is you're rotating about global z-axis first and then rotating about global x-axis. You'll see both ways of thinking end up with the same result. The first way of thinking is very helpful when you do articulated objects where you have a hierarchy of bones and the transformation of a bone is influenced by its parent bone.

For small rotation angles your Euler angle method works fine.

Share this post


Link to post
Share on other sites
Here's EXACTLY what you need to do. Create a matrix which is the identity matrix. Then each time you perform a rotation, get the modelview matrix with glGetMatrixf(GL_MODELVIEW, mat), where you declared float mat[16];

Then simply take your created matrix, L and multiply it with mat
L * mat;

Then store the result back in L. Then clear the modelview matrix with glLoadIdentity and simply call glLoadMatrix(L);


What this will basically do is concatenate all your rotations and it will enable you to do local rotations no matter what the orientation of the model is.

You do the same thing after translating or scaling your model.

So here's a short example

glClear(...);
glLoadIdentity();
// perform camera rotations, translations, ect... here

glPushMatrix();
glLoadIdentity();

glRotate(angle, 0, 1, 0); // rotate model around y-axis
glGetMatrixf(GL_MODELVIEW, mat);
multiplyMatrices(local_matrix, mat);

glPopMatrix();
glMultMatrixf(local_matrix);

Share this post


Link to post
Share on other sites
Quote:
Original post by oconnellseanm
So here's a short example

glClear(...);
glLoadIdentity();
// perform camera rotations, translations, ect... here

glPushMatrix();
glLoadIdentity();

glRotate(angle, 0, 1, 0); // rotate model around y-axis
glGetMatrixf(GL_MODELVIEW, mat);
multiplyMatrices(local_matrix, mat);

glPopMatrix();
glMultMatrixf(local_matrix);


That's no different to:



glClear(...);
glLoadIdentity();
// perform camera rotations, translations, ect... here

glRotate(angle, 0, 1, 0); // rotate model around y-axis



Except that your version is horribly inefficient. When you call glRotate, the rotation matrix is automatically post-multiplied with the current modelview matrix.

Share this post


Link to post
Share on other sites
Actually its completely different from what you said.

You do not just call glRotate, you also STORE that rotation and multiply it against your local_matrix, which is storing every single transformation you perform on your model. Its very fast and it works perfectly. This is exactly how I do it in my world editor software, http://www.freeworld3d.org. You can rotate against the local or world axes.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By LifeArtist
      Good Evening,
      I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
      First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
      I am really stucked right now because of the fundamental question:
      Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
      If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on. 
      In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
      Should I treat those debug objects as entities/components?
      For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
      Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
      Regards,
      LifeArtist
    • By QQemka
      Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
      Let's go:
      Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
      Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
      Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
      What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
      There were several more but i forgot/solved them at time of writing
      Thanks in advance
    • By RenanRR
      Hi All,
      I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
      I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
      Vertex Shader:
      #version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
      ..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);  
      So, some doubts:
      - Why use it like that?
      - Is it okay to manipulate the camera that way?
      -in this way, are not the vertex's positions that changes instead of the camera?
      - I need to pass MVP to all shaders of object in my scenes ?
       
      What it seems, is that the camera stands still and the scenery that changes...
      it's right?
       
       
      Thank you
       
    • By dpadam450
      Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

      int rgbValue = int(textureSample.w);//4 bytes of data packed as color
      // algorithm might not be correct and endianness might need switching.
      vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
      extractedData /= 255.0f;
    • By Devashish Khandelwal
      While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
      Anyone has any idea .. what should I do?
  • Advertisement