• 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

2D vs 3D Camera transform matrix

2 posts in this topic

I was hoping someone could clear something up for me...

In 3D space, to obtain the camera view transform matrix, I believe it is scale * rotation * translation matrix.

However in 2D space (I've been working on a small project) I found it is actually the translation matrix * scale matrix, or the camera sometimes comes up with odd behavior.

After doing some searching online, I found for 3D camera problems the correct sequence was what I put above, same for 2D. I was wondering can someone offer a quick explanation as to why that is?

I'm just confused as to why you scale first then move the sprite for 3D, and move first then scale the model for 2D, since all 2D is missing is the Z axis.

Additional Info: I'm coding in MonoGame (XNA)



Share this post

Link to post
Share on other sites

There is no dependency on dimensionality with regard to the order of transformations.




In 3D space, to obtain the camera view transform matrix, I believe it is scale * rotation * translation matrix...

Such statements are meaningless as long as 

(1) one tells whether column vectors (like e.g. typically in OpenGL) or else row vectors (like e.g. typically in D3D) is used, and

(2) one tells what exactly the "camera view transform" means, and

(3) one tells what effect should be yielded in.


Usually, the camera transform is called what places the camera object into the world, i.e. the transformation from the camera local space into the global space. Also usually the view transform is the inverse of the camera transform, i.e. the transformation from the global space into the camera local (a.k.a. view) space.


With the above definition and the usage of column vectors, a camera transform is often build up as

   C := T * R * S

what you will call

   translation mul rotation mul scaling

but actually means

   scaling on the mesh, rotating the scaled mesh, translating the rotated scaled mesh


The corresponding view transform is then

   V := C-1 = S-1 * R-1 * T-1

where, if you stores the matrices as view matrices, you say

  scaling mul rotation mul translation


Now, the same game with row vectors gives you

   C := S * R * T

so that the order is reversed. This is true for all derived matrices, but the meaning is left as is! E.g. the above C actually still means

   scaling on the mesh, rotating the scaled mesh, translating the rotated scaled mesh

This is the difference of column vs row vector math.

In the end you see that both orders are valid in both systems, depending of what you speak of. Furthermore, you can think of applications that are not as easy as the composite of 3 matrices above, giving perhaps other orders in both systems. Whenever you read about transformation matrices you must realize the convention used in the reading, or else you cannot exactly interpret what you read.
Hope that helps. Matrix math is a bit confusing if the caveats are not known.
Edited by haegarr

Share this post

Link to post
Share on other sites

Oh I got it! I was thinking of the view transform and the camera transform as one in the same. Thanks a lot!


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