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

Orthographic Projection Issue

8 posts in this topic

Hi there guys,

 

 

I have a problem with my Ortho Matrix. The engine uses the perspective projection fine but for some reason the Ortho matrix is messed up. (See screenshots below).

 

Can anyone understand what is happening here?

 

VIDEO Shows the same scene, rotating on the Y axis.
http://youtu.be/2feiZAIM9Y0

 

Ortho Projection code

void Matrix4f::InitOrthoProjTransform(float left, float right, float top, float bottom, float zNear, float zFar)
{
m[0][0] = 2 / (right - left);
m[0][1] = 0;
m[0][2] = 0;
m[0][3] = 0;

m[1][0] = 0;
m[1][1] = 2 / (top - bottom);
m[1][2] = 0;
m[1][3] = 0;

m[2][0] = 0;
m[2][1] = 0;
m[2][2] = -1 / (zFar - zNear);
m[2][3] = 0;

m[3][0] = -(right + left) / (right - left);
m[3][1] = -(top + bottom) / (top - bottom);
m[3][2] = -zNear / (zFar - zNear);
m[3][3] = 1;
}

Then using projectionMatrix.InitOrthoProjTransform(0.0f, 800.0f, 0.0f, 600.0f, 0.1f, 1000.0f);

 

OK so the first screenshot that is attached shows the Ortho, second one shows perspective (rotated slightly to show persp).

Edited by nickyc95
0

Share this post


Link to post
Share on other sites

you should use these parameters (-1.0, 1.0, -1.0*height/width, 1.0*height/width, 0.1, 1000) for ortho

in order (bottom , top , left , right , near , far)

Edited by Hosein G
0

Share this post


Link to post
Share on other sites

you should use these parameters (-1.0, 1.0, -1.0*height/width, 1.0*height/width, 0.1, 1000) for ortho

in order (bottom , top , left , right , near , far)

Why?

 

I thought that when you create an Ortho Matrix you use the screen dimensions to get a "pixel perfect" area to draw in (e.g. 800*600)

 

Thanks

0

Share this post


Link to post
Share on other sites

no actually there is no pixels there so the point is a ratio between height and width and you should take the origin in center

0

Share this post


Link to post
Share on other sites

no actually there is no pixels there so the point is a ratio between height and width and you should take the origin in center


Can you expand further?

Thanks
0

Share this post


Link to post
Share on other sites

ortho matrix is easy to master in the manner of width and height. but you can easiily screw up depth! resulting in paranormal oclusion- or, objects being further ocluding objects being closer. Watch out.  (Ortho normal projection is an observation phenomena that is being rather paranormal- as it is)

0

Share this post


Link to post
Share on other sites

 

you should use these parameters (-1.0, 1.0, -1.0*height/width, 1.0*height/width, 0.1, 1000) for ortho
in order (bottom , top , left , right , near , far)

This is not correct.
http://msdn.microsoft.com/en-us/library/windows/desktop/dd373965(v=vs.85).aspx
 
You are already passing the correct values, which should be actual pixel sizes.
 
Your Z values are both incorrect.
 
m[2][2] = -1 / (zFar - zNear); should be m[2][2] = -2 / (zFar - zNear);.

m[3][2] = -zNear / (zFar - zNear); should be m[3][2] = -(zFar + zNear) / (zFar - zNear);.

 

This is OpenGL, not Direct3D.

Also, try transposing the matrix if these changes do not work.

 

 

L. Spiro

 

Hi, 

 

thanks for "backing me up", haha.

 

Yeah turns out my matrices weren't consistent with each other, thus caused this issue.

 

Thanks

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