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

Archived

This topic is now archived and is closed to further replies.

subnet_rx

Matrix Stacks

8 posts in this topic

I''m having trouble understanding this concept, does someone know of a good tutorial that might explain this graphically? I know glPushMatrix() puts the matrix on the stack and glPopMatrix() takes it off, but in the examples of code I''m reading, I don''t understand why they are pushing an object onto the stack, then calling PopMatrix right after that. Wouldn''t that just take it right back off?
0

Share this post


Link to post
Share on other sites
Yes it would. Push saves the matrix and pop restores it. If you see a push followed by a pop with no code between was probably some object removed but the push/pop was forgotten.
0

Share this post


Link to post
Share on other sites
Actually, they call a push, create the object, then call a pop. I must not understand the matrix stack, b/c in my mind, this would put it on the matrix stack, then take it off. So, I''m just not getting something.
0

Share this post


Link to post
Share on other sites
Yes the matrix stack would be unchanged but they are temporary saving the current matrix. Pop does not just remove it from the stack but also load the current matrix with the top of the stack.
0

Share this post


Link to post
Share on other sites
ok, one last question to really help me understand this. I''m typing the Robot example in Gamedev''s OpenGL book if your wondering. Anyway, it calls a push, then it creates a head, torso, then it calls another push, creates one arm, then calls a pop. Why isn''t it calling a pop after each object?
0

Share this post


Link to post
Share on other sites
From http://www.cs.rutgers.edu/~decarlo/442-F99/opengl.html

Matrix stacks and transformations

OpenGL maintains several matrix stacks. The top matrix on each stack is used in the transformations performed by OpenGL. In this course, we will be using the modeling/viewing stack (GL_MODELVIEW) and the camera projection stack (GL_PROJECTION). Which one of these to use is specified using the glMatrixMode function. Other matrix stack functions that are commonly used include: glPushMatrix Adds a matrix to the current matrix stack (duplicating the previous matrix at the top of the stack)
glPopMatrix Discards the current (topmost) matrix on the current stack
glLoadIdentity Replaces the current matrix with the Identity matrix
Geometric transformations modify the current matrix. These functions include: glTranslate, glRotate and glScale.

Viewing transformations (orthographic and projective) modify the current matrix (typically the mode will be GL_PROJECTION in this case). These functions include: glOrtho, glFrustum, gluOrtho2D and gluPerspective.
0

Share this post


Link to post
Share on other sites
quote:
Original post by Floppy
They do that so the hand will move with the arm, but not the legs. Make since?


In the sequence I listed, there is no hand. Only a head, a torso, and a arm. Do you mean arm with the torso? If so, after they call that pop, they call a push, create arm #2 and call another pop, so that doesn''t seem to have anything to do with the torso. But the entire robot creation is nested inside a push and pop, so maybe that ties the whole thing together or something.

Is this easy for everyone to understand? I understand every line of code except this push and pop thing. I am just not visualizing it right or something.


subnet_rx
0

Share this post


Link to post
Share on other sites
Okay.

The whole reason for matrix stacks is so you can save your transformation matrix, alter it, render something, then restore it.

Push. This makes a copy of the current matrix on the stack, so you can alter it and restore it later.

Pop. This restores the old matrix.

Imagine drawing an arm. You want the forearm to be drawn RELATIVE to the upper arm.

Draw upper arm.
Push.
Rotate by the forearm rotation.
Draw the forearm.
Pop.

It really is that simple.
0

Share this post


Link to post
Share on other sites