Calculate Screen Coordinates (Determine Screen Coordinates from World Coordinates of an object)

Posted on 2004-07-31
Last Modified: 2013-12-26
The Problem is: I can't fully understand this function wich calculates the screen coordinates of an given object in world coordinates:

inline void Calculate_Screen_Coordinates(float* pScreenX, float* pScreenY, D3DXVECTOR3* pVec)
    tempX = pVec->x;
    tempY = pVec->y;
    tempZ = pVec->z;

    tempX2 = ViewProjectionMatrix._11*tempX + ViewProjectionMatrix._21*tempY + ViewProjectionMatrix._31*tempZ + ViewProjectionMatrix._41;
    tempY2 = ViewProjectionMatrix._12*tempX + ViewProjectionMatrix._22*tempY + ViewProjectionMatrix._32*tempZ + ViewProjectionMatrix._42;
    tempW2 = ViewProjectionMatrix._14*tempX + ViewProjectionMatrix._24*tempY + ViewProjectionMatrix._34*tempZ + ViewProjectionMatrix._44;

// Here comes part wich i can't understand fully:
     tempInvW2 = 1.0f/tempW2;

    *pScreenX = (1.0f + (tempX2*tempInvW2))*0.5f*screenwidth;
    *pScreenY = (1.0f - (tempY2*tempInvW2))*0.5f*screenheight;  

In detail:
// Next line i can't understand ->
tempInvW2 = 1.0f/tempW2;
i only know that this is a faktor for the z coord because the screen has only x/y but i don't know
why 1.0f and why the variable name is tempInv like Invers ?

This line is clearly:
*pScreenX = (1.0f + (tempX2*tempInvW2))*0.5f*screenwidth;

This line seems me wrong:
*pScreenY = (1.0f - (tempY2*tempInvW2))*0.5f*screenheight;
==> i would say:
*pScreenY = (1.0f + (tempY2*tempInvW
because the viewport coordinates are from -1/-1 to 1/1 and the screen coords are beginning in the  left top corner at 0/0 therefore transform -1/-1 & 1/1 to 0/0 & 2/2 ?!

Can anybody explain this in detail ?
Question by:WolfgangKoenig
LVL 17

Accepted Solution

davebytes earned 125 total points
ID: 11743364
A similar question/explanation at:

W is the scaling factor for the viewport.  Dividing by it will get you into screen-relative space.  1.0/W is pre-calculating the inverse so that a multiply can be used -- it is only used twice, but still faster to calculate the inverseW once and multiply against it, rather than dividing twice (yes, division is THAT BAD).

The - is because the 0,0 in 3D screen coords is usually the BOTTOM left, need to flip Y to get it to the TOP left.

As you say, generated view coordinates will be in the range of [-1,1] so for x:
1 + [-1,1] => [0,2] * 0.5 => [0,1]
and for y:
1 - [-1,1] => [2,0] * 0.5 => [1,0]
thus flipping the Y axis on the screen properly.

Multiplying by height/width then gets into screen pixels.


Featured Post

Secure Your Active Directory - April 20, 2017

Active Directory plays a critical role in your company’s IT infrastructure and keeping it secure in today’s hacker-infested world is a must.
Microsoft published 300+ pages of guidance, but who has the time, money, and resources to implement? Register now to find an easier way.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Artificial Intelligence comes in many forms, and for game developers, Path-Finding is an important ability for making an NPC (Non-Playable Character) maneuver through terrain.  A* is a particularly easy way to approach it.  I’ll start with the algor…
Performance in games development is paramount: every microsecond counts to be able to do everything in less than 33ms (aiming at 16ms). C# foreach statement is one of the worst performance killers, and here I explain why.

740 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question