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

OpenGL
Problems with glm::ortho

3 posts in this topic

Hi!

I am currently trying to learn openGL (and 3d programming in general) using this tutorial:
[url="http://www.opengl-tu...ners-tutorials/"]http://www.opengl-tu...ners-tutorials/[/url]

I have finished the first 3 tutorials and I think that I have a basic grasp of what's going on.

Now, my problem is that when I try to follow the authors advice to experiment with glm::ortho as an alternative to glm::perspective I cannot, for the life of me, get anything to show in the cameras "field of view".

The problematic code:
[CODE]// Projection matrix : 45° Field of View, 4:3 ratio, display range : 0.1 unit <-> 100 units
//glm::mat4 Projection = glm::perspective(45.f, 4.0f / 3.0f, 0.1f, 100.0f);
glm::mat4 Projection = glm::ortho(
0.0f,
static_cast<float>(SCREEN_WIDTH),
static_cast<float>(SCREEN_HEIGHT),
0.0f,
0.0f,
100.0f
);
// Camera matrix
glm::mat4 View = glm::lookAt(
glm::vec3(0,0,5), // Camera is at (0,0,5), in World Space
glm::vec3(0,0,0), // and looks at the origin
glm::vec3(0,1,0) // Head is up (set to 0,-1,0 to look upside-down)
);
// Model matrix : an identity matrix (model will be at the origin)
glm::mat4 Model = glm::mat4(1.0f);
// Our ModelViewProjection : multiplication of our 3 matrices
glm::mat4 MVP = Projection * View * Model; // Remember, matrix multiplication is the other way around
// An array of 3 vectors which represents 3 vertices
static const GLfloat g_vertex_buffer_data[] =
{
1.0f, 1.0f, 0.0f,
1.0f, 2.0f, 0.0f,
0.0f, 1.0f, 0.0f,
};[/CODE]

SCREEN_WIDTH and SCREEN_HEIGHT are int constants 1024, 768 respectively.

If I use a projection matrix generated with glm::perspective (the on commented out at line 2) everything works as it should.
As I move the object around and change the projection matrix parameters, it behaves as you think it should.

But when I use glm::ortho I cannot get the triangle to show, no mather what coordinates I use for the triangles vertices or what values I pass as parameters to glm::ortho. (And I've tried a lot of them [img]http://public.gamedev.net//public/style_emoticons/default/tongue.png[/img])

If I understand it correctly you would use ortho when you want to display objects without depth, kind of like how you would in normal 2d space, (which makes me a bit confused about the zNear and zFar parameters, but still, if I'm not misstaken, the triangle should be visible given the projeciton matrix im producing with glm::ortho and the triangles position)

I've searched both gamedev and other resources on the web but I can't find that I'm doing anything wrong or different compared to working examples.

So, the only conclusion I can come to is that I'm missunderstanding the use of glm::ortho or 3d space in general, or that I made some noob mistake, as my grasp of 3d programming is close to nonexisting.

So please, if you have the time, enlighten me as to what I am doing wrong!

Whole main.cpp if needed:
[CODE]// Include standard headers
#include <iostream>
// Include GLEW
#define GLEW_STATIC
#include "glew.h"
// Include GLFW
#include "glfw.h"
// Include GLM
#include <glm/glm.hpp>
#include <glm/gtc/matrix_transform.hpp>
#include <glm/gtx/transform.hpp>
// Include Shaders
#include "common/shader.hpp"
const int SCREEN_WIDTH = 1024;
const int SCREEN_HEIGHT = 768;
const int SCREEN_BPP = 32;
int main( void )
{
// Initialise GLFW
if (!glfwInit())
{
std::cout << stderr << "Failed to initialize GLFW." << std::endl;
return -1;
}
glfwOpenWindowHint(GLFW_FSAA_SAMPLES, 4);
glfwOpenWindowHint(GLFW_OPENGL_VERSION_MAJOR, 3);
glfwOpenWindowHint(GLFW_OPENGL_VERSION_MINOR, 3);
glfwOpenWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE);
// Open a window and create its OpenGL context
if (!glfwOpenWindow(SCREEN_WIDTH, SCREEN_HEIGHT, 0, 0, 0, 0, SCREEN_BPP, 0, GLFW_WINDOW))
{
std::cout << stderr << "Failed to open GLFW window." << std::endl;
glfwTerminate();
return -1;
}
// Initialize GLEW
if (glewInit() != GLEW_OK)
{
std::cout << stderr << "Failed to initialize GLEW." << std::endl;
return -1;
}
glfwSetWindowTitle("OpenGL 3 Training");
// Ensure we can capture the escape key being pressed below
glfwEnable(GLFW_STICKY_KEYS);
// Black background
glClearColor(0.f, 0.f, 1.f, 1.f);
GLuint VertexArrayID;
glGenVertexArrays(1, &VertexArrayID);
glBindVertexArray(VertexArrayID);
// Create and compile our GLSL program from the shaders
GLuint programID = LoadShaders("SimpleTransformShader.vertexshader", "SimpleFragmentShader.fragmentshader");
// Get a handle for our "MVP" uniform
GLuint MatrixID = glGetUniformLocation(programID, "MVP");
// Projection matrix : 45° Field of View, 4:3 ratio, display range : 0.1 unit <-> 100 units
//glm::mat4 Projection = glm::perspective(45.f, 4.0f / 3.0f, 0.1f, 100.0f);
glm::mat4 Projection = glm::ortho(
0.0f,
static_cast<float>(SCREEN_WIDTH),
static_cast<float>(SCREEN_HEIGHT),
0.0f,
0.0f,
100.0f
);
// Camera matrix
glm::mat4 View = glm::lookAt(
glm::vec3(0,0,5), // Camera is at (0,0,5), in World Space
glm::vec3(0,0,0), // and looks at the origin
glm::vec3(0,1,0) // Head is up (set to 0,-1,0 to look upside-down)
);
// Model matrix : an identity matrix (model will be at the origin)
glm::mat4 Model = glm::mat4(1.0f);
// Our ModelViewProjection : multiplication of our 3 matrices
glm::mat4 MVP = Projection * View * Model; // Remember, matrix multiplication is the other way around
// An array of 3 vectors which represents 3 vertices
static const GLfloat g_vertex_buffer_data[] =
{
1.0f, 1.0f, 0.0f,
1.0f, 2.0f, 0.0f,
0.0f, 1.0f, 0.0f,
};
static const GLushort g_element_buffer_data[] = { 0, 1, 2 };
// This will identify our vertex buffer
GLuint vertexbuffer;
// Generate 1 buffer, put the resulting identifier in vertexbuffer
glGenBuffers(1, &vertexbuffer);
// The following commands will talk about our 'vertexbuffer' buffer
glBindBuffer(GL_ARRAY_BUFFER, vertexbuffer);
// Give our vertices to OpenGL.
glBufferData(GL_ARRAY_BUFFER, sizeof(g_vertex_buffer_data), g_vertex_buffer_data, GL_STATIC_DRAW);
while (true)
{
// Check if the ESC key was pressed or the window was closed
if (glfwGetKey(GLFW_KEY_ESC) == GLFW_PRESS || !glfwGetWindowParam(GLFW_OPENED))
break;
// Clear the screen with the clearcolor
glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT);
// User our shader
glUseProgram(programID);
// Send our transformation to the currently bound shader, in the "MVP" uniform
glUniformMatrix4fv(MatrixID, 1, GL_FALSE, &MVP[0][0]);
// First attribute buffer : vertices
glEnableVertexAttribArray(0);
glBindBuffer(GL_ARRAY_BUFFER, vertexbuffer);
glVertexAttribPointer(
0, // attribute 0. No particular reason for 0, but must match the layout in the shader.
3, // size
GL_FLOAT, // type
GL_FALSE, // normalized?
0, // stride
(void*)0 // array buffer offset
);
// Draw the triangle !
glDrawArrays(GL_TRIANGLES, 0, 3); // Starting from vertex 0; 3 vertices total -> 1 triangle
glDisableVertexAttribArray(0);
// Swap buffers
glfwSwapBuffers();
}
// Cleanup VBO and shader
glDeleteBuffers(1, &vertexbuffer);
glDeleteProgram(programID);
glDeleteVertexArrays(1, &VertexArrayID);
// Close OpenGL window and terminate GLFW
glfwTerminate();
return 0;
}
[/CODE]

Thanks in advance / AS.
0

Share this post


Link to post
Share on other sites
You cannot just replace a perspective projection with an orthographic projection and expect things to just work with the same vertex data. The two are vastly different.

For example, just ignoring the look-at matrix for the moment, the orthographic projection matrix you use defines the visible coordinate range from 0 to 1024 along the X-axis, from 768 to 0 along the Y-axis (that is, a top-down axis), and from 0 to 100 along the Z-axis. If you then draw a triangle on the scale of 1 unit large (it extends between 0 and 1 on the X-axis and 1 and 2 on the Y-axis), inside a view volume 1024 by 768 units large, the triangle is only one pixel large.

If your triangle is inside the view volume, it will cover at most half of a single pixel in one of the four corners (once you add the look-at matrix, can't directly figure out which one though). It may even be too small to even be rasterized [i]at all[/i] if the rasterizer decides it's doesn't cover enough of the pixel.

There are some things you can do to locate your triangle:[list=1]
[*]Look closer in the very corners of your window. It may be that there is in fact a small pixel there and the triangle is just too small that you haven't see it yet.
[*]Make the view volume smaller or the triangle larger. Much smaller, or much larger. By a factor 100 or so.
[*]Extend the view volume into the negative coordinates. It may be that your look-at matrix rotates the view volume such that the visible X-range is rotated around the Y-axis, from its original visible range from 0 to 1024, into the new visible range from 0 to -1024.
[*]Drop the look-at matrix and focus just on getting the triangle to show up with the orthographic projection alone.
[/list]
2

Share this post


Link to post
Share on other sites
Hi Brother Bob.

Thanks for the quick reply.

[quote name='Brother Bob' timestamp='1352473161' post='4999302']
If you then draw a triangle on the scale of 1 unit large (it extends between 0 and 1 on the X-axis and 1 and 2 on the Y-axis), inside a view volume 1024 by 768 units large, the triangle is only one pixel large.
[/quote]
From reading posts on stack overflow, I actually came to understand this but for some reason i started to doubt if I actually understood it correctly.
I did try with a few hundered pixels large triangle without any result so I doubt that is the problem, but I might be wrong, I'll try it again!

[quote name='Brother Bob' timestamp='1352473161' post='4999302']
If your triangle is inside the view volume
[/quote]
This is the only reason I could think of trying to work it out on my own - that the triangle is out of bounds and thus not shown.
Using a larger triangle I can deduct wheter this is the case or not.

The main problem is that since this is uncharted territory for me, it's hard to trust instincts or information, your post cleared out some of the mist - thanks!

[quote name='Brother Bob' timestamp='1352473161' post='4999302']
There are some things you can do to locate your triangle:
1.Look closer in the very corners of your window. It may be that there is in fact a small pixel there and the triangle is just too small that you haven't see it yet.
2.Make the view volume smaller or the triangle larger. Much smaller, or much larger. By a factor 100 or so.
3.Extend the view volume into the negative coordinates. It may be that your look-at matrix rotates the view volume such that the visible X-range is rotated around the Y-axis, from its original visible range from 0 to 1024, into the new visible range from 0 to -1024.
4.Drop the look-at matrix and focus just on getting the triangle to show up with the orthographic projection alone.
[/quote]

I think the major cause of confusion for me was the translation from "-1 to 1" space to "Screen width*height in pixels" space.
Unfortunatley I had to go to work for a few hours so I can't try this out right now, but I'm sure I'll get it working following these steps when I get home.


Thanks for taking your time to help me.
0

Share this post


Link to post
Share on other sites
OK! So, I'm home now and able to go through it again.

[quote]
1. Look closer in the very corners of your window. It may be that there is in fact a small pixel there and the triangle is just too small that you haven't see it yet.
[/quote]
Wow, It's there! Right where you'd think it would be, in the top left corner ( since it has 1,1 as coords).

Im such a retard. i THOUGHT i made a 100 pixel large triangle but what I really did was that I increased ALL points by 100 so I only moved the 1 pixel large triangle 100 pixels in the posetive x and y axis. *sigh*

static const GLfloat g_vertex_buffer_data[] =
{
1.0f, 1.0f, 0.0f,
100.0f, 1.0f, 0.0f,
0.0f, 100.0f, 0.0f,
};

Works as intended!

Thanks alot m8! Edited by AlanSmithee
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

  • Similar Content

    • By Toastmastern
      So it's been a while since I took a break from my whole creating a planet in DX11. Last time around I got stuck on fixing a nice LOD.
      A week back or so I got help to find this:
      https://github.com/sp4cerat/Planet-LOD
      In general this is what I'm trying to recreate in DX11, he that made that planet LOD uses OpenGL but that is a minor issue and something I can solve. But I have a question regarding the code
      He gets the position using this row
      vec4d pos = b.var.vec4d["position"]; Which is then used further down when he sends the variable "center" into the drawing function:
      if (pos.len() < 1) pos.norm(); world::draw(vec3d(pos.x, pos.y, pos.z));  
      Inside the draw function this happens:
      draw_recursive(p3[0], p3[1], p3[2], center); Basically the 3 vertices of the triangle and the center of details that he sent as a parameter earlier: vec3d(pos.x, pos.y, pos.z)
      Now onto my real question, he does vec3d edge_center[3] = { (p1 + p2) / 2, (p2 + p3) / 2, (p3 + p1) / 2 }; to get the edge center of each edge, nothing weird there.
      But this is used later on with:
      vec3d d = center + edge_center[i]; edge_test[i] = d.len() > ratio_size; edge_test is then used to evaluate if there should be a triangle drawn or if it should be split up into 3 new triangles instead. Why is it working for him? shouldn't it be like center - edge_center or something like that? Why adding them togheter? I asume here that the center is the center of details for the LOD. the position of the camera if stood on the ground of the planet and not up int he air like it is now.

      Full code can be seen here:
      https://github.com/sp4cerat/Planet-LOD/blob/master/src.simple/Main.cpp
      If anyone would like to take a look and try to help me understand this code I would love this person. I'm running out of ideas on how to solve this in my own head, most likely twisted it one time to many up in my head
      Thanks in advance
      Toastmastern
       
       
    • By fllwr0491
      I googled around but are unable to find source code or details of implementation.
      What keywords should I search for this topic?
      Things I would like to know:
      A. How to ensure that partially covered pixels are rasterized?
         Apparently by expanding each triangle by 1 pixel or so, rasterization problem is almost solved.
         But it will result in an unindexable triangle list without tons of overlaps. Will it incur a large performance penalty?
      B. A-buffer like bitmask needs a read-modiry-write operation.
         How to ensure proper synchronizations in GLSL?
         GLSL seems to only allow int32 atomics on image.
      C. Is there some simple ways to estimate coverage on-the-fly?
         In case I am to draw 2D shapes onto an exisitng target:
         1. A multi-pass whatever-buffer seems overkill.
         2. Multisampling could cost a lot memory though all I need is better coverage.
            Besides, I have to blit twice, if draw target is not multisampled.
       
    • By mapra99
      Hello

      I am working on a recent project and I have been learning how to code in C# using OpenGL libraries for some graphics. I have achieved some quite interesting things using TAO Framework writing in Console Applications, creating a GLUT Window. But my problem now is that I need to incorporate the Graphics in a Windows Form so I can relate the objects that I render with some .NET Controls.

      To deal with this problem, I have seen in some forums that it's better to use OpenTK instead of TAO Framework, so I can use the glControl that OpenTK libraries offer. However, I haven't found complete articles, tutorials or source codes that help using the glControl or that may insert me into de OpenTK functions. Would somebody please share in this forum some links or files where I can find good documentation about this topic? Or may I use another library different of OpenTK?

      Thanks!
    • By Solid_Spy
      Hello, I have been working on SH Irradiance map rendering, and I have been using a GLSL pixel shader to render SH irradiance to 2D irradiance maps for my static objects. I already have it working with 9 3D textures so far for the first 9 SH functions.
      In my GLSL shader, I have to send in 9 SH Coefficient 3D Texures that use RGBA8 as a pixel format. RGB being used for the coefficients for red, green, and blue, and the A for checking if the voxel is in use (for the 3D texture solidification shader to prevent bleeding).
      My problem is, I want to knock this number of textures down to something like 4 or 5. Getting even lower would be a godsend. This is because I eventually plan on adding more SH Coefficient 3D Textures for other parts of the game map (such as inside rooms, as opposed to the outside), to circumvent irradiance probe bleeding between rooms separated by walls. I don't want to reach the 32 texture limit too soon. Also, I figure that it would be a LOT faster.
      Is there a way I could, say, store 2 sets of SH Coefficients for 2 SH functions inside a texture with RGBA16 pixels? If so, how would I extract them from inside GLSL? Let me know if you have any suggestions ^^.
    • By KarimIO
      EDIT: I thought this was restricted to Attribute-Created GL contexts, but it isn't, so I rewrote the post.
      Hey guys, whenever I call SwapBuffers(hDC), I get a crash, and I get a "Too many posts were made to a semaphore." from Windows as I call SwapBuffers. What could be the cause of this?
      Update: No crash occurs if I don't draw, just clear and swap.
      static PIXELFORMATDESCRIPTOR pfd = // pfd Tells Windows How We Want Things To Be { sizeof(PIXELFORMATDESCRIPTOR), // Size Of This Pixel Format Descriptor 1, // Version Number PFD_DRAW_TO_WINDOW | // Format Must Support Window PFD_SUPPORT_OPENGL | // Format Must Support OpenGL PFD_DOUBLEBUFFER, // Must Support Double Buffering PFD_TYPE_RGBA, // Request An RGBA Format 32, // Select Our Color Depth 0, 0, 0, 0, 0, 0, // Color Bits Ignored 0, // No Alpha Buffer 0, // Shift Bit Ignored 0, // No Accumulation Buffer 0, 0, 0, 0, // Accumulation Bits Ignored 24, // 24Bit Z-Buffer (Depth Buffer) 0, // No Stencil Buffer 0, // No Auxiliary Buffer PFD_MAIN_PLANE, // Main Drawing Layer 0, // Reserved 0, 0, 0 // Layer Masks Ignored }; if (!(hDC = GetDC(windowHandle))) return false; unsigned int PixelFormat; if (!(PixelFormat = ChoosePixelFormat(hDC, &pfd))) return false; if (!SetPixelFormat(hDC, PixelFormat, &pfd)) return false; hRC = wglCreateContext(hDC); if (!hRC) { std::cout << "wglCreateContext Failed!\n"; return false; } if (wglMakeCurrent(hDC, hRC) == NULL) { std::cout << "Make Context Current Second Failed!\n"; return false; } ... // OGL Buffer Initialization glClear(GL_DEPTH_BUFFER_BIT | GL_COLOR_BUFFER_BIT); glBindVertexArray(vao); glUseProgram(myprogram); glDrawElements(GL_TRIANGLES, indexCount, GL_UNSIGNED_SHORT, (void *)indexStart); SwapBuffers(GetDC(window_handle));  
  • Popular Now