Sign in to follow this  

OpenGL Vao render problem on ATI graphic card

Recommended Posts

andeandr100    196

This code runs with Opengl 3.2

The code works when i use Nvidia graphic card on both Windows 7 and Ubuntu.

But when i tested on my laptop with Radeon HD 5650 on windows 7 only 50% of my vao buffer was rendered to the screen the other 50% did not render at all.

I have tested to run with different shaders and changed how i created my vao buffer but i have had no luck finding out what is the problem.

Can anyone see what can be the problem because i have viewed me blind on this problem for a few days.


//Vao buffer

//I have assumed that my vertex and index creation step works due to they have 
//been  successfully rendered on different machine with different OS
//int vertexSize = 8
//float* _pData; /*float x,y,z; float r,g,b; float ux, uy;*/
//unsigned int* _pIndex;

//vao creation
glGenVertexArrays(1, &_vao);

//Bind the VBO and setup pointers for the VAO
glGenBuffers(1, &_vbo);
glBindBuffer(GL_ARRAY_BUFFER, _vbo);
glBufferData(GL_ARRAY_BUFFER, _numVertex * vertexSize * sizeof(float), pData, GL_DYNAMIC_DRAW);

glVertexAttribPointer( vertexId, 3, GL_FLOAT, GL_FALSE, sizeof(float) * vertexSize, BUFFER_OFFSET(0));//vertex
glVertexAttribPointer( vertexColorId, 3, GL_FLOAT, GL_FALSE, sizeof(float) * vertexSize, BUFFER_OFFSET(sizeof(float)*3));//Color
glVertexAttribPointer( UvCordId, 2, GL_FLOAT, GL_FALSE, sizeof(float) * vertexSize, BUFFER_OFFSET(sizeof(float)*6));//Uv

glEnableVertexAttribArray( vertexId );
glEnableVertexAttribArray( vertexColorId );
glEnableVertexAttribArray( UvCordId );

//Bind the IBO for the VAO
glGenBuffers(1, &_ibo);
glBindBuffer(GL_ELEMENT_ARRAY_BUFFER, _ibo);
glBufferData(GL_ELEMENT_ARRAY_BUFFER, _numIndex * sizeof(GLuint), _pIndex, GL_DYNAMIC_DRAW);


//render code

//Bind shader
glUseProgramObjectARB( _program );
glUniformMatrix4fv( _projViewLoc,  1, false, _projectionCameraMatrix );
glUniformMatrix4fv( _modelViewLoc,  1, false, _modelMatrix );
glUniform1i( _textureLoc, 0 );

//Bind texture
glActiveTexture( GL_TEXTURE0);
glBindTexture(GL_TEXTURE_2D, _textureId );

//Bind and render vao
glBindVertexArray( _vao );
glDrawRangeElements(GL_TRIANGLES, 0, _numVertex, _numIndex, GL_UNSIGNED_INT, NULL);


//vertex shader
#version 140
uniform mat4 projCamView, modelMatrix;
in vec3 position;
in vec3 inColor;
in vec2 inTextCord;
out vec2 TextCord;
out vec3 vertexColor;
void main()
	TextCord = inTextCord;
	vertexColor = inColor;
	gl_Position = projCamView * modelMatrix * vec4(position,1.0f);

//fragment shader
#version 140
uniform sampler2D myTexture;
in vec2 TextCord;
in vec3 vertexColor;
out vec4 Frag_Color;
void main()
	vec4 textureColor = texture2D(myTexture, TextCord);
	Frag_Color = vec4( textureColor.rgb * vertexColor, textureColor.a );

Share this post

Link to post
Share on other sites
mhagain    13430

From a quick look, I can see that you're mixing the old GL_ARB_shader_objects extension with more modern code, in particular expecting that old extension to support GLSL version 140.  I'd suggest that you initially stop doing that and use the core GL functions instead, since GLSL 140 didn't exist when GL_ARB_shader_objects was specified, and you shouldn't expect it to be supported.

Share this post

Link to post
Share on other sites
andeandr100    196

Have taken your advice and removed all ARB extension from the project.

Sadly it did not fix the problem.


How the program look on my computer with Nvidia graphic card.


How it looks on my laptop with ATI graphic card






Share this post

Link to post
Share on other sites
Lodeman    1596



It might be interesting for you to download Cgc in order to find potential issues with your shaders:

I actually had the reverse problem, it was working on my Radeon card, but it wasn't for other people their Nvidia.

An exaple of how to use cgc with command line:

C:\Users\Kevin>cgc -oglsl -strict -glslWerror -nocode -profile gp5fp "C:\Users\Kevin\Documents\Test\Shaders\test.frag"
^for fragment shaders
C:\Users\Kevin>cgc -oglsl -strict -glslWerror -nocode -profile gp5vp "C:\Users\Kevin\Documents\Test\Shaders\test.vert"
^for vertex shaders

This method has helped me eliminate any issues I've had with "incompatibility".


Good luck and cheers!

Share this post

Link to post
Share on other sites
shacktar    1512

Judging by your VAO setup and rendering snippets, it looks like you're assuming that the calls to glEnableVertexAttribArray are bound to the particular VAO. They are not. In fact, that state is not even bound to the active shader program.


I had a bug once that revolved around this assumption. It turned out that calls to glEnableVertexAttribArray while one shader was active was causing some driver state trampling when I was rendering using another shader.


This might be your issue if you have multiple shaders. If so, then perhaps you can try disabling the currently enabled attributes when switching shaders.

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