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

Modelmatrix and translation/scale/rotation

4 posts in this topic

I think I missunderstand how to correctly apply translation/scale/rotation to my model matrix.

 

My SceneNode has a Mat4 called "mTransform". I get translation to work as expected, but applying rotation and scaling somehow causes the mesh not to be rendered on the screen.

 

Scale/Translate/RotateTransform corresponds to the glm:: methods. 

 

Am I correct in the way I do this?

 

    void SceneNode::Scale(Vec3 scaleVec)
    {
        mTransform = ScaleTransform(mTransform, scaleVec);
    }

    void SceneNode::Translate(Vec3 translateVec)
    {
        mTransform = TranslateTransform(mTransform, translateVec);
    }
        
    void SceneNode::Rotate(Vec3 rotateVec, const float angle)
    {
        mTransform = RotateTransform(mTransform, angle, rotateVec);
    }

 

 

0

Share this post


Link to post
Share on other sites

I don't know if those methods are correct, but on glm, you include

#include <glm\gtc\matrix_transform.hpp>

 

and then you can use the following methods

glm::translate(glm::mat4 startMatrix, glm::vec3 transVector);

glm::rotate(glm::mat4 startMatrix, float angle, glm::vec3 rotVector);

glm::scale(glm::mat4 startMatrix, glm::vec3 scaleVector);

 

which return the respective transformed 'startMatrix'.

 

They have the same functionality as the following deprecated OpenGL functions glTranslatef(), glRotatef(), and glScalef() respectively.

 

Also note that the glm::mat4 does not have to be a matrix of floats, it can be doubles, etc, which affect the arguments/parameters.

 

And i'm not sure, but i think the order in which you transform the matrices matters,for example translating the matrix and then rotating it is not the same as doing it the other way around.

0

Share this post


Link to post
Share on other sites
And i'm not sure, but i think the order in which you transform the matrices matters,for example translating the matrix and then rotating it is not the same as doing it the other way around.

This. Matrix don't work like conventional numbers, their multiplication is not commutative. ie, For matrix A and matrix B, A*B =/= B*A.

 

I think you had to reverse the order to get things working. ie, I have a vertex, a perspective matrix and a rotation. I want to rotate the vertex and then use the perspective projection on it, thus the order would be:

 

perspective * rotation * vertex

 

Scaling comes before a rotation otherwise you'd scale along the wrong axis (ie, deform your model), so in the multiplication you reverse it by putting it after the rotation.

 

Thus you'd have: perspective * rotation * scaling * vertex.

Edited by TheChubu
0

Share this post


Link to post
Share on other sites
Can't I combine all my translation, rotation and scaling into one model matrix? And then if I want to translate it further I could just do translate on the previous matrix the next frame?

OR do I have to save each translation, rotate and scale as separate matrices for the model? Edited by KaiserJohan
0

Share this post


Link to post
Share on other sites

I believe you can combine all the transformations on the same matrix, provided they are done in the right order, however if you wish to transform again, you must apply all transformations again on  an identity matrix (the default matrix).

Because if the order in which you apply the transformations matter, by applying another transformation on top of other you're effectively changing the order (eg: scale, rotate, translate and then another rotate).

 

I think the exception to this, is if you make the same type of transformation (example: scale, translate and then another translate), thnit would be like the last transformations combined (again: the last too translations could be combined as one).

 

But i ask that someone confirms this.

1

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