Sign in to follow this  
Followers 0
Vincent_M

OpenGL
glGetError() INVALID_OPERATION (1282)

6 posts in this topic

OpenGL doesn't appear to want to render any triangles to the screen anymore. It'll render lines for my models' bones and normals just fine, however, but no triangles...

 

I checked glGetError() and it comes back with 1282, and a quick google reveals that this could be caused by some driver issues, however, I'm not sure. I was experimenting with some render target code before I noticed the issue, but again, I am getting some things to show up onscreen. I'm not even sure if error 1282 is the cause of this issue either. I've also tried restarting my computer.

 

Any ideas?

 

 

EDIT: A quicker looks reveals that the triangles are appearing, it's just that everything is rendered pure-black. There's one mesh that doesn't appear black, however.

Edited by Vincent_M
0

Share this post


Link to post
Share on other sites
glGetError returns the current error state of the OpenGL state machine. After calling glGetError, the error state reverts to GL_NO_ERROR and it will remain so until an OpenGL function is called which sets an error state.

If you find an unexpected error state you need to find the function(s) that set it. At some point glGetError is GL_NO_ERROR right before a GL call but not afterwards. This function is not used correctly.

It's probably not a bad idea to have (as a bare minimum solution) something like assert(glGetError() == GL_NO_ERROR); after each GL call. That will immediately complain about error conditions in debug builds but compile down to nothing in release builds.
3

Share this post


Link to post
Share on other sites

Disable texturing before drawing non-textured things? And enable it.

 

glDisable(TEXTURE_2D);

 

But I guess we need more info.

Edited by Nercury
0

Share this post


Link to post
Share on other sites

most likely you forget to bind some necessary data to the current shader, pls post your code

render for debugging with glPolygonmode in wireframe, helps alot

(and dont use black as background color ;D )

0

Share this post


Link to post
Share on other sites

I've got to admit that this was the first time I've actually used glGetError() to track stuff down, but once I realized it holds the last error, I kept running it through my initialization code until I found the method that does it. Calling glGetError() after each gl* call is expensive on OES implementations, so if I do that, I'll have to setup a bunch of #ifdef preprocessors so that I can run my builds w/o being bogged down.

 

As far as glDisable(GL_TEXTURE_2D), I've been checking that, but this where I think the issue could lie because I actually don't call commonly used glEnable/glDisable states directly. Instead, I have my own method that holds a synchronization variable to determine whether the state is already enabled before calling glEnable(), and vice-versa. This meant to cull unnecessary calls for OES builds. I think something could be wrong with glBindTexture because I modified one of my wrapper methods recently for that particular call. I'll also have to check glActiveTexture's wrapper function...

 

My models also don't use just textures directly, they use a Material object that is configured to work with the corresponding config of my uber shader built for that model to render. My Material class has some logic when uploading texture types that don't exist across each mesh in my model (uber shaders work at the per-model level for efficiency). So, if some parts of my model uses normal mapping, but others don't, instead of loading two shaders, I just load one with normal mapping, and for materials that don't have normal maps associated with it, it'll send a default 2x2 normal map. If I'm using diffuse maps, then they default meshes without ambient maps to a white texture.

 

These textured vertices aren't lit, however, and I know it's going through the lighting shader too, so I think it's some sort of GL state issues like you've all pointed out.

1

Share this post


Link to post
Share on other sites

glGetError returns the current error state of the OpenGL state machine. After calling glGetError, the error state reverts to GL_NO_ERROR and it will remain so until an OpenGL function is called which sets an error state.

 

That is not entirely correct.

 

If you check http://www.opengl.org/sdk/docs/man/xhtml/glGetError.xml, you'll find that more than one error may be recorded by OpenGL, and that glGetError() should be called in a loop until GL_NO_ERROR is returned.

2

Share this post


Link to post
Share on other sites
I've only had 1 OpenGL error at once, but I was thinking it acts more like a stack that'll show the most current out of a queue up to some defined max
0

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  
Followers 0

  • Similar Content

    • By recp
      Hi,
      I'm working on new asset importer (https://github.com/recp/assetkit) based on COLLADA specs, the question is not about COLLADA directly
      also I'm working on a new renderer to render (https://github.com/recp/libgk) imported document.
      In the future I'll spend more time on this renderer of course, currently rendering imported (implemented parts) is enough for me
      assetkit imports COLLADA document (it will support glTF too),
      importing scene, geometries, effects/materials, 2d textures and rendering them seems working
      My actual confusion is about shaders. COLLADA has COMMON profile and GLSL... profiles,
      GLSL profile provides shaders for effects so I don't need to wory about them just compile, link, group them before render

      The problem occours in COMMON profile because I need to write shaders,
      Actually I wrote them for basic matrials and another version for 2d texture
      I would like to create multiple program but I am not sure how to split this this shader into smaller ones,

      Basic material version (only colors):
      https://github.com/recp/libgk/blob/master/src/default/shader/gk_default.frag
      Texture version:
      https://gist.github.com/recp/b0368c74c35d9d6912f524624bfbf5a3
      I used subroutines to bind materials, actually I liked it,
      In scene graph every node can have different program, and it switches between them if parentNode->program != node->program
      (I'll do scene graph optimizations e.g.  view frustum culling, grouping shaders... later)

      I'm going to implement transparency but I'm considering to create separate shaders,
      because default shader is going to be branching hell
      I can't generate shader for every node because I don't know how many node can be exist, there is no limit.
      I don't know how to write a good uber-shader for different cases:

      Here material struct:
      struct Material { ColorOrTexture emission; ColorOrTexture ambient; ColorOrTexture specular; ColorOrTexture reflective; ColorOrTexture transparent; ColorOrTexture diffuse; float shininess; float reflectivEyety; float transparency; float indexOfRefraction; }; ColorOrTexture could be color or 2d texture, if there would be single colorOrTex then I could split into two programs,
      Also I'm going to implement transparency, I am not sure how many program that I needed

      I'm considering to maintain a few default shaders for COMMON profile,
      1-no-texture, 2-one of colorOrTexture contains texture, 3-........

      Any advices in general or about how to optimize/split (if I need) these shaders which I provied as link?
      What do you think the shaders I wrote, I would like to write them without branching if posible,
      I hope I don't need to write 50+ or 100+ shaders, and 100+ default programs

      PS: These default shaders should render any document, they are not specific, they are general purpose...
             I'm compiling and linking default shaders when app launched

      Thanks
    • By CircleOfLight97
      Hi guys,
      I would like to contribute to a game project as a developer (open source possibly). I have some experiences in C/C++ in game development (perso projects). I don't know either unreal or unity but I have some knowledges in opengl, glsl and shading theory as I had some courses at university regarding to that. I have some knowledges in maths and basic in physics. I know a little how to use blender to do modelling, texturing and simple game assets (no characters, no animation no skinning/rigging). I have no game preferences but I like aventure game, dungeon crawler, platformers, randomly generated things. I know these kind of projects involve a lot of time and I'd be really to work on it but if there are no cleary defined specific design goals/stories/gameplay mechanics I would like to not be part of it x) and I would rather prefer a smaller but well defined project to work on that a huge and not 'finishable' one.
      CircleOfLight97
    • By gamesthatcouldbeworse
      Hi, I finally released KILL COMMANDO on gamejolt for free. It is a retro-funsplatter-shooter with C64 style. Give it a try.
    • By phil67rpg

      void TimerFunction(int value) {  glutPostRedisplay();  glutTimerFunc(1000, TimerFunction, 1); } void drawScene() {  glClear(GL_COLOR_BUFFER_BIT);      drawScene_bug();  TimerFunction(1);  eraseScene_bug(); // drawScene_bug_two(); // eraseScene_bug_two(); drawScene_ship(); drawScene_bullet();  glutSwapBuffers(); }
  • Popular Now