Sign in to follow this  

OpenGL VBO normals issue

Recommended Posts

This is the first time I'm making a vbo and I bumped into a problem:

When rendering vbos, the object comes out 100% black.

The lookat/perspective matrices are loaded correctly.
Depth test is enabled and working.
I have enabled lighting and set the parameters for GL_LIGHT0.
The object loads correctly (from an .obj file) and has all the vertex positions/normals it needs.
The vbo/ibo generate without errors.
The position data seems correct (as far as I can tell from the black outline).
Using the silly opengl immediate mode the model renders correctly (perfect smooth lighting).
The mesh material has diffuse/ambient/specular values != (0,0,0,0).
The vert/frag/program get compiled and used before the rendering begins.

The vertex structure is the following:

struct Vertex
static const byte POSITION_OFFSET = 0;
static const byte NORMAL_OFFSET = sizeof(Vector3f);
static const byte TANGENT_OFFSET = 2 * sizeof(Vector3f);
static const byte UV_OFFSET = 3 * sizeof(Vector3f);
static const byte COLOR_OFFSET = 3 * sizeof(Vector3f) + sizeof(Vector2f);

Vector3f pos;
Vector3f nor;
Vector3f tan;
Vector2f uv;
Color color;

My code for the immediate mode rendering is:


for(int i = facei.size()-1; i > 0; i--)








and the vbo one:



glBindBufferARB(GL_ARRAY_BUFFER_ARB, rendObj.oglSurface->vboID); // for vertex coordinates

glVertexPointer(3, GL_FLOAT, sizeof(Vertex), Vertex::POSITION_OFFSET);

glNormalPointer(GL_FLOAT, sizeof(Vertex), (void*)Vertex::NORMAL_OFFSET);

glBindBufferARB(GL_ELEMENT_ARRAY_BUFFER_ARB, rendObj.oglSurface->iboID); // for indices

glDrawElements(GL_TRIANGLES, rendObj.oglSurface->cpuSurface->facei.size() * 3, GL_UNSIGNED_INT, 0);




and the shader used has the following source code:


"varying vec3 normal, lightDir, eyeVec; \n"
" \n"
"void main() \n"
"{ \n"
" normal = gl_NormalMatrix * gl_Normal; \n"
" \n"
" vec3 vVertex = vec3(gl_ModelViewMatrix * gl_Vertex); \n"
" \n"
" lightDir = vec3(gl_LightSource[0] - vVertex); \n"
" eyeVec = -vVertex; \n"
" \n"
" gl_Position = ftransform(); \n"
"} \n\0";



"varying vec3 normal, lightDir, eyeVec; \n"
" \n"
"void main (void) \n"
"{ \n"
" vec4 final_color = \n"
" (gl_FrontLightModelProduct.sceneColor * gl_FrontMaterial.ambient) + \n"
" (gl_LightSource[0].ambient * gl_FrontMaterial.ambient); \n"
" \n"
" vec3 N = normalize(normal); \n"
" vec3 L = normalize(lightDir); \n"
" \n"
" float lambertTerm = dot(N,L); \n"
" \n"
" if(lambertTerm > 0.0) \n"
" { \n"
" final_color += gl_LightSource[0].diffuse * \n"
" gl_FrontMaterial.diffuse * \n"
" lambertTerm; \n"
" \n"
" vec3 E = normalize(eyeVec); \n"
" vec3 R = reflect(-L, N); \n"
" float specular = pow( max(dot(R, E), 0.0), \n"
" gl_FrontMaterial.shininess ); \n"
" final_color += gl_LightSource[0].specular * \n"
" gl_FrontMaterial.specular * \n"
" specular; \n"
" } \n"
" \n"
" gl_FragColor = final_color; \n"
"} \n\0"


Both the immediate mode and vbo rendering is done in the same method, so there is no opengl state change between them (and, of course, I only use one of them and comment out the second when I'm testing).

One more thing that could have relevance is that if I replace the last line of the frag shader with "gl_fragColor = vec4(1.0,0.0,0.0,1.0)" I actually do get a full red mesh.

If anyone knows where I should search for the problem, any help would be appreciated. If I left out relevant information, I'll add it asap, just say.


Share this post

Link to post
Share on other sites
Ok, found out where the problem is, but I still don't get it:

When I pass the material color info I use:

glMaterialiv(GL_FRONT_AND_BACK, GL_AMBIENT, mat.ambientCol.ToGLintArray());
glMaterialiv(GL_FRONT_AND_BACK, GL_DIFFUSE, mat.diffuseCol.ToGLintArray());
glMaterialiv(GL_FRONT_AND_BACK, GL_SPECULAR, mat.specularCol.ToGLintArray());
glMaterialf(GL_FRONT_AND_BACK, GL_SHININESS, mat.shininess);

I did a little test, replacing that code with this:


float whitef[4] = {1.0f, 1.0f, 1.0f, 1.0f};

glMaterialfv(GL_FRONT_AND_BACK, GL_AMBIENT, whitef);

And ta-da, a wild beautiful mesh appears, lighted like never before.

After I replaced that code with


int whitei[4] = {255,255,255,255};

glMaterialiv(GL_FRONT_AND_BACK, GL_AMBIENT, whitei)


The mesh turned black again.

I don't get it: should I enable something special to be able to pass glMaterialiv parameters? I couldn't find any documentation on this... as far as I can tell, if glMaterialfv works, so should glMaterialiv. But in my case, it does not.

Share this post

Link to post
Share on other sites
I'm not sure what is wrong here, but it is clearer to define your own uniforms/attributes, much more easier than trying to switch OpenGL's state machine parameters. Define your own material/light parameters in your shaders.

Share this post

Link to post
Share on other sites
[quote name='Karim Kenawy' timestamp='1305452990' post='4811011']
I'm not sure what is wrong here, but it is clearer to define your own uniforms/attributes, much more easier than trying to switch OpenGL's state machine parameters. Define your own material/light parameters in your shaders.

Yep, I found out this thing about 15 mins ago. The 4.0 ogl doesn't even have them anymore.

Also, problem solved: apparently the glMaterial takes colors in the [0-MAX_GLINT] range, not in the [0-255]. I find it this very counter-intuitive, but maybe it's just me. So the problem was that my mesh had the float-equivalent color of 0.000000something instead of 1.0, like I thought it should be.

Share this post

Link to post
Share on other sites
[quote] I find it this very counter-intuitive, but maybe it's just me[/quote]
As stated before, stop using fixed function (glMaterial, glLight, glTexEnv).

Also, normally, people use the floating point version of glMaterial. Sounds like you need a "unsigned byte" version but that doesn't exist for glMaterial.

Share this post

Link to post
Share on other sites
[quote name='V-man' timestamp='1305463577' post='4811056']
[quote] I find it this very counter-intuitive, but maybe it's just me[/quote]
As stated before, stop using fixed function (glMaterial, glLight, glTexEnv).

Also, normally, people use the floating point version of glMaterial. Sounds like you need a "unsigned byte" version but that doesn't exist for glMaterial.

As I said, I will. And yea, an "unsigned byte" alternative would look pretty nice, since you usually store a color as a 4 [0-255] values. Thanks for the input!

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  

  • Announcements

  • Forum Statistics

    • Total Topics
    • Total Posts
  • Similar Content

    • By test opty
      Hi all,
      I'm starting OpenGL using a tut on the Web. But at this point I would like to know the primitives needed for creating a window using OpenGL. So on Windows and using MS VS 2017, what is the simplest code required to render a window with the title of "First Rectangle", please?
    • By DejayHextrix
      Hi, New here. 
      I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc.... 
      I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn? 
      How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want? 
      Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn. 
      So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started. 
      Dejay Hextrix 
    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
  • Popular Now