Sign in to follow this  
SingularOne

OpenGL Rotation Matrix about point

Recommended Posts

SingularOne    100
Hey, would you help me a bit? I'm struggling with making matrices to rotate about point. My rotation part of the matrix construction looks like that:

[code]

boneMatrices[offs + 0] = cos(rx) * cos(ry);


boneMatrices[offs + 1] = -cos(rz) * sin(rx) - cos(rx)*sin(ry)*sin(rz);
boneMatrices[offs + 2] = cos(rx) * cos(rz) * sin(ry) + sin(rx) * sin(rz);

boneMatrices[offs + 4] = cos(ry) * sin(rx);
boneMatrices[offs + 5] = cos(rx) * cos(rz) - sin(rx)*sin(ry)*sin(rz);
boneMatrices[offs + 6] = cos(rz) * sin(rx) * sin(ry) - cos(rx) * sin(rz);

boneMatrices[offs + 8] = -sin(ry);
boneMatrices[offs + 9] = cos(ry) * sin(rz);
boneMatrices[offs + 10] = cos(ry) * cos(rz);
[/code]

I pass origin for rotation instead of scaling part of the matrix, and then, in vertex shader i do:

1) subtract origin from vertex

2) rotate vertex

3) add origin to vertex

It works, but it sucks. too much operations, ugly code;

I want to pass to my shader matrices that already do rotation about specific point. but really i need someone's help here. how can i make above matrix to rotate about specific point? i couldn't find any descriprion adoptable in my case.




i use opengl, if it matters.

Share this post


Link to post
Share on other sites
haegarr    7372
Assuming that you use column vectors, if [b]T[/b]([b]c[/b]) is the translation matrix to the center of rotation and [b]R[/b] is the rotation matrix, then the product
[b]M[/b] := [b]T[/b]([b]c[/b]) * [b]R[/b] * [b]T[/b](-[b]c[/b])
defines the desired new rotation matrix. It translates by -[b]c[/b], rotates, and translates back by [b]c[/b] like you do now separately.

EDIT:
You can take advantage from knowing the structures of the matrices when you compute the above product. Think of [b]M[/b] having a 3x3 sub-marix [b]M[/b][sub]R[/sub] on the upper left and a 1x3 sub-matrix [b]M[/b][sub]T[/sub] on the upper right, and doing so with [b]R[/b] and [b]T[/b] as well, then
[b]M[/b][sub]R[/sub] := [b]R[/b][sub]R[/sub]
[b]M[/b][sub]T[/sub] := [b]R[/b][sub]R[/sub] * [b]T[/b][sub]T[/sub](-[b]c[/b]) + [b]T[/b][sub]T[/sub]([b]c[/b])
means the minimum computations to be done for yielding in [b]M[/b].

Share this post


Link to post
Share on other sites
SillyCow    1463
[quote name='SingularOne' timestamp='1313475830' post='4849719']
1) subtract origin from vertex

2) rotate vertex

3) add origin to vertex

[/quote]

I know you might not want to hear this, but the way you listed above is the correct way. If you want your code to still look good, you can write it like this (writen in psuedocode of course):

[code]
function RotateAboutPoint(Point,Rotation){
return MoveToAxis * Rotate * MoveFromAxis;
}
[/code]

It might even perform better than your "beautiful" code since matrix multiplication is accelerated while multiplying every element in your matrix separately is not... (Not sure about this one though...)

Share this post


Link to post
Share on other sites
SingularOne    100
Thanks for your replies.

Well i've tried to do it like [b]haegarr [/b]described:




[code]

//Origins

oMat.make_identity();
oMat2.make_identity();

oMat.element(0, 3) = -ox;
oMat.element(1, 3) = -oy;
oMat.element(2, 3) = -oz;

oMat2.element(0, 3) = ox;
oMat2.element(1, 3) = oy;
oMat2.element(2, 3) = oz;


//Rotation(tested)
bMat.make_identity();

bMat.element(0, 0) = cos(rx) * cos(ry);
bMat.element(1, 0) = -cos(rz) * sin(rx) - cos(rx)*sin(ry)*sin(rz);
bMat.element(2, 0) = cos(rx) * cos(rz) * sin(ry) + sin(rx) * sin(rz);;
bMat.element(0, 1) = cos(ry) * sin(rx);
bMat.element(1, 1) = cos(rx) * cos(rz) - sin(rx)*sin(ry)*sin(rz);
bMat.element(2, 1) = cos(rz) * sin(rx) * sin(ry) - cos(rx) * sin(rz);
bMat.element(0, 2) = -sin(ry);
bMat.element(1, 2) = cos(ry) * sin(rz);
bMat.element(2, 2) = cos(ry) * cos(rz);

//Bone translation

bMat.element(0, 3) = translation.x;
bMat.element(1, 3) = translation.y;
bMat.element(2, 3) = translation.z;


//M := R * T(-c) + T© ??
bMat *= oMat;
bMat += oMat2;[/code]


[b]and rotation\translation is now rigth, but for some reason i[u][color="#8b0000"]t's about 2x weaker than it should be and it looks like it scales vertices a bit then rotating[/color][/u][/b]

Share this post


Link to post
Share on other sites
SillyCow    1463
[quote name='SingularOne' timestamp='1313485221' post='4849759']
[code]

bMat *= oMat;
bMat += oMat2;[/code]

[/quote]

Why are you adding? All matrix chaining transformations should be multiplications...

Share this post


Link to post
Share on other sites
SingularOne    100
Ok, fixed by


[code]
bMat *= oMat;
oMat2 *= bMat;
bMat = oMat2;//(or just pass oMat2 to shader)[/code]

(equialent of -T * R * T)

but i'm not sure if it's ok to use such a matrix for tangent and normal? looks ok, but just want to know.

Share this post


Link to post
Share on other sites
haegarr    7372
[quote name='SillyCow' timestamp='1313504494' post='4849857']
[quote name='SingularOne' timestamp='1313485221' post='4849759']
[code]
bMat *= oMat;
bMat += oMat2;[/code]
[/quote]

Why are you adding? All matrix chaining transformations should be multiplications...
[/quote]
[font="arial, verdana, tahoma, sans-serif"][size="2"]Please let me clarify what
[color="#1C2837"][size="2"][b]M[/b][sub]T[/sub] := [b]R[/b][sub]R[/sub] * [b]T[/b][sub]T[/sub](-[b]c[/b]) + [b]T[/b][sub]T[/sub]([b]c[/b])[/size][/color][/size][/font]
actually means. As mentioned my post above, [color="#1C2837"][size="2"][b]R[/b][sub]R[/sub][/size][/color] is a 3x3 matrix and [color="#1C2837"][size="2"][b]T[/b][sub]T[/sub][/size][/color] is a 1x3 matrix (a.k.a. column vector). Multiplying a 3x3 matrix on the left and a 1x3 matrix on the right gives you a 1x3 matrix. Adding a 1x3 matrix onto a 1x3 matrix gives you a 1x3 matrix.

So notice that the result [color="#1C2837"][size="2"][b]M[/b][sub]T[/sub][/size][/color] is a 1x3 matrix (and that [color="#1C2837"][size="2"][b]M[/b][sub]R[/sub][/size][/color] is a 3x3 matrix), while [b]M[/b] itself is a usual homogeneous 4x4 matrix. The correct assembly then looks like
[code]
bMat.make_identity();
// MR
bMat.element(0, 0) = cos(rx) * cos(ry);
bMat.element(1, 0) = -cos(rz) * sin(rx) - cos(rx)*sin(ry)*sin(rz);
bMat.element(2, 0) = cos(rx) * cos(rz) * sin(ry) + sin(rx) * sin(rz);;
bMat.element(0, 1) = cos(ry) * sin(rx);
bMat.element(1, 1) = cos(rx) * cos(rz) - sin(rx)*sin(ry)*sin(rz);
bMat.element(2, 1) = cos(rz) * sin(rx) * sin(ry) - cos(rx) * sin(rz);
bMat.element(0, 2) = -sin(ry);
bMat.element(1, 2) = cos(ry) * sin(rz);
bMat.element(2, 2) = cos(ry) * cos(rz);
// MT = MR * TT(-c) + TT(c)
bMat.element(0, 3) = bMat.element(0, 0) * (-ox) + bMat.element(0, 1) * (-oy) + bMat.element(0, 2) * (-oz) + ox;
bMat.element(1, 3) = bMat.element(1, 0) * (-ox) + bMat.element(1, 1) * (-oy) + bMat.element(1, 2) * (-oz) + oy;
bMat.element(2, 3) = bMat.element(2, 0) * (-ox) + bMat.element(2, 1) * (-oy) + bMat.element(2, 2) * (-oz) + oz;
[/code]
if I have interpreted the indexing scheme correctly.


EDIT: It is for sure possible to compose the desired rotation simply by computing [color="#1C2837"][size="2"][b]T[/b]([b]c[/b]) * [b]R[/b] * [b]T[/b](-[b]c[/b])[/size][/color]. The above way just shows (as mentioned) the minimal computational effort to do; it avoids all that nasty scalar products with 0 and 1. However, this kind of optimization will probably not be noticeable.

Share this post


Link to post
Share on other sites
SingularOne    100
[color="#1C2837"][size="2"][b] [url="http://www.gamedev.net/user/90444-haegarr/"]haegarr[/url],[/b]
i don't know how to thank you for your effort, your method works fine and it's much more efficient[/size][/color]
[size="2"][color="#1c2837"]
[b][url="http://www.gamedev.net/user/144405-sillycow/"]SillyCow[/url],[/b]
thank you too for pointing out the part i misunderstood.[/color][/size]
[size="2"] [/size]
[size="2"][color="#1c2837"]and yeah, i've alredy noticed, that it's not really good to rotate normals.[/color][/size]

Share this post


Link to post
Share on other sites
haegarr    7372
[quote name='SingularOne' timestamp='1313506514' post='4849879']
...
(equialent of -T * R * T)

but i'm not sure if it's ok to use such a matrix for tangent and normal? looks ok, but just want to know.
[/quote]
Well, please notice that -[b]T[/b] is not the same as [b]T[/b](-[b]c[/b]), because the elements on the main diagonal will be negated in -[b]T[/b] but not in [b]T[/b](-[b]c[/b])!

However, you can apply [b]T[/b](-[b]c[/b]) * [b]R[/b] * [b]T[/b]([b]c[/b]) to a normal / tangent because
a) normals and tangents are direction vectors and are hence invariant to translations, and
b) there is no scaling or shearing in this formula.
Hence for normals and tangents the above formula does the same as the lonely [b]R[/b] does: It simply rotates the vector.

Share this post


Link to post
Share on other sites
SingularOne    100
yes it looks like problem is in my shader.

here shader that i found in nvidia example of hardware skinning:


[code]
attribute vec4 position;
attribute vec3 normal;
attribute vec4 weight;
attribute vec4 index;
attribute float numBones;

uniform mat4 boneMatrices[30];
uniform vec4 color;
uniform vec4 lightPos;

void main()
{
vec4 transformedPosition = vec4(0.0);
vec3 transformedNormal = vec3(0.0);

vec4 curIndex = index;
vec4 curWeight = weight;

for (int i = 0; i < int(numBones); i++)
{
mat4 m44 = boneMatrices[int(curIndex.x)];

// transform the offset by bone i
transformedPosition += m44 * position * curWeight.x;

mat3 m33 = mat3(m44[0].xyz,
m44[1].xyz,
m44[2].xyz);

// transform normal by bone i
transformedNormal += m33 * normal * curWeight.x;

// shift over the index/weight variables, this moves the index and
// weight for the current bone into the .x component of the index
// and weight variables
curIndex = curIndex.yzwx;
curWeight = curWeight.yzwx;
}

gl_Position = gl_ModelViewProjectionMatrix * transformedPosition;

transformedNormal = normalize(transformedNormal);
gl_FrontColor = dot(transformedNormal, lightPos.xyz) * color;
}[/code]


and significant part of my adoption(maximum 2 bones affecting vertex, 1st one is always most effective, so 2nd affecting bone might exist only if 1st one is):

[code] V = gl_Vertex;
vec3 n2 = gl_Normal;
vec3 t2 = Tangent;
if(Bones.x >= 0.0)//Bone1 ID
{
mat4 tmat = BonesMat[int(Bones.x)]; //Bone matrix
mat3 nmat = mat3(tmat[0].xyz, tmat[1].xyz, tmat[2].xyz);

V = tmat * gl_Vertex * Bones.z; //Bones.z - Bone 1 weight
n2 = nmat * gl_Normal * Bones.z;
t2 = nmat * Tangent * Bones.z;

if(Bones.y >= 0.0)//Bone2 ID
{
tmat = BonesMat[int(Bones.y)];
nmat = mat3(tmat[0].xyz, tmat[1].xyz, tmat[2].xyz);

V += tmat * gl_Vertex * Bones.w; //Bones.w - Bone2 weight
n2 += nmat * gl_Normal * Bones.w;
t2 += nmat * Tangent * Bones.w;
}
}
[/code]
Further - using V,N,T as regular;

result: rotation\translation is alright.
problem: lighting glitches. then i move camera away from object - vertices that affected by 2 bones become dark with the distance(lambert decreasing).

Share this post


Link to post
Share on other sites
haegarr    7372
IMHO the shown adopted code snippet is missing a normalization of both n2 and t2 (assuming that "using V,N,T as regular" doesn't include it). The code snippet probably only works well if Bones.z == 1 and Bones.y < 0. In all other cases the lengths of n2 and t2 may be anything but are later expected to be 1.

Share this post


Link to post
Share on other sites
SingularOne    100
yes, i've noticed before, it works ok if bone1 weight = 1.0 and bone2 is ineffective, but i do normalize resulting normal and tangent


[code]

vec3 T = normalize(gl_NormalMatrix * normalize(t2));
vec3 N = normalize(gl_NormalMatrix * normalize(n2));
vec3 B = cross(N, T);[/code]


and even if i remove normal rotation, problem doesn't go away.
also i modified code so second bone weight = 1.0 - FirstBoneWeight (because outside shader my program actually calculates weights for all affecting bones, but in examples i use to test it's always <= 2 bones affecting vertex);

and to avoid wasting your time with snippets:
full code of stuff that actually affects that problem,
[spoiler]
[code]#version 110
attribute vec4 Bones;
attribute vec3 Tangent;
uniform mat4 BonesMat[30];
varying vec3 ld;
varying vec3 eye;
varying vec4 V;

void main()
{
V = gl_Vertex;
vec3 n2 = gl_Normal;
vec3 t2 = Tangent;
if(Bones.x >= 0.0)
{
mat4 tmat = BonesMat[int(Bones.x)];
mat3 nmat = mat3(tmat[0].xyz, tmat[1].xyz, tmat[2].xyz);

V = tmat * gl_Vertex * Bones.z;
n2 = nmat * gl_Normal * Bones.z;
t2 = nmat * Tangent * Bones.z;

if(Bones.y >= 0.0)
{
tmat = BonesMat[int(Bones.y)];
nmat = mat3(tmat[0].xyz, tmat[1].xyz, tmat[2].xyz);

V += tmat * gl_Vertex * (1.0-Bones.z);
n2 += nmat * gl_Normal * (1.0-Bones.z);
t2 += nmat * Tangent * (1.0-Bones.z);
}
}

gl_TexCoord[0] = gl_MultiTexCoord0;
V = gl_ModelViewMatrix * V;

vec3 T = -normalize(gl_NormalMatrix * normalize(t2));
vec3 N = normalize(gl_NormalMatrix * normalize(n2));
vec3 B = cross(N, T);

vec3 lv = (gl_LightSource[0].position - V).xyz;
ld.x = dot(lv, B);
ld.y = dot(lv, T);
ld.z = dot(lv, N);

vec3 vt = -V.xyz;
eye.x = dot(vt, B);
eye.y = dot(vt, T);
eye.z = dot(vt, N);
gl_Position = gl_ProjectionMatrix * V;
}[/code]

[/spoiler]

Share this post


Link to post
Share on other sites
SingularOne    100
The problem was i'm using 3-component vectors for all my lighting calculation, so vertex w-component was modified by rotation matrix correctly, but wasn't affecting lighting. so i should do it manually.

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  

  • Partner Spotlight

  • Similar Content

    • By pseudomarvin
      I assumed that if a shader is computationally expensive then the execution is just slower. But running the following GLSL FS instead just crashes
      void main() { float x = 0; float y = 0; int sum = 0; for (float x = 0; x < 10; x += 0.00005) { for (float y = 0; y < 10; y += 0.00005) { sum++; } } fragColor = vec4(1, 1, 1 , 1.0); } with unhandled exception in nvoglv32.dll. Are there any hard limits on the number of steps/time that a shader can take before it is shut down? I was thinking about implementing some time intensive computation in shaders where it would take on the order of seconds to compute a frame, is that possible? Thanks.
    • By Arulbabu Donbosco
      There are studios selling applications which is just copying any 3Dgraphic content and regenerating into another new window. especially for CAVE Virtual reality experience. so that the user opens REvite or CAD or any other 3D applications and opens a model. then when the user selects the rendered window the VR application copies the 3D model information from the OpenGL window. 
      I got the clue that the VR application replaces the windows opengl32.dll file. how this is possible ... how can we copy the 3d content from the current OpenGL window.
      anyone, please help me .. how to go further... to create an application like VR CAVE. 
       
      Thanks
    • By cebugdev
      hi all,

      i am trying to build an OpenGL 2D GUI system, (yeah yeah, i know i should not be re inventing the wheel, but this is for educational and some other purpose only),
      i have built GUI system before using 2D systems such as that of HTML/JS canvas, but in 2D system, i can directly match a mouse coordinates to the actual graphic coordinates with additional computation for screen size/ratio/scale ofcourse.
      now i want to port it to OpenGL, i know that to render a 2D object in OpenGL we specify coordiantes in Clip space or use the orthographic projection, now heres what i need help about.
      1. what is the right way of rendering the GUI? is it thru drawing in clip space or switching to ortho projection?
      2. from screen coordinates (top left is 0,0 nd bottom right is width height), how can i map the mouse coordinates to OpenGL 2D so that mouse events such as button click works? In consideration ofcourse to the current screen/size dimension.
      3. when let say if the screen size/dimension is different, how to handle this? in my previous javascript 2D engine using canvas, i just have my working coordinates and then just perform the bitblk or copying my working canvas to screen canvas and scale the mouse coordinates from there, in OpenGL how to work on a multiple screen sizes (more like an OpenGL ES question).
      lastly, if you guys know any books, resources, links or tutorials that handle or discuss this, i found one with marekknows opengl game engine website but its not free,
      Just let me know. Did not have any luck finding resource in google for writing our own OpenGL GUI framework.
      IF there are no any available online, just let me know, what things do i need to look into for OpenGL and i will study them one by one to make it work.
      thank you, and looking forward to positive replies.
    • By fllwr0491
      I have a few beginner questions about tesselation that I really have no clue.
      The opengl wiki doesn't seem to talk anything about the details.
       
      What is the relationship between TCS layout out and TES layout in?
      How does the tesselator know how control points are organized?
          e.g. If TES input requests triangles, but TCS can output N vertices.
             What happens in this case?
      In this article,
      http://www.informit.com/articles/article.aspx?p=2120983
      the isoline example TCS out=4, but TES in=isoline.
      And gl_TessCoord is only a single one.
      So which ones are the control points?
      How are tesselator building primitives?
    • By Orella
      I've been developing a 2D Engine using SFML + ImGui.
      Here you can see an image
      The editor is rendered using ImGui and the scene window is a sf::RenderTexture where I draw the GameObjects and then is converted to ImGui::Image to render it in the editor.
      Now I need to create a 3D Engine during this year in my Bachelor Degree but using SDL2 + ImGui and I want to recreate what I did with the 2D Engine. 
      I've managed to render the editor like I did in the 2D Engine using this example that comes with ImGui. 
      3D Editor preview
      But I don't know how to create an equivalent of sf::RenderTexture in SDL2, so I can draw the 3D scene there and convert it to ImGui::Image to show it in the editor.
      If you can provide code will be better. And if you want me to provide any specific code tell me.
      Thanks!
  • Popular Now