Sign in to follow this  
Michael Wojcik

OpenGL Orthogonal matrix issue

Recommended Posts

Michael Wojcik    163
Hello everyone.

I've ran into a strange issue in my engine. With openGL ES 2.0, when I render my scene with a projection matrix, my scene renders correctly. With a orthogonal matrix, nothing renders at all. I'm using my own projection matrix functions to generate the matrices, so naturally, my first suspicion would be that my orthogonal matrix is being constructed erroneously but even openGL's orthoM() function bears the same problem.

Here is my GLSL vertex shader.

[code]
uniform mat4 u_projection_matrix;
uniform mat4 u_view_matrix;
uniform mat4 u_model_matrix;
attribute vec3 a_position;
attribute vec3 a_normal;
attribute vec2 a_texCoord0;
varying vec2 v_texCoord0;

void main()
{
v_texCoord0 = a_texCoord0;
gl_Position = ((u_projection_matrix * u_view_matrix * u_model_matrix) * vec4(a_position.xyz, 1.0));
}
[/code]

Here is my orthogonal projection matrix generation function just in case..

[code]
public void CreateOrthoMatrix(float left, float right, float bottom, float top, float near, float far)
{
// These paramaters are lens properties.
// The "near" and "far" create the Depth of Field.
// The "left", "right", "bottom" and "top" represent the rectangle formed
// by the near area, this rectangle will also be the size of the visible area.

Matrix.setIdentityM(projectionMatrix, 0);

// First Column
projectionMatrix[0] = 2.0f / (right - left);
projectionMatrix[1] = 0.0f;
projectionMatrix[2] = 0.0f;
projectionMatrix[3] = 0.0f;

// Second Column
projectionMatrix[4] = 0.0f;
projectionMatrix[5] = 2.0f / (top - bottom);
projectionMatrix[6] = 0.0f;
projectionMatrix[7] = 0.0f;

// Third Column
projectionMatrix[8] = 0.0f;
projectionMatrix[9] = 0.0f;
projectionMatrix[10] = -2.0f / (far - near);
projectionMatrix[11] = 0.0f;

// Fourth Column
projectionMatrix[12] = (right + left) / (right - left);
projectionMatrix[13] = (top + bottom) / (top - bottom);
projectionMatrix[14] = (far + near) / (far - near);
projectionMatrix[15] = 1;
}
[/code]

Anyone have any ideas whats going on?

My appreciations.

Share this post


Link to post
Share on other sites
NumberXaero    2624
Try

[code] // Fourth Column
projectionMatrix[12] = -(right + left) / (right - left);
projectionMatrix[13] = -(top + bottom) / (top - bottom);
projectionMatrix[14] = -(far + near) / (far - near);
projectionMatrix[15] = 1; [/code]

Share this post


Link to post
Share on other sites
Michael Wojcik    163
[quote name='NumberXaero' timestamp='1312667268' post='4845560']
Try

[code] // Fourth Column
projectionMatrix[12] = -(right + left) / (right - left);
projectionMatrix[13] = -(top + bottom) / (top - bottom);
projectionMatrix[14] = -(far + near) / (far - near);
projectionMatrix[15] = 1; [/code]
[/quote]

Thank you, but still no go after replacing my fourth column code the code you posted :(. If it helps this is how I call the method.

[code]
CreateOrthoMatrix(0.0f, width, 0.0f, height, 0.1f, 100f);
[/code]

Where the width and height is the width and height of my viewport. Which are matched to the pixel width and height of my device's screen.

Share this post


Link to post
Share on other sites
JTippetts    12949
Switching from a perspective to orthogonal matrix sometimes isn't simply as easy as changing the matrix. You also have to look at the scale of things that were being drawn before, and how they are being drawn now. Some objects might be too large, some might be too small, etc... For instance, a very small object (say, less than 1 unit in length/width/height) would occupy a large portion of the screen if viewed through a projection matrix, if it were close enough to the camera. However, with an orthogonal matrix, regardless of how near the camera it is, that object would always be drawn as less than one pixel in size (given a 1:1 mapping of projection space to screen space) since it's real size is less than one.

I'd say, test out your projection code with a controllable test case first, before you switch your in-project matrix, then when you are assured the matrix code is working correctly, begin the process of switching your game over.

Share this post


Link to post
Share on other sites
Michael Wojcik    163
[quote name='JTippetts' timestamp='1312673160' post='4845601']
Switching from a perspective to orthogonal matrix sometimes isn't simply as easy as changing the matrix. You also have to look at the scale of things that were being drawn before, and how they are being drawn now. Some objects might be too large, some might be too small, etc... For instance, a very small object (say, less than 1 unit in length/width/height) would occupy a large portion of the screen if viewed through a projection matrix, if it were close enough to the camera. However, with an orthogonal matrix, regardless of how near the camera it is, that object would always be drawn as less than one pixel in size (given a 1:1 mapping of projection space to screen space) since it's real size is less than one.

I'd say, test out your projection code with a controllable test case first, before you switch your in-project matrix, then when you are assured the matrix code is working correctly, begin the process of switching your game over.
[/quote]

jTippetts, Extrodenary Information!! I am making my engine unit relative to the metric meter. Yet I was contructing my orthogonal projection matrix's bounds to be relative to pixils, so everything in the scene was way too small. I am glad to now know that aspect in the nature of working with an othrogonal projection matrix.

NumberXaero, Thank you as well! That fixed up the implementation of my orthogonal projection matrix and now it works!

Thanks guys, you both saved me boat loads of time and made my day!

[b]
[/b]

Share this post


Link to post
Share on other sites
NicoG    172
You might want to consider using glm.
http://glm.g-truc.net/
It is a really nice math library for Vectors and Matrices especially designed for OpenGL and written against the GLSL ShaderSpec.
It saved [b]me[/b] a lot of time implementing that on my own.

Share this post


Link to post
Share on other sites
Michael Wojcik    163
[quote name='NicoG' timestamp='1312675908' post='4845611']
You might want to consider using glm.
[url="http://glm.g-truc.net/"]http://glm.g-truc.net/[/url]
It is a really nice math library for Vectors and Matrices especially designed for OpenGL and written against the GLSL ShaderSpec.
It saved [b]me[/b] a lot of time implementing that on my own.
[/quote]

I'll be sure to check it out, thanks!

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  

  • Similar Content

    • By Kjell Andersson
      I'm trying to get some legacy OpenGL code to run with a shader pipeline,
      The legacy code uses glVertexPointer(), glColorPointer(), glNormalPointer() and glTexCoordPointer() to supply the vertex information.
      I know that it should be using setVertexAttribPointer() etc to clearly define the layout but that is not an option right now since the legacy code can't be modified to that extent.
      I've got a version 330 vertex shader to somewhat work:
      #version 330 uniform mat4 osg_ModelViewProjectionMatrix; uniform mat4 osg_ModelViewMatrix; layout(location = 0) in vec4 Vertex; layout(location = 2) in vec4 Normal; // Velocity layout(location = 3) in vec3 TexCoord; // TODO: is this the right layout location? out VertexData { vec4 color; vec3 velocity; float size; } VertexOut; void main(void) { vec4 p0 = Vertex; vec4 p1 = Vertex + vec4(Normal.x, Normal.y, Normal.z, 0.0f); vec3 velocity = (osg_ModelViewProjectionMatrix * p1 - osg_ModelViewProjectionMatrix * p0).xyz; VertexOut.velocity = velocity; VertexOut.size = TexCoord.y; gl_Position = osg_ModelViewMatrix * Vertex; } What works is the Vertex and Normal information that the legacy C++ OpenGL code seem to provide in layout location 0 and 2. This is fine.
      What I'm not getting to work is the TexCoord information that is supplied by a glTexCoordPointer() call in C++.
      Question:
      What layout location is the old standard pipeline using for glTexCoordPointer()? Or is this undefined?
       
      Side note: I'm trying to get an OpenSceneGraph 3.4.0 particle system to use custom vertex, geometry and fragment shaders for rendering the particles.
    • By markshaw001
      Hi i am new to this forum  i wanted to ask for help from all of you i want to generate real time terrain using a 32 bit heightmap i am good at c++ and have started learning Opengl as i am very interested in making landscapes in opengl i have looked around the internet for help about this topic but i am not getting the hang of the concepts and what they are doing can some here suggests me some good resources for making terrain engine please for example like tutorials,books etc so that i can understand the whole concept of terrain generation.
       
    • By KarimIO
      Hey guys. I'm trying to get my application to work on my Nvidia GTX 970 desktop. It currently works on my Intel HD 3000 laptop, but on the desktop, every bind textures specifically from framebuffers, I get half a second of lag. This is done 4 times as I have three RGBA textures and one depth 32F buffer. I tried to use debugging software for the first time - RenderDoc only shows SwapBuffers() and no OGL calls, while Nvidia Nsight crashes upon execution, so neither are helpful. Without binding it runs regularly. This does not happen with non-framebuffer binds.
      GLFramebuffer::GLFramebuffer(FramebufferCreateInfo createInfo) { glGenFramebuffers(1, &fbo); glBindFramebuffer(GL_FRAMEBUFFER, fbo); textures = new GLuint[createInfo.numColorTargets]; glGenTextures(createInfo.numColorTargets, textures); GLenum *DrawBuffers = new GLenum[createInfo.numColorTargets]; for (uint32_t i = 0; i < createInfo.numColorTargets; i++) { glBindTexture(GL_TEXTURE_2D, textures[i]); GLint internalFormat; GLenum format; TranslateFormats(createInfo.colorFormats[i], format, internalFormat); // returns GL_RGBA and GL_RGBA glTexImage2D(GL_TEXTURE_2D, 0, internalFormat, createInfo.width, createInfo.height, 0, format, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); DrawBuffers[i] = GL_COLOR_ATTACHMENT0 + i; glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_COLOR_ATTACHMENT0 + i, textures[i], 0); } if (createInfo.depthFormat != FORMAT_DEPTH_NONE) { GLenum depthFormat; switch (createInfo.depthFormat) { case FORMAT_DEPTH_16: depthFormat = GL_DEPTH_COMPONENT16; break; case FORMAT_DEPTH_24: depthFormat = GL_DEPTH_COMPONENT24; break; case FORMAT_DEPTH_32: depthFormat = GL_DEPTH_COMPONENT32; break; case FORMAT_DEPTH_24_STENCIL_8: depthFormat = GL_DEPTH24_STENCIL8; break; case FORMAT_DEPTH_32_STENCIL_8: depthFormat = GL_DEPTH32F_STENCIL8; break; } glGenTextures(1, &depthrenderbuffer); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); glTexImage2D(GL_TEXTURE_2D, 0, depthFormat, createInfo.width, createInfo.height, 0, GL_DEPTH_COMPONENT, GL_FLOAT, 0); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MAG_FILTER, GL_NEAREST); glTexParameteri(GL_TEXTURE_2D, GL_TEXTURE_MIN_FILTER, GL_NEAREST); glBindTexture(GL_TEXTURE_2D, 0); glFramebufferTexture(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, depthrenderbuffer, 0); } if (createInfo.numColorTargets > 0) glDrawBuffers(createInfo.numColorTargets, DrawBuffers); else glDrawBuffer(GL_NONE); if (glCheckFramebufferStatus(GL_FRAMEBUFFER) != GL_FRAMEBUFFER_COMPLETE) std::cout << "Framebuffer Incomplete\n"; glBindFramebuffer(GL_FRAMEBUFFER, 0); width = createInfo.width; height = createInfo.height; } // ... // FBO Creation FramebufferCreateInfo gbufferCI; gbufferCI.colorFormats = gbufferCFs.data(); gbufferCI.depthFormat = FORMAT_DEPTH_32; gbufferCI.numColorTargets = gbufferCFs.size(); gbufferCI.width = engine.settings.resolutionX; gbufferCI.height = engine.settings.resolutionY; gbufferCI.renderPass = nullptr; gbuffer = graphicsWrapper->CreateFramebuffer(gbufferCI); // Bind glBindFramebuffer(GL_DRAW_FRAMEBUFFER, fbo); // Draw here... // Bind to textures glActiveTexture(GL_TEXTURE0); glBindTexture(GL_TEXTURE_2D, textures[0]); glActiveTexture(GL_TEXTURE1); glBindTexture(GL_TEXTURE_2D, textures[1]); glActiveTexture(GL_TEXTURE2); glBindTexture(GL_TEXTURE_2D, textures[2]); glActiveTexture(GL_TEXTURE3); glBindTexture(GL_TEXTURE_2D, depthrenderbuffer); Here is an extract of my code. I can't think of anything else to include. I've really been butting my head into a wall trying to think of a reason but I can think of none and all my research yields nothing. Thanks in advance!
    • By Adrianensis
      Hi everyone, I've shared my 2D Game Engine source code. It's the result of 4 years working on it (and I still continue improving features ) and I want to share with the community. You can see some videos on youtube and some demo gifs on my twitter account.
      This Engine has been developed as End-of-Degree Project and it is coded in Javascript, WebGL and GLSL. The engine is written from scratch.
      This is not a professional engine but it's for learning purposes, so anyone can review the code an learn basis about graphics, physics or game engine architecture. Source code on this GitHub repository.
      I'm available for a good conversation about Game Engine / Graphics Programming
    • By C0dR
      I would like to introduce the first version of my physically based camera rendering library, written in C++, called PhysiCam.
      Physicam is an open source OpenGL C++ library, which provides physically based camera rendering and parameters. It is based on OpenGL and designed to be used as either static library or dynamic library and can be integrated in existing applications.
       
      The following features are implemented:
      Physically based sensor and focal length calculation Autoexposure Manual exposure Lense distortion Bloom (influenced by ISO, Shutter Speed, Sensor type etc.) Bokeh (influenced by Aperture, Sensor type and focal length) Tonemapping  
      You can find the repository at https://github.com/0x2A/physicam
       
      I would be happy about feedback, suggestions or contributions.

  • Popular Now