Sign in to follow this  

OpenGL Opengl failing to draw in debug mode

Recommended Posts

rocklobster    415
Hi guys,

I've got a problem with my debug mode in Visual Studio 2010. It seems that my models only draw when i'm in release mode, everytime i'm in debug mode the drawing is either really weird, or i can't see anything on screen.

This is my drawing code. Because each game object belongs to a node in a scene graph (i know its just a temporary solution) we have to traverse back through to its base node saving the matrices at each state, then we multiply down to get the child node's correct orientation. This works fine in release mode and the model is all oriented correctly, however in debug mode, I can't even see the model. If i remove all the matrix multiplications i can see the model, but everything isn't oriented correctly.

[code]for (int i = 0; i < (signed)m_drawBuffer.size(); i++)
GameObject* go = m_drawBuffer[i];
if (go->getComponent("ComponentRender") != NULL)
ComponentRender* render = (ComponentRender*)go->getComponent("ComponentRender");

for (int i = 0; i < render->modelResourceSize(); i++)
Matrix4<float> temp;
SceneNode* pos2 = go->getNode()->getRoot();
stack<Matrix4<float> > s;
while(pos2 != NULL)
Matrix4<float> temp2=;
temp = temp2 * temp;
matrixStackPush(); // gl push matrix
int delta = render->getModel(i)->getVBOID();
if (render->getModel(i)->getVBOID() != -1)
drawVBO(render->getModel(i)->getVBOID(), GL_TRIANGLES);
matrixStackPop(); // gl pop matrix

Help would be greatly appreciated i'm dying trying to work this one out!

- Cheers

Share this post

Link to post
Share on other sites
reloadead    1795
Mostly this is the other way around that in debug stuff works, but release mode makes things go nuts.. Have you initialized everything properly?

Share this post

Link to post
Share on other sites
rocklobster    415
I'm using SDL for the window so i thought that was causing problems. So i setup my window in main and the put the opengl init code right after and i'm still getting the same problem. I've removed the mult matrix calls and i can see the object fine in both release/debug, but as soon as i try and change the model view matrix i cant see the object in debug, or by tweaking the camera, i see a gigantic grey square on my screen that is always in the same position (happens on both of my computers).

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 povilaslt2
      Hello. I'm Programmer who is in search of 2D game project who preferably uses OpenGL and C++. You can see my projects in GitHub. Project genre doesn't matter (except MMO's :D).
    • By ZeldaFan555
      Hello, My name is Matt. I am a programmer. I mostly use Java, but can use C++ and various other languages. I'm looking for someone to partner up with for random projects, preferably using OpenGL, though I'd be open to just about anything. If you're interested you can contact me on Skype or on here, thank you!
      Skype: Mangodoor408
    • By tyhender
      Hello, my name is Mark. I'm hobby programmer. 
      So recently,I thought that it's good idea to find people to create a full 3D engine. I'm looking for people experienced in scripting 3D shaders and implementing physics into engine(game)(we are going to use the React physics engine). 
      And,ye,no money =D I'm just looking for hobbyists that will be proud of their work. If engine(or game) will have financial succes,well,then maybe =D
      Sorry for late replies.
      I mostly give more information when people PM me,but this post is REALLY short,even for me =D
      So here's few more points:
      Engine will use openGL and SDL for graphics. It will use React3D physics library for physics simulation. Engine(most probably,atleast for the first part) won't have graphical fron-end,it will be a framework . I think final engine should be enough to set up an FPS in a couple of minutes. A bit about my self:
      I've been programming for 7 years total. I learned very slowly it as "secondary interesting thing" for like 3 years, but then began to script more seriously.  My primary language is C++,which we are going to use for the engine. Yes,I did 3D graphics with physics simulation before. No, my portfolio isn't very impressive. I'm working on that No,I wasn't employed officially. If anybody need to know more PM me. 
    • By Zaphyk
      I am developing my engine using the OpenGL 3.3 compatibility profile. It runs as expected on my NVIDIA card and on my Intel Card however when I tried it on an AMD setup it ran 3 times worse than on the other setups. Could this be a AMD driver thing or is this probably a problem with my OGL code? Could a different code standard create such bad performance?
    • 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++.
      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.
  • Popular Now