Sign in to follow this  
Prune

OpenGL Detachable hierarchical objects

Recommended Posts

Prune    224
I'm assuming only rotations and translations are used in this. The easiest way to have a hierarchical object is to just store local transforms in the hierarchy, and in rendering the usual OpenGL transforms can be applied then popped when going up the hierarchy. But what if I want to have objects be able to detach and reattach to/from the hierarchy? When detaching, the object should be in world coordinates, with a rotation (quaternion) and translation. How do I extract that from the combined transforms of the hierarchy? Reattaching seems even more complex to me, as in I'm not at all clear how to approach the issue. Suggestions are greatly appreciated.

Share this post


Link to post
Share on other sites
Palidine    1315
Quote:
Original post by Prune
How do I extract that from the combined transforms of the hierarchy?


Just start at the root and multiply the matrices until you get to the leaf (just like OpenGL does). Then store the result in the object's orientation matrix.

To attach just set your local matrix to be = identity * attachPointOffsetMatrix.

-me

Share this post


Link to post
Share on other sites
Prune    224
Quote:
Original post by Palidine
Just start at the root and multiply the matrices until you get to the leaf (just like OpenGL does). Then store the result in the object's orientation matrix.

How would I extract from that matrix a single translation and single rotation to represent it, when that matrix has resulted from a composition of rotations around different points and directions? I need to extract this since I need to do physical simulation on the detached object.

Quote:
To attach just set your local matrix to be = identity * attachPointOffsetMatrix.

But, as above, how would I find the local rotation that, when transformed by the sequence of transforms of the hierarchy, makes the object have the same orientation in world coordinate basis as when it was detached?

If hierarchy and global are something like this
R1*T1*R2*T2*R3*T3 <--> R0*T0
First case is how do I decompose the multiplied matrices from the hierarchy into R0 and T0.
Second case is, how do I find R3 and T3... OK the translation seems easy, but what about R3?

Share this post


Link to post
Share on other sites
Palidine    1315
Quote:
Original post by Prune
How would I extract from that matrix a single translation and single rotation to represent it, when that matrix has resulted from a composition of rotations around different points and directions? I need to extract this since I need to do physical simulation on the detached object.


I'm not sure I see the problem. If you can render it you have the necessary matrices. Just multiply them together starting from the root and you'll end up with the appropriate world-relative transform for the attached object

Quote:
Original post by PruneBut, as above, how would I find the local rotation that, when transformed by the sequence of transforms of the hierarchy, makes the object have the same orientation in world coordinate basis as when it was detached?


This, I suppose is a bit more complex

First, to back up let's make sure we've got the correct architecture:

Root - world-relative matrix (orientation plus translation
|
|
Child - Root-relative orientation matrix (includes root relative translation)
|
|
Child of Child - Child-relative orientation matrix (includes child-relative translation)

So to detach Child of Child:

matrix = rootMatrix * childMatrix * childOfChildMatrix
this now contains the proper world-relative orientation and translation. this is how you're already rendering it so it shouldn't look confusing.


To attach child of child back (now I'm unsure of this [smile]):

matrix = invRootMatrix * invChildMatrix * childOfChildMatrix;
If I'm not mistaken this will transform Child of Child back into Child relative object space (which is what you want).

[EDIT: a little shaky on the math but what you want is inverse(rootMatrix * childMatrix) * childOfChildMatrix. I believe that what I wrote above is equivalent but my matrix math is a tad weak [smile]. If that doesn't work, what you want to do conceptually is: when detaching transform CoC from child relative space into world-relative space; when attaching transform CoC from world-relative space into child-relative space]

-me

Share this post


Link to post
Share on other sites
Prune    224
OK, that makes sense.
From the composed matrix resulting from the multiplications, I know translation is just entries 13, 14, and 15, but I also need to extract the rotation. I assume that if a transform matrix was composed of only translation and rotation matrix multiplications, I can use the usual matrix to axis angle conversion on the 3x3 submatrix?

Share this post


Link to post
Share on other sites
Palidine    1315
Quote:
Original post by Prune
OK, that makes sense.
From the composed matrix resulting from the multiplications, I know translation is just entries 13, 14, and 15, but I also need to extract the rotation. I assume that if a transform matrix was composed of only translation and rotation matrix multiplications, I can use the usual matrix to axis angle conversion on the 3x3 submatrix?


I guess... I mean you'll always need to work with the world-relative matrix representation to extract the axis-angle or euler angles.

But, why do you need to extract anything? You'll have the complete orientation matrix, that's all you need to render or perform game logic. You can directly load a matrix in both OpenGL and DirectX for rendering, you don't need axis-angle representations.

-me

Share this post


Link to post
Share on other sites
Sneftel    1788
Quote:
Original post by Prune
OK, that makes sense.
From the composed matrix resulting from the multiplications, I know translation is just entries 13, 14, and 15, but I also need to extract the rotation...

You're determined to think in terms of translations and rotations. Stop it. For this sort of thing, all that matters is the 4x4 affine transformation matrix. Translations and rotations are merely an artifact of the transformation. Multiply two transformations, and you get the composition of the two transformations. If you like, you can extract translation and rotation from that, though for most purposes it's not necessary.

Share this post


Link to post
Share on other sites
Prune    224
It may not matter for rendering, but when specifying a keyframe in an animation to/from which to interpolate it's very useful. It's easier for me to specify, be at such and such angle at this point, then interpolate the rotation to get there from a previous one; likewise for translation. I'm also mixing such animation with simplified simulation in other parts of the timeline where again an orientation conceptually represented in terms of the object's axes which are aligned with the object in physically meaningful ways is useful.

Share this post


Link to post
Share on other sites
Palidine    1315
Quote:
Original post by Prune
It may not matter for rendering, but when specifying a keyframe in an animation to/from which to interpolate it's very useful. It's easier for me to specify, be at such and such angle at this point, then interpolate the rotation to get there from a previous one; likewise for translation. I'm also mixing such animation with simplified simulation in other parts of the timeline where again an orientation conceptually represented in terms of the object's axes which are aligned with the object in physically meaningful ways is useful.


But all you're doing is complicating the math that is more easily done with matrices. What Sneftel is saying is that you already have the perfect tool for this job: a matrix. That you don't yet know the math is irrelivant. Better to learn the appropriate tool than whittling down your square peg so it can go in the round hole. =)

For interpolation you may find quaternions more elegant; but they are easily generated from that same matrix you already have.

A corollary would be trying to determine the angle between a unit's facing orientation and it's target using trigonometry instead of just the dot product of the two vectors. Sure it'll work, but it gets confusing fast and is not easy to implement.

-me

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Similar Content

    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      Question:
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
       
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
    • By markshaw001
      Hi i am new to this forum  i wanted to ask for help from all of you i want to generate real time terrain using a 32 bit heightmap i am good at c++ and have started learning Opengl as i am very interested in making landscapes in opengl i have looked around the internet for help about this topic but i am not getting the hang of the concepts and what they are doing can some here suggests me some good resources for making terrain engine please for example like tutorials,books etc so that i can understand the whole concept of terrain generation.
       
    • By KarimIO
      Hey guys. I'm trying to get my application to work on my Nvidia GTX 970 desktop. It currently works on my Intel HD 3000 laptop, but on the desktop, every bind textures specifically from framebuffers, I get half a second of lag. This is done 4 times as I have three RGBA textures and one depth 32F buffer. I tried to use debugging software for the first time - RenderDoc only shows SwapBuffers() and no OGL calls, while Nvidia Nsight crashes upon execution, so neither are helpful. Without binding it runs regularly. This does not happen with non-framebuffer binds.
      GLFramebuffer::GLFramebuffer(FramebufferCreateInfo createInfo) { glGenFramebuffers(1, &fbo); glBindFramebuffer(GL_FRAMEBUFFER, fbo); textures = new GLuint[createInfo.numColorTargets]; glGenTextures(createInfo.numColorTargets, textures); GLenum *DrawBuffers = new GLenum[createInfo.numColorTargets]; for (uint32_t i = 0; i < createInfo.numColorTargets; i++) { glBindTexture(GL_TEXTURE_2D, textures[i]); GLint internalFormat; GLenum format; TranslateFormats(createInfo.colorFormats[i], format, internalFormat); // returns GL_RGBA and GL_RGBA glTexImage2D(GL_TEXTURE_2D, 0, internalFormat, createInfo.width, createInfo.height, 0, format, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); DrawBuffers[i] = GL_COLOR_ATTACHMENT0 + i; glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0 + i, textures[i], 0); } if (createInfo.depthFormat != FORMAT_DEPTH_NONE) { GLenum depthFormat; switch (createInfo.depthFormat) { case FORMAT_DEPTH_16: depthFormat = GL_DEPTH_COMPONENT16; break; case FORMAT_DEPTH_24: depthFormat = GL_DEPTH_COMPONENT24; break; case FORMAT_DEPTH_32: depthFormat = GL_DEPTH_COMPONENT32; break; case FORMAT_DEPTH_24_STENCIL_8: depthFormat = GL_DEPTH24_STENCIL8; break; case FORMAT_DEPTH_32_STENCIL_8: depthFormat = GL_DEPTH32F_STENCIL8; break; } glGenTextures(1, &depthrenderbuffer); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); glTexImage2D(GL_TEXTURE_2D, 0, depthFormat, createInfo.width, createInfo.height, 0, GL_DEPTH_COMPONENT, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, depthrenderbuffer, 0); } if (createInfo.numColorTargets > 0) glDrawBuffers(createInfo.numColorTargets, DrawBuffers); else glDrawBuffer(GL_NONE); if (glCheckFramebufferStatus(GL_FRAMEBUFFER) != GL_FRAMEBUFFER_COMPLETE) std::cout << "Framebuffer Incomplete\n"; glBindFramebuffer(GL_FRAMEBUFFER, 0); width = createInfo.width; height = createInfo.height; } // ... // FBO Creation FramebufferCreateInfo gbufferCI; gbufferCI.colorFormats = gbufferCFs.data(); gbufferCI.depthFormat = FORMAT_DEPTH_32; gbufferCI.numColorTargets = gbufferCFs.size(); gbufferCI.width = engine.settings.resolutionX; gbufferCI.height = engine.settings.resolutionY; gbufferCI.renderPass = nullptr; gbuffer = graphicsWrapper->CreateFramebuffer(gbufferCI); // Bind glBindFramebuffer(GL_DRAW_FRAMEBUFFER, fbo); // Draw here... // Bind to textures glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, textures[0]); glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, textures[1]); glActiveTexture(GL_TEXTURE2); glBindTexture(GL_TEXTURE_2D, textures[2]); glActiveTexture(GL_TEXTURE3); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); Here is an extract of my code. I can't think of anything else to include. I've really been butting my head into a wall trying to think of a reason but I can think of none and all my research yields nothing. Thanks in advance!
    • By Adrianensis
      Hi everyone, I've shared my 2D Game Engine source code. It's the result of 4 years working on it (and I still continue improving features ) and I want to share with the community. You can see some videos on youtube and some demo gifs on my twitter account.
      This Engine has been developed as End-of-Degree Project and it is coded in Javascript, WebGL and GLSL. The engine is written from scratch.
      This is not a professional engine but it's for learning purposes, so anyone can review the code an learn basis about graphics, physics or game engine architecture. Source code on this GitHub repository.
      I'm available for a good conversation about Game Engine / Graphics Programming
    • By C0dR
      I would like to introduce the first version of my physically based camera rendering library, written in C++, called PhysiCam.
      Physicam is an open source OpenGL C++ library, which provides physically based camera rendering and parameters. It is based on OpenGL and designed to be used as either static library or dynamic library and can be integrated in existing applications.
       
      The following features are implemented:
      Physically based sensor and focal length calculation Autoexposure Manual exposure Lense distortion Bloom (influenced by ISO, Shutter Speed, Sensor type etc.) Bokeh (influenced by Aperture, Sensor type and focal length) Tonemapping  
      You can find the repository at https://github.com/0x2A/physicam
       
      I would be happy about feedback, suggestions or contributions.

  • Popular Now