• Advertisement
Sign in to follow this  

OpenGL Buffer / Shader Issues [C# OpenTK]

This topic is 2257 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Preface: I was happily working in OpenGL 3.3 until not enough laptops at the place I work at could support OpenGL 3.3. So I wanted to convert my code to work with OpenGL 2.0 which most of the laptops at my work support.

So I basically created a "Capabilities" class with a bunch of static flags to indicate what the context could and couldn't do. Then went through and added branching for certain capabilities. Whether or not VAOs work, instancing with glDrawElementsInstanced or Pseudo-instancing, glGenerateMipMaps... etc etc)

When I ran my monstrosity it turned all my geometry into soup.

So I took everything out except for the simplest shader / mesh I had. Which was a really thin quad used like a line to help me test ray picking.

It too doesn't look like a line.


It does the weird change shape as I move the camera around thing I've seen before so I'm suspecting the problem to be in the realm of the shader.

Just in case I read the vertices from the VBO back in and displayed them, they were nice and line like.

VBO Dump:
<4.960452, 4.932934, 4.933001>
<1.110205, -1.596217, -1.589712>
<4.960452, 4.933934, 4.933001>
<1.110205, -1.595217, -1.589712>

So I also outputed the shader program information

Shader Program 51
Uniform 0: Color @ 0
Uniform 1: Projection @ 1
Uniform 2: View @ 2
Uniform 3: World @ 3
Vertex Attributes:
0: FloatVec4 InPosition

The uniforms are there and the attributes are there, so the shader builds fine.

I render said line like this.

Shaders.SolidShader.Begin(); //Just calls GL.UseProgram
Shaders.SolidShader["View"].Set(cam.View); //Calls GL.UniformMatrix4(); on the correct uniform
Shaders.SolidShader["Color"].Set(color); //Really just a vec4
LineBuffer.RenderGeometry(); //Where I think the culprit is.
Shaders.SolidShader.End(); //uses program 0

I wrapped it up like XNA's Effect class to make shaders a bit more usable.

RenderGeometry looks like this...

public void RenderGeometry()
if (!Capabilities.CanUseVAO)
BindVBO(); //GL.BindBuffer(BufferTarget.ArrayBuffer, ID);
BindIBO(); //GL.BindBuffer(BufferTarget.ElementArrayBuffer, ID);
Format.UseFormat(); //See below
Format.Bind(); //Binds the VAO

GL.DrawElements(BeginMode.Triangles, TriangleCount*3, DrawElementsType.UnsignedShort, 0);

if (!Capabilities.CanUseVAO)

I'd swear I only need "TriangleCount" and not "TriangleCount*3" but it never rendered the whole geometry without it.

And finally UseFormat, kinda a monster. But I basically cloned the FVF bitfield idea from DirectX since it was a rather quick way to express the very few vertex types I use. I've stripped out the important part, the actual OpenGL calls.

int Offset = 0;//Our data is interleaved so we keep track of the starting offset
if ((format & VertexFormat.Position) == VertexFormat.Position)
GL.VertexAttribPointer(0, 3, VertexAttribPointerType.Float, false, LastVertexSize, 0);
GL.EnableVertexAttribArray(0); //Position is attrib 0 (Shader usage maps "InPosition" to this attrib)
Offset += 12; //3x4 bytes
if ((format & VertexFormat.Texture) == VertexFormat.Texture)
GL.VertexAttribPointer(1, 2, VertexAttribPointerType.Float, false, LastVertexSize, Offset);
GL.EnableVertexAttribArray(1); //Texturecoordinates are attrib 1
Offset += 8;//2x4 bytes
if ((format & VertexFormat.Normal) == VertexFormat.Normal)
GL.VertexAttribPointer(2, 3, VertexAttribPointerType.Float, false, LastVertexSize, Offset);
GL.EnableVertexAttribArray(2); //Normals are attrib 2
Offset += 12;//3x4 bytes
if ((format & VertexFormat.Tangent) == VertexFormat.Tangent) //These are for normal mapping but I don't use them yet
GL.VertexAttribPointer(3, 3, VertexAttribPointerType.Float, false, LastVertexSize, Offset);
Offset += 12;
if ((format & VertexFormat.BiTangent) == VertexFormat.BiTangent)
GL.VertexAttribPointer(4, 3, VertexAttribPointerType.Float, false, LastVertexSize, Offset);
Offset += 12;

If you didn't TL;DR; and still have your retinas intact from looking at my [s]code [/s]spaghetti. I'd love some help because I'm stumped.

Share this post

Link to post
Share on other sites
I have a feeling that your problem lies in the VBO coordinates. Quad vertices must lie on a single plane and should form a convex polygon, i.e.

1 2

4 3


1 2

3 4

Otherwise, results are undefined.

(Btw, quads are deprecated in GL3.x).

Share this post

Link to post
Share on other sites
Hmm good thought, I however miss-typed. In my head I think of it as a quad however its rendered with two triangles.

It also occurred to me I forgot to post the actual shader code, the error could be in there.

I basically went through and replaced "in" and "out" with "varying" and "attribute" as needed and made use of gl_FragColor instead of my custom FragColor variable.

Vertex Shader:

uniform mat4 World;
uniform mat4 View;
uniform mat4 Projection;

attribute vec4 InPosition;
attribute vec2 InTextureCoordinate;
attribute vec3 InNormal;

varying vec3 Normal;
varying vec2 TextureCoordinate;
varying vec4 FragPos;

void main ()
TextureCoordinate = InTextureCoordinate;
gl_Position = (Projection * View * World) * InPosition;
FragPos = World * InPosition;
Normal = mat3 (World) * InNormal;

Fragment Shader:

uniform vec4 Color;

void main ()
gl_FragColor = Color;

The extra stuff in the vertex shader is used for various other fragment shaders.

The working OpenGL 3.x shaders are at these codepad links:
Vert: http://codepad.org/AAY0wP7Z
Frag: http://codepad.org/Qm4qJTdq

Share this post

Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By LifeArtist
      Good Evening,
      I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
      First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
      I am really stucked right now because of the fundamental question:
      Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
      If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on. 
      In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
      Should I treat those debug objects as entities/components?
      For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
      Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
    • By QQemka
      Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
      Let's go:
      Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
      Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
      Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
      What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
      There were several more but i forgot/solved them at time of writing
      Thanks in advance
    • By RenanRR
      Hi All,
      I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
      I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
      Vertex Shader:
      #version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
      ..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);  
      So, some doubts:
      - Why use it like that?
      - Is it okay to manipulate the camera that way?
      -in this way, are not the vertex's positions that changes instead of the camera?
      - I need to pass MVP to all shaders of object in my scenes ?
      What it seems, is that the camera stands still and the scenery that changes...
      it's right?
      Thank you
    • By dpadam450
      Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

      int rgbValue = int(textureSample.w);//4 bytes of data packed as color
      // algorithm might not be correct and endianness might need switching.
      vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
      extractedData /= 255.0f;
    • By Devashish Khandelwal
      While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
      Anyone has any idea .. what should I do?
  • Advertisement