Hello,
I have an issue with an "engine" that I "wrote" , the problem is that the 3D models are not rendered (.obj) , and this only occurs on nVidia graphic cards ,I only tried on GT 220, and GT 430, I also tried running the application on an ATI video card and it has no problems, also the shaders are compiling correctly. The OpenGL context is actually initializing cause I can see the glClear color.
If you guys can help me with any information about his problem , or if you encountered this before please help.
Thank You!
0
OpenGL Not Rendering Models
Started by Bogdan.Vlad, Oct 31 2012 05:05 AM
11 replies to this topic
Sponsor:
#2 Members - Reputation: 4750
Posted 31 October 2012 - 06:03 AM
It is hard to tell a problem from text only. Could you please provide some comparision screenshots ? Have you checked for opengl errors ? There're always differences between ati and nvidia GPUs and it needs some time to fix all issues which runs on only one plattform.
Ashaman
My game: Gnoblins
Developer journal about Gnoblins
Small goodies: Simple alpha transparency in deferred shader
My game: Gnoblins
Developer journal about Gnoblins
Small goodies: Simple alpha transparency in deferred shader
#3 Members - Reputation: 114
Posted 31 October 2012 - 06:40 AM
After checking for OpenGL errors, I managed to pinpoint the problem to this line of code :
[source lang="cpp"]glVertexAttribPointer ( 0, 3, GL_FLOAT, GL_FALSE, 0, (void*)0 );[/source]
which is the vertex attribute buffer. It just says "inavlid operation".
[source lang="cpp"]glVertexAttribPointer ( 0, 3, GL_FLOAT, GL_FALSE, 0, (void*)0 );[/source]
which is the vertex attribute buffer. It just says "inavlid operation".
Edited by Bogdan.Vlad, 31 October 2012 - 06:42 AM.
#4 Members - Reputation: 4750
Posted 31 October 2012 - 08:02 AM
1. Check if you don't call this between a call of glBegin and glEnd.
2. Check for errors before this call and after this call, because the error will refer to the last ocurred error, which could be produced by a previous ogl api call .
2. Check for errors before this call and after this call, because the error will refer to the last ocurred error, which could be produced by a previous ogl api call .
Edited by Ashaman73, 31 October 2012 - 08:03 AM.
#5 Members - Reputation: 114
Posted 31 October 2012 - 08:56 AM
This function is called in the rendering loop, and I have two error checks before and after the function.
[source lang="java"]CHECKOGLERRORS;glVertexAttribPointer( ... );CHECKOGLERRORS;[/source]
I am not sure what the last parameter should do and how I could change it because I think that's the problem.
[source lang="java"]CHECKOGLERRORS;glVertexAttribPointer( ... );CHECKOGLERRORS;[/source]
I am not sure what the last parameter should do and how I could change it because I think that's the problem.
Edited by Bogdan.Vlad, 31 October 2012 - 09:03 AM.
#6 Members - Reputation: 501
Posted 31 October 2012 - 09:59 AM
The last parameter, unless I'm sadly mistaken, is a pointer to the beginning of the data. If this is part of a buffer, it gets treated more as an offset then a direct pointer to memory. (void*)0 simply tells it "start at the beginning of the buffer" so if you have a vertex struct, the very first data entry in the struct should be this attribute. Typically when I get an error there (and I use only nvidia cards), it's because I've failed to enable that vertex array OR because I have passed an invalid value (like 8 instead of 3 floats). Be sure also that your shader program uses a vec3 when you pass it those 3 floats.
EDIT: Just though, also make sure that the layout of your shader program matches the order of the attribute arrays. Thus, attribute 0 must be a vec3 or other 3 float containing data type.
EDIT: Just though, also make sure that the layout of your shader program matches the order of the attribute arrays. Thus, attribute 0 must be a vec3 or other 3 float containing data type.
Edited by Zouflain, 31 October 2012 - 10:00 AM.
#7 Members - Reputation: 114
Posted 31 October 2012 - 10:07 AM
After browsing some forums I found out that nVidia enforces the use of use vao + vbo with 3.x. with the new drivers. The problem is that I don't know what VAO is or where I should use it , I am already using VBO if you guys can help by pointing me in the right direction on how I should use VAO I would appreciate it very much.
#8 Members - Reputation: 190
Posted 31 October 2012 - 11:41 AM
That's probably what your issue is. Just call glCreateVertexArray to create a VAO, and then glBindVertexArray to bind it before you do your glBindBuffer, glEnableVertexAttribArray and glVertexPointer calls (Do this once). From that point on, all you have to do is bind the vertex array in your render loop and the rest is of the state (which was saved by making those calls with a VAO bound) is set up automatically.
#9 Members - Reputation: 451
Posted 31 October 2012 - 12:24 PM
The reason vertex array objects were introduced is to have less traffic in the binding of your attribute and index buffers, so you can just enable a VAO, bind all the buffers the way you want for that VAO and then just switch between different VAOs. I don't get why it was enforced; there's no "default VAO" that you could just use if you only want to render a single set of geometry, but that's the way it is.
Koehler already told what functions to use and what to do, I just wanted to clear up what VAOs are around for
Koehler already told what functions to use and what to do, I just wanted to clear up what VAOs are around for
#11 Moderators - Reputation: 14300
Posted 01 November 2012 - 07:27 AM
Because the specification tells them to --I don't get why it was enforced
The default vertex array object (the name zero) is also deprecated.
Calling VertexAttribPointer when no vertex array object is bound will generate an INVALID OPERATION error.
ATI is wrongly bending the rules of the specification in this case, so they're the ones at fault, not nVidia.
