Object rotation problem...

Your explanation of what your seeing is a little vague ('it kinda shrinks it's width"). [smile] Something a bit more technical might be helpful.

However, this looks suspicious:

D3DXMatrixScaling(&m_ScalingMatrix, fScaleX, fScaleY, 0); // scale

Scaling by 0 on the z-axis should give some peculiar results. Maybe try scaling z by 1 instead?

I've tried with 1 also, I've read somewhere that when using orthogonal projection, moving (scaling) objects on Z axis doesn't matter, so that's why it's 0 there. I can't give you more precise except a screenshot if that would make things clearer:

http://img258.imageshack.us/my.php?image=d3drotproblemry1.jpg

Both are just 2-triangle meshes, first one is with rotation 0 degrees, second one is close to 45 degrees...

Drop that kind of scaling stuff. You've specified the size (inclusive aspect ratio) of the view in the world already with the parameters of D3DXMatrixOrthoLH. No need to do it a second time. If you want to scale your object, then do it equally in both dimensions.

I agree with Haegarr. From the picture it looks like the result of your unusual scaling.

What do you mean by "drop.." ? If I don't have scaling (my meshes are 1x1 squares), how to scale something on the screen ? From the vertex buffer ?

Quote:

Original post by Predator_MF What do you mean by "drop.." ? If I don't have scaling (my meshes are 1x1 squares), how to scale something on the screen ? From the vertex buffer ?

The sequence of transformations done are
model-to-world .. world-to-view(camera) .. projection .. device-mapping
Therein the projection and the device-mapping deal with the screen aspect ratio. But you've integrated it also into the model-to-world portion.

You can scale your objects, of course, but it is in general not correct to do screen related scaling before the projection.

Think this way:

You have a world. Inside this world there is your camera "looking" along the line-of-sight. So far the camera specifies the world-to-view transformation with its position and orientation.

Furthur, the camera restricts what is seen at the sides and at the top and bottom, e.g. to a view of 1m width and 0.75m height. This is the camera's view, still specified in the world, so it is a kind of "virtual" view. You tell D3D this by invoking D3DXMatrixOrthoLH routine (perhaps you have to give it the half width and height, I don't know ATM).

The aspect ration of the view above is width/height, 4:3 in this case. Internally, the set-up done by D3DXMatrixOrthoLH, scales the visible portion of the world down to fit into a unit cube. It then maps the horizontal and vertical dimensions to fit into the pixels of the screen. Let's assume that the window is 800 by 600 pixels, and hence also shows an aspect ratio of 4:3 (i.e. the same aspect ratio than those given to D3DXMatrixOrthoLH!).

Following this procedure for an object of 0.5m by 0.5m size planar in front of the camera, means that
(1) it is scaled down as part of the projection to 0.5m/1m = 0.5 horizontally and 0.5m/0.75m = 0.667 vertically
and then
(2) mapped to 0.5*800px = 400px horizontally and 0.667*600px = 400px vertically onto the screen.
Voila: As you can see, the square is mapped to a square without any screen related scaling by yourself!

What you have to guarantee is that the aspect ratio given to D3DXMatrixOrthoLH and the aspect ratio of the screen (or window, whereever to display the scene) are identical.

Your attempt, on the other hand, has scaled the object something like:
width of 1m/4=0.25m, so that 0.25m/1m = 0.25, 0.25*800px = 200px
and height of 1m/3 = 0.333m, so that 0.333m/0.75m = .444, 0.444*600px = 266.4px
and that isn't a square anymore. That comes, of course, from the fact that the object itself isn't a square anymore after its scaling.

[Edited by - haegarr on June 30, 2008 2:27:43 PM]

Thanks guyz for the replies, I think I got it, I'll try it tomorrow and hopefully I would not have to write in this thread anymore xD

__
Pencheff