• 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
soloman

a camera problem in directx11

7 posts in this topic

In directx11,a camera is identified with a position,a forcus direction,and a up direction.In my opinion?the up vector should be perpendicular to the forcus vertor.But in MS's toturial :

 

    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 );
    g_View = XMMatrixLookAtLH( Eye, At, Up );
    //cbNeverChanges.mView = XMMatrixTranspose( g_View );
As you can see, the At vec is same with the Up vec.I just confused with this usage.
By the way,what the reason to do the transpose after every XMMatricx**() be called.
 
Thanks for any help!
0

Share this post


Link to post
Share on other sites

Can you link the tutorial, or, if it's in the SDK, post the name of the project?

 

XMMatrixLookAtLH builds a "left-handed" matrix - i.e., row-major. Transposing a matrix swaps the rows and columns, making it a column-major matrix. Apparently, the view matrix is used somewhere (looks like the shader) which needs a column-major matrix.

Edited by Buckeye
1

Share this post


Link to post
Share on other sites

A look at matrix is just what it says, it creates a matrix from a point to a target.

 

Not a direction, the direction of view is define by (using your variables) At - Eye

 

I think that is why you are getting confused.

 

You are correct that Up should be perpendicular to (At -Eye)

 

You have to view tutorials with a grain of salt, they are written by humans. Often they work even though they have bugs in them, it's only when you try to use the code in a different environment that the bugs become apparent. 

 

The best tutorial writers allow feedback and are prepared to fix issues when they are pointed out to them. Microsoft..... not so much smile.png

1

Share this post


Link to post
Share on other sites

 

In directx11,a camera is identified with a position,a forcus direction,and a up direction.In my opinion?the up vector should be perpendicular to the forcus vertor.But in MS's toturial :

 

    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 );
    g_View = XMMatrixLookAtLH( Eye, At, Up );
    //cbNeverChanges.mView = XMMatrixTranspose( g_View );
As you can see, the At vec is same with the Up vec.I just confused with this usage.
By the way,what the reason to do the transpose after every XMMatricx**() be called.
 
Thanks for any help!

 

 

You are correct that the look at vector and up vector should not be colinear. But the At vector is not the view direction, but the spot you are looking at.

 

1) As mentioned previously, the function XMMatrixLookAtLH will create a look vector using at-eye to get a vector from the eyepoint to the look at point.

2) The cross product between the view vector and the up vector give a vector perpendicular to the view and up vectors

3) The view vector is crossed with the perpendicular to give a new up vector that finalizes the orthonormal basis.

4) IIRC (can't remember from where) at one point the mul intrinsic in HLSL worked faster with column major layout than row major layout

1

Share this post


Link to post
Share on other sites

Can you link the tutorial, or, if it's in the SDK, post the name of the project?

 

XMMatrixLookAtLH builds a "left-handed" matrix - i.e., row-major. Transposing a matrix swaps the rows and columns, making it a column-major matrix. Apparently, the view matrix is used somewhere (looks like the shader) which needs a column-major matrix.

it's in sdk.here the path:

Microsoft DirectX SDK (June 2010)\Samples\C++\Direct3D11\Tutorials\Tutorial07

1

Share this post


Link to post
Share on other sites

Thanks for the path. I didn't notice the Up vector when I played with the file. In any case, if you take a look at how a view matrix is constructed, you can see that the Up vector is only used in a cross product with vector(At - Eye) to form a "to-the-right" vector. There are an infinite number of vectors perpendicular to a vector, so as long as the Up vector you use in view matrix construction is perpendicular to the desired "to-the-right" direction (edit: well, and not the same direction as At-Eye) and pointing in the general "up" direction* desired, the view matrices all come out identical.

 

*I say the general "up" direction because it's crossed with At-Eye. If the Up vector points "downward," the sign of the crossproduct changes and (you may have guessed) the scene will appear upside-down.

Edited by Buckeye
0

Share this post


Link to post
Share on other sites

Buck, I think the " "left-handed" matrix" bit from your previous reply should be removed, as handedness and majorness are different ideas altogether.

0

Share this post


Link to post
Share on other sites

Nah, "left-hand" was specifically in quotation marks because the context was regarding a specific function advertised as "Look-At-Left-Hand," and I clearly stated the result was a row-major matrix.

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