• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
codecandy2k

Matrix LookAt problem

2 posts in this topic

So as a learning process I'm trying to create some matrix functions to use in place of the XNA Math functions in DirectX.

 

Right now I'm stuck on MatrixLookAtLH which would replace XMMatrixLookAtLH.

 

Here is my function:

 

 

inline void MatrixLookAt( Matrix4F& matrixOut, Vector3F& eye, Vector3F& at, Vector3F& up )
{
    Vector3F zAxis( at.x() - eye.x(), at.y() - eye.y(), at.z() - eye.z() );
    VectorNormalize( zAxis );

    Vector3F xAxis = VectorCrossProduct( up, zAxis );
    VectorNormalize( xAxis );

    Vector3F yAxis = VectorCrossProduct( zAxis, xAxis );
    VectorNormalize(yAxis);


    MatrixSetRow( matrixOut, 0, xAxis );
    MatrixSetRow( matrixOut, 1, yAxis );
    MatrixSetRow( matrixOut, 2, zAxis );

    Vector3F wAxis( -VectorDotProduct(xAxis,eye), -VectorDotProduct(yAxis,eye), -VectorDotProduct(zAxis,eye) );
    MatrixSetRow( matrixOut, 3, wAxis );
}


And here is some code that calls it and the XM function:

 

   XMVECTOR Eye = XMVectorSet( 0.0f, 3.0f, -6.0f, 0.0f );
    XMVECTOR At = XMVectorSet( 0.0f, 1.0f, 0.0f, 0.0f );
    XMVECTOR Up = XMVectorSet( 0.0f, 1.0f, 0.0f, 0.0f );

    Vector3F Eye2 = Vector3F(0.0f, 3.0f, -6.0f);
    Vector3F At2 = Vector3F(0.0f, 1.0f, 0.0f);
    Vector3F Up2 = Vector3F(0.0f, 1.0f, 0.0f);

    Matrix4F view;
    MatrixLookAt(view, Eye2, At2, Up2);

    XMMATRIX xmView = XMMatrixLookAtLH( Eye, At, Up );
 

 

The results of the functionis are simiar but not exact.


This is the matrix "xmView" after calling the XNA XMMatrixLookAtLH function:

 

1 0 0 0
0 0.94868326 -0.31622776 0
0 0.31622776  0.94868326 0
0 -0.94868326 6.6407828 1

 

 

And this is the matrix "view" after calling my MatrixLookAtLH function:

 

1 0 0 0

0 0.94868326 0.31622776 0
0 -0.31622776  0.94868326 0
0 -0.94868326 6.6407828 1
 

 

As you can see, [1][2] and [2][1] seem to be reversed in the output from my code and everything else is the same.

 

Is there something fundamental in my calculation that I'm doing wrong, or is it possible that the step that I am missing is just reversing those 2 values?

 

Thanks!

Edited by codecandy2k
0

Share this post


Link to post
Share on other sites

The view matrix transforms from world to screen space.  It is the inverse of the camera's world matrix.  

 

We know that the inverse of a rotation matrix is its transpose.  Since what you are calculating is the view matrix, you need to transpose the upper 3x3 portion of the matrix to get the desired result.  Notice if you do that with your results, that you get the same thing as the library's matrix (don't just negate that's silly).  You can either transpose the matrix after setting the 3 columns or just set it directly.

 

What you are doing now is right for the translation, but is giving the world space rotation (when really we want its inverse).  Use your left hand given your input, have it point from the "eye" to the "at".  Hopefully it then becomes clear how the properly calculated view matrix is undoing that transformation.

1

Share this post


Link to post
Share on other sites

Brilliant, thanks so much for the answer and the explanation. I created a function to transpose the 3x3 portion of a 4x4 matrix in-place, and it works like a champ now.

0

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  
Followers 0