Transformations

[Cleverbeans]

If your plane is a component, then I believe it's orientation if constant based on how the component axes were defined originally. If your plane is not entering the model with consistent orientation, that suggest your placement transformation is rotating it rather than doing a strict translation. Once you've discerned your original orientation, it should be a simple matter of adding a rotation to orient the nose to the directional tangent to the spline then having your "up" vector rotate around the tangent until its parallel to the z-axis.

[zitoun]

@cleverbeans said:

If your plane is a component, then I believe it's orientation if constant based on how the component axes were defined originally. If your plane is not entering the model with consistent orientation, that suggest your placement transformation is rotating it rather than doing a strict translation. Once you've discerned your original orientation, it should be a simple matter of adding a rotation to orient the nose to the directional tangent to the spline then having your "up" vector rotate around the tangent until its parallel to the z-axis.

Thanks Cleverbeans! Yes indeed you're right, if I have the initial orientation of my plane I should be able to retrieve the orientation at any time... And I may do this in the end but I'm not too fond of this.
First because I don't really know the place of my plane at the first frame (cause I placed the plane and scaled it in the room to fit my purpose).
And secondly, (I could but) I will not place my plane at the origin with the right orientation and put my scene around just because there is no simple way to find the actual orientation of a selected component! I feel like it's really a basic feature to be able to know the precise location and orientation (and, to be exhaustive, scale) of my component at any time. Plus I will further add other planes and may have to do more complicated things in the future.

So I am really looking for a mean to find the exact orientation of a component at any time.

[zitoun]

However, Cleverbeans, an idea would be to integrate my plane as an external component and tailor the parameters so that it fits in my scene... That can be an idea, but I'll look into that once I'm desesperate !

[thomthom]

@zitoun said:

@thomthom said:

The transformation class has an axes method that I think could be used to get your bearings.

As I see it, Transformation::axes method only enables to SET the axes, unfortunately not to GET them...

Sorry - I refereed to the wrong methods.
instead, use xaxis, yaxis and zaxis
http://code.google.com/apis/sketchup/docs/ourdoc/transformation.html#xaxis

and of course the origin:
http://code.google.com/apis/sketchup/docs/ourdoc/transformation.html#origin

Everything is there in the transformation object.

[zitoun]

@thomthom said:

The transformation class has an axes method that I think could be used to get your bearings.

As I see it, Transformation::axes method only enables to SET the axes, unfortunately not to GET them...

EDIT: but maybe I should just SET the initial transformation, just like that... OK, let's try this.
But I still think it should be a standard feature to get the absolute or relative rotation matrix/quaternion for any component of the scene...

RE-EDIT: I hadn't seen Transformation::Xaxis, Yaxis and Zaxis method!
I have no clue what these are yet, but I guess I somehow can retrieve my rotation matrix from such component...

[zitoun]

@thomthom said:

In the same way my example took the local 3d position and transformed it with the combined transformation for all the containing groups/components you must apply the combined transformation to your vector of orientation/direction.

Sure thomthom, I get that. My pb is deeper... OK, I have to give the details! Here is what I understood so far:

An object has a 4x4 transformation matrix M attached that combines three parameters defining the geometrical state of the object:

• the position T in space
• the orientation R
• the scale S

Let's say I want to rotate my object (entity is the correct term I think) without changing the position: I will have to

• apply to M the inverse of the translation T (so far I use [0,0,0]-T)
  Sketchup.active_model.active_entities.transform_entities(ORIGIN-fromPos,e) #puts the objet at the origin
• then apply the relative orientation dR I need
  Sketchup.active_model.active_entities.transform_entities(Geom::Transformation.rotation(ORIGIN,UP,angle),e)
• and finally apply back the translation T.

You may say I should simply use the M.inverse but I think the scale factor would be a probl****em... Or not? (testing around) ... All right. Seems we can simply do :

• apply M.inverse,
  Sketchup.active_model.active_entities.transform_entities(e.transformation.inverse,e)
• apply dR
• apply M back
  Should be OK.

And here comes my tiny problem: current orientation R of the object is somehow melted with the other parameters T and S in global my transformation matrix M... How the hell do I get a proper orientation R?
Cause I already know the final absolute orientation R' I want my object (or entity, or, in my case, a good old german biplane) to reach: all I need is this initial orientation R to compute the difference dR.

I thought to just get rid of the transformation, discard it and return to the identity and thus apply directly the wanted orientation R', then the position T. But it would be too easy: to fit in a small room, my plane had to be scaled, and I then need to know this scale factor S (that I otherwise simply ignore).

This special line is to thank the reader for the effort he put to read my reply.
And this one is for the people that would give me some clues: I owe you!

[zitoun]

OK, I surrender, I chose Cleverbeans method in the end, which revealed to be quite fine to do:
I re-initialized my plane transformation, then I scale it with a factor of 1/2 several time, until I had the right size (1/32 in the end). I then chose a reference rotation to position the plane as I wanted to in the first place. I then have an "initialTransformation" that I will have to apply each time BEFORE the other regular transformation.

So for each frame I'll have
e.transform!( e.transformation.inverse ) e.transform!( initialTransformation ) e.transform!( transformationAtSuchFrame ) #with transformationAtSuchFrame combining a rotation and a translation

Now I am not depending anymore of a random initial state.
Of course I will rather combine all the intermediate matrices and then apply once the resulting transformation, it should be quicker.

EDIT: I may have a quicker solution, that I still have to validate: Geom::Transformation.origin method gives the translation to put the object at the origin (and then be able to perform a simple rotation).
I might use this rather than combine several 4x4 matrix, it has to be a lot quicker !

[thomthom]

@zitoun said:

e.transform!( e.transformation.inverse )
e.transform!( initialTransformation )

This seems like it can be reduced to
e.transformation = initialTransformation

and that could possibly be reduced to:

e.transformation = initialTransformation * transformationAtSuchFrame

[zitoun]

@thomthom said:

This seems like it can be reduced to
e.transformation = initialTransformation
and that could possibly be reduced to:
e.transformation = initialTransformation * transformationAtSuchFrame

Really?
I thought I had tested this solution and my results were not conclusive.
But maybe I was too tired: I'm gonna try again !

[thomthom]

If you always calculate from one fixed state then there is no need to undo the current transformation, you just set a new transformation overriding the old one.

[zitoun]

@thomthom said:

If you always calculate from one fixed state then there is no need to undo the current transformation, you just set a new transformation overriding the old one.

Yes indeed, but for some reason I thought that the method entity.transformation= was working differently (but I may have been really tired at the time I tested it).
It completely make sense that it works the way you describe it.

[zitoun]

Ahem.

Just remember:

@object.transform! @object.transformation.inverse
@object.transform! @transformationAt[toPage]

@object.transform! @transformationAt[toPage] * @object.transformation.inverse

Note the order of the transformations... I had forgotten this well known pb !

[thomthom]

@zitoun said:

@object.transform! @object.transformation.inverse

This just resets the transformation - same as @object.transformation = Geom::Transformation.new

@zitoun said:

@object.transform! @transformationAt[toPage] * @object.transformation.inverse

Isn't this just the same as: @object.transformation = @transformationAt[toPage] ?

[AdamB]

@thomthom said:

If you always calculate from one fixed state then there is no need to undo the current transformation, you just set a new transformation overriding the old one.

And you will end up with many problems if you build your code around inverting the CTM and multiplying by a new transform.

So if you're rotating an object, a low quality approach is to repeatedly apply a (say) 5 degree rotation rather than as Thomthom suggest, calculate the rotation at a time T and then calc what rotation you need.

The problem is that floating point does have finite precision, so if you repeatedly perform incremental transform as it seems you're doing, you'll end up with a non-orthonormal matrix. (Thats a bad thing).

[zitoun]

@thomthom said:

@zitoun said:

@object.transform! @object.transformation.inverse

This just resets the transformation - same as @object.transformation = Geom::Transformation.new

@zitoun said:

@object.transform! @transformationAt[toPage] * @object.transformation.inverse

Isn't this just the same as: @object.transformation = @transformationAt[toPage] ?

Yes, the inverse is not useful in my case.
I use @object.transformation= @transformationAt[toPage], as you suggest, and it works (well I still have some awkward pbs but I expect to solve them soon).

The code was just for my tests, I wanted to underline here that if you wish to do

entity.transform! entity.transformation.inverse
entity.transform! transfA
entity.transform! transfB

you could as well do

entity.transform! transfB * transfA * entity.transformation.inverse

or even better, as you say Thomthom

entity.transformation = transf[b]B[/b] * transf[b]A[/b]

[zitoun]

@adamb said:

And you will end up with many problems if you build your code around inverting the CTM and multiplying by a new transform.

Not really: it's more like reseting the transformation and set the one you like. No inverse is needed, and this solution is actually the only solution I can see so far.

But you're right, ignoring each object's current orientation is a real problem.

[thomthom]

@zitoun said:

But you're right, ignoring each object's current orientation is a real problem.

But you know that from the previous transformation.

[zitoun]

Another thing: angle_between only gives absolute angles.
If you need oriented angles, you might need something like

def angBtw(v1, v2)
	u1 = v1.normalize
	u2 = v2.normalize
	a = u1.angle_between u2
	if ( u1.cross u2 ).dot( Z_AXIS ) > 0
		return a
	else
		return -a
	end
end

Note 1: normalization is used only because there seems to be some trouble with angle_between for small values...
Note 2: I took Z_AXIS as my scene reference vector for now, but the good way to do would be to take the up vector of your object.

[Cleverbeans]

@zitoun said:

I have no clue what these are yet, but I guess I somehow can retrieve my rotation matrix from such component...

Note that a transformation has the .to_a method as well which gives you exactly the information you're looking for. The array it returns is 16 floats for the four by four matrix which defines the transformation from the components defining coordinate system to the current coordinate system. Since you mentioned quaternions I'll assume you're familiar with with the essentials of matrices and linear transformations. First, we can interpret the scaling and rotation of a component as the action of a matrix on the basis vectors of the component definition. Say for example you define your component relative to the standard basis of x=[1,0,0], y=[0,1,0], z=[0,0,1]. Rather than keeping these vectors separately, you can just encode them as the 3x3 identity matrix, and then define all the entities in the component relative to this matrix. From here, any sort of rotation/scaling can be interpreted as a change of basis. The trouble of course is that any linear transformation preserves the zero vector, so you can't model a translation in this way. This means to fully describe the relative coordinates you require a an equation of the form Ax + b where A is an invertible 3x3 change of basis matrix and b is the translation vector with x being the "defining" vector of some entity internal to the component.

This is where the clever bit comes in. You can model an affine transformation of the form Ax + b as a single matrix transformation by embedding it into a space with one higher dimension. This is why the transformation.to_a method returns a 16 entry array, it's a 4x4 matrix with the first four entries being the first column, the second four entries being the second column and so on. It's easy enough to extract the original 3x3 matrix and the translation vector as well, the "upper-left" 3x3 block matrix is exactly the change of basis matrix A, and the final column vector is of the form [b, 1] where b is the translation vector. From here extracting the rotation matrix is a simple matter of matrix algebra since any change of basis matrix A can be decomposed as A = QS where Q is a rotation matrix and S is a diagonal matrix representing the scaling of each axis.

It's worth getting to know the 4x4 representation if you haven't before since it's also the way the OpenGL standard models the objects. The ability to model vector addition as matrix multiplication is only one of the reason they do it, the other being that when you're rendering perspective views rather than simply orthographic views the value of the bottom right entry plays an important role in correcting the scale of the transformation after applying the perspective matrix.