Sign in to follow this  

OpenGL Lock states in openGL

Recommended Posts

gatofedorento    155
Hello, I'm making a level editor and I came across a design doubt.

Like in UDK, I want my editor to change from fill the polygons to wireframes or to points in real time with just the press of a button, that's easy to do in openGL, the problem is that when i change to wireframes I want to be able to disable textures, color, etc.

In my implementation when the draw function of an object is called first it sets all the states it needs to (textures, color, etc) and then draws, I want to be able to lock these states so even though the draw functions calls them nothing happens, it's easy to do, I just need to cover the openGL functions with some of my own.

My questions are: is there a better way to do this? Am I falling in other things in my design about each draw functions sets up the states?

Share this post

Link to post
Share on other sites
Brother Bob    10344
I would say that this is a design problem by letting objects set up and draw themselves, yes.

The problem is that, unless you're doing very trivial state changes, you will have problems with that design. An object should not set up and draw itself. What you end up with is code at many different places that have to be kept in sync. For this design to work in your case, you need the wire-frame and state locking code at every place where this wire-frame and state locking must have effect. Every single place where you draw something has to be aware of it; possibly even places that are not supposed to be affected by this wire-frame and state locking mechanism so that they can revert to standard rendering if you're in the wrong state.

State management like this will explode to everywhere in your code for every non-trivial piece of state management if you let objects set up and draw themselves, because they now have to be aware of every state that directly affect them, and possibly even indirectly affect them.

Instead have a single point in your code that handles OpenGL. Instead of having object set up and draw themselves, have the object provide this single point with what is needed to draw the object (a vertex array for example) what states are required to draw it (for example a structure containing states like what shaders, colors, textures, materials, blending states and so on that describes how to draw the model). You now have a single point that can override an object's requested state for normal drawing with a basic color-less wire-frame setup when your application is in wire-frame mode. Your objects don't even have to be aware of wire-frame mode in the first place.

Share this post

Link to post
Share on other sites
gatofedorento    155
I think you misunderstood ( or maybe I misunderstood your explanation, sorry =( ) part of what I wrote.

But I got your point, it is indeed a bad design choice, and what you told me is a better way to do things, but anyway i will try to explain what I wanted to do in pseudo code and compare to your design:

[code]Renderer -> disableTextures
Renderer -> disableColor
Renderer -> renderWireframe
Renderer -> lockTexturesState
Renderer -> lockColorState
//at this point the wireframes will be ready to use without color and textures, now let's see what happens in the draw function of one of my object, let's say a terrain
Terrain -> enableTexture //this won't take effect because of the lock
Terrain -> setTexture //the texture will be set, but it won't do anything, because the texture is disabled
Terrain -> draw the mesh //which will be a wireframe
//now that the terrain is drawn I can unlock the states for the other elements in my screen to draw normally, let's say GUI for example
Renderer-> unlockTextures
Renderer -> unlockColor
GUI -> enableTextures
GUI -> setTexture
GUI -> draw //now everything will be draw normally

Instead of what I did up here every object in my scene could have a function that sets the states and another function that draws the mesh, and depending of the mode I have only the renderer would know what to do, and the code would be somehting like this:

if(state == FILL){
Renderer -> setFillMode
foreach(Element in Elements){
Element -> setupState
Element -> drawMesh
else if(state == WIREFRAME){
Renderer -> setWireFrameMode
foreach(Element in Elements){
Element -> drawMesh

I think the last piece of pseudo code seems indeed more clean and I wouldn't need the locks, which would avoid the programmer of causing state bugs.

Thanks for the help and sorry for the long post, I want to make sure I make good design choices, so I don't have the need to make huge refactorings later.

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