Sign in to follow this  

OpenGL Vertices, Normals and Indices

Recommended Posts

I'm trying to write a basic python script to take collada geometry data and put it in buffer format for openGL. I've ran into a problem that doesnt make sense to me.
I have
7858 vertices
9519 normals

It doesn't make sense to have more normals than vertices right? In order to specify indexes into the buffers for openGL both the vertex buffer and normal buffer must be the same size right?
Is there simply repeated data in the normals of the collada file that need to be removed?
Is it more complicated then just shifting data around? (i.e. do normals have to be recalculated?)

Any insight would help. Thanks in advance.

Share this post

Link to post
Share on other sites
Mussi    4409
If the format contains 1 normal per vertex it's possible, the number of indices should equal the number of normals then. For example, you have two triangles connected to each other trough a shared vertex; you'd have 5 unique vertices, 6 vertex indices and 6 normals.

Share this post

Link to post
Share on other sites
SmellyIrishMan    198
Think about a cube also.

A cube has 8 vertices, but there needs to be 3 normals at each of those vertices (for a total of 24 normals) if you want to get accurate shading results. Have a look at this image for an example of that. [url=""]Cube with proper normals.[/url] These additional normals are typically created when the angle between two normals on the same vertex break a certain threshold.

If you had just one averaged normal at each vertex then you get [url=""]this[/url] and that's going to give you some funky shading.

Share this post

Link to post
Share on other sites
Ahhhh. Thanks guys that helps out alot. I didn't think about having multiple normals per vertex for edges, but that makes sense now for lighting calculations. I had been using Mesh Labs to convert my content and I think they do average the normals in order to make #vertices = #normals. This will give bad lighting you say? The way I have been rendering models in openGL requires all of the buffers to be the same size because each buffer is indexed the same. What is the proper way to have multiple normals per vertex using this format?

I suppose there are two options
1)average them in some way (may give bad lighting)
2)repeat vertices for each unique normal (will be slower at runtime). not 100% sure this method would work, the newest vertex may overwrite the previous one?

Thanks for the help!

Share this post

Link to post
Share on other sites
RDragon1    1205
A better way to think of it is you have more normals than *positions*, and positions != vertices. A vertex is a unique combination of a postiion, normal, and whatever other attributes belong to the vertex (uv, color, etc)

Typically data formats (like collada) have a set of indices per vertex - so for a single vertex, it will index separately into the position stream, normal stream, etc. This is different than what GPUs support, which is a single index per vertex that indexes into every attribute stream (typically interleaved) with the same index.

When building an interleaved vertex buffer for a GPU, you'll end up duplicating attributes across vertices. My typical approach is to create an 'index tuple' per vertex when reading the collada data, the index tuple contains the index for each attribute into the source data for that vertex - from there it's easy to take each index tuple and create a unique vertex for the GPU.

Share this post

Link to post
Share on other sites
Okay, let me try to make sure I understand what you're saying.

For an index tuple you will have a format similar to collada, maybe something like
v = vertex
t = textureCoord
n = normal

(v1, v2, v3, n1, n2, n3, t1, t2)

would represent one unique vertex

Then one could use those tuples to generate their index buffer. Is it possible to save memory by taking advantage of repeated data via proper indexing? If the tuples are unique I would think the answer is no. Thanks for all of the help. I just want to avoid taking up extra memory by having a brute force script!

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 pseudomarvin
      I assumed that if a shader is computationally expensive then the execution is just slower. But running the following GLSL FS instead just crashes
      void main() { float x = 0; float y = 0; int sum = 0; for (float x = 0; x < 10; x += 0.00005) { for (float y = 0; y < 10; y += 0.00005) { sum++; } } fragColor = vec4(1, 1, 1 , 1.0); } with unhandled exception in nvoglv32.dll. Are there any hard limits on the number of steps/time that a shader can take before it is shut down? I was thinking about implementing some time intensive computation in shaders where it would take on the order of seconds to compute a frame, is that possible? Thanks.
    • By Arulbabu Donbosco
      There are studios selling applications which is just copying any 3Dgraphic content and regenerating into another new window. especially for CAVE Virtual reality experience. so that the user opens REvite or CAD or any other 3D applications and opens a model. then when the user selects the rendered window the VR application copies the 3D model information from the OpenGL window. 
      I got the clue that the VR application replaces the windows opengl32.dll file. how this is possible ... how can we copy the 3d content from the current OpenGL window.
      anyone, please help me .. how to go further... to create an application like VR CAVE. 
    • By cebugdev
      hi all,

      i am trying to build an OpenGL 2D GUI system, (yeah yeah, i know i should not be re inventing the wheel, but this is for educational and some other purpose only),
      i have built GUI system before using 2D systems such as that of HTML/JS canvas, but in 2D system, i can directly match a mouse coordinates to the actual graphic coordinates with additional computation for screen size/ratio/scale ofcourse.
      now i want to port it to OpenGL, i know that to render a 2D object in OpenGL we specify coordiantes in Clip space or use the orthographic projection, now heres what i need help about.
      1. what is the right way of rendering the GUI? is it thru drawing in clip space or switching to ortho projection?
      2. from screen coordinates (top left is 0,0 nd bottom right is width height), how can i map the mouse coordinates to OpenGL 2D so that mouse events such as button click works? In consideration ofcourse to the current screen/size dimension.
      3. when let say if the screen size/dimension is different, how to handle this? in my previous javascript 2D engine using canvas, i just have my working coordinates and then just perform the bitblk or copying my working canvas to screen canvas and scale the mouse coordinates from there, in OpenGL how to work on a multiple screen sizes (more like an OpenGL ES question).
      lastly, if you guys know any books, resources, links or tutorials that handle or discuss this, i found one with marekknows opengl game engine website but its not free,
      Just let me know. Did not have any luck finding resource in google for writing our own OpenGL GUI framework.
      IF there are no any available online, just let me know, what things do i need to look into for OpenGL and i will study them one by one to make it work.
      thank you, and looking forward to positive replies.
    • By fllwr0491
      I have a few beginner questions about tesselation that I really have no clue.
      The opengl wiki doesn't seem to talk anything about the details.
      What is the relationship between TCS layout out and TES layout in?
      How does the tesselator know how control points are organized?
          e.g. If TES input requests triangles, but TCS can output N vertices.
             What happens in this case?
      In this article,
      the isoline example TCS out=4, but TES in=isoline.
      And gl_TessCoord is only a single one.
      So which ones are the control points?
      How are tesselator building primitives?
    • By Orella
      I've been developing a 2D Engine using SFML + ImGui.
      Here you can see an image
      The editor is rendered using ImGui and the scene window is a sf::RenderTexture where I draw the GameObjects and then is converted to ImGui::Image to render it in the editor.
      Now I need to create a 3D Engine during this year in my Bachelor Degree but using SDL2 + ImGui and I want to recreate what I did with the 2D Engine. 
      I've managed to render the editor like I did in the 2D Engine using this example that comes with ImGui. 
      3D Editor preview
      But I don't know how to create an equivalent of sf::RenderTexture in SDL2, so I can draw the 3D scene there and convert it to ImGui::Image to show it in the editor.
      If you can provide code will be better. And if you want me to provide any specific code tell me.
  • Popular Now