Sign in to follow this  
jbb

OpenGL Managing opengl contexts for more than one window

Recommended Posts

How do people manage multiple opengl contexts, if in fact they do?

My code has a 'Window' class, so, in theory at least, you can create two or more windows. Each window can have it's own pixel format and opengl context due to the way it works. Now the problem is that before making *every* call to opengl I have to check that the current gl context is the correct one, and if not do wglMakeCurrent to switch to it. Or else I have to make a function on 'Window' called something like 'makeActive' before I do any opengl operations on it. And be sure to always remember to do this.

My question is how do people cope with this? Is doing this very slow? Or do people generally not support more than one context in a program?

Secondly, it seems that on windows at least, you have to call opengl functions via function pointers obtained from wglGetProcAddress and those pointers can be *different* for each context if they have different pixel formats. I am using multisampled output window in my main window and intend in a debug mode to have a separate window that doesn't need to have that so I *will* be having different pixel formats. So I can't just slap them into a lot of global variables.

How do people cope with this?
Or do people in general decide that supporting multiple windows is more effort than it's worth and find alternative solutions?

Share this post


Link to post
Share on other sites
You can build GLEW in a way that it can deal with different function pointers, but that requires an additional context parameter in each OpenGL function call.

For games though I would try to do whatever I can to avoid having to deal with this issue. Why exactly do you need to do that anyway? Wouldn't it be far easier to have no multisampling in the pixel format and just use FBOs with/without multisampling?

Share this post


Link to post
Share on other sites

If I want to use multsampling on the output, don't I have to create a multisampled pixel format?
Or are you saying I can create a multisampled render-to-texture and render to that, and then somehow copy that to the display?
Won't that be slow?

Share this post


Link to post
Share on other sites
That's not an area I have much experience in, but if you do not create a texture to render on but a renderbuffer (which you can render to in an FBO but not use as a texture) you can blit extremely fast between renderbuffers (including the implicit renderbuffer of your window). Thta's pretty much what OpenGL already has to do anyway, but hidden from you. A monitor cannot display multiple samples per pixel. They must be collapsed into a single sample before display anyway.

I would have a look at the OpenGL wiki regarding multisampling, I remember reading it a while back and it cleared up a lot of misconceptions.

As far as I know, no one really does multisampling outside of FBOs anymore.

Share this post


Link to post
Share on other sites

Thanks, i looked into it now :)

That makes a lot of sense and makes things very much easier as I can basically pick a single pixel format and use that for all my windows and hard code it and forget about all this.

Hmm, does that mean I need a depth buffer on my render buffer and don't need to create my window with one...

Share this post


Link to post
Share on other sites

Hmm, does that mean I need a depth buffer on my render buffer and don't need to create my window with one...


You would need an additional renderbuffer (or a qualified texture) acting as depth buffer, yes, unless there is some kind of mixed color/depth format around (to my knowledge, there is no such thing). If you will only render to your FBOs, you do not need a depth buffer with your window's framebuffer.

Share this post


Link to post
Share on other sites

My question is how do people cope with this? Is doing this very slow? Or do people generally not support more than one context in a program?


People generally avoid it, and yes it is slow (depending on platform).

The magic global context which is both a device and a swap-chain is one of the over-arching worst design mistakes of OpenGL (which is really saying something) and one of the reasons that Vulkan is an entirely new API rather than a set of GL extensions. GL's design also complicates multi-threading renderers.

If you have a particular need for fancier application, I have to suggest that you use DirectX (9 or 11, your pick)instead. The API is just far better designed and handles such intricate tasks as multiple windows without surprise or problem. :)

Share this post


Link to post
Share on other sites

Thanks everyone.
I don't actually need this at all. As they say, I'm trying to make a game, not a general purpose engine, but it's always nice to separate components where possible and effective, so it seemed right to make a Window class which naturally lead to thinking what if the user makes more than one.

Well my game isn't going to, and it looks tricky, so I'll probably come up with an alternative interface that assumes only one "window", precluding the question even arising.

Still a useful discussion for me anyway, as it's lead to me looking into and understanding renderbuffers and fbo's and why I might use one :)

Share this post


Link to post
Share on other sites
Games don’t do this. Switching contexts is extremely slow, plus the overhead of whatever you are doing to check for the current context.
Not only this, but resources are not shared across contexts, so you would also need to keep track of which textures, vertex buffers, shaders, etc., are available given the current context.

Tools/editors may use multiple contexts, in which case you would use shared contexts. This is extremely easy to set up with Qt and allows you to have 1 window showing the model and other windows displaying the model textures, with different contexts each but able to share the resources (textures in this example) without having to load them once-per-context.


L. Spiro

Share this post


Link to post
Share on other sites

Thanks again all.

?Based on the comments I'm not going to try to support multiple windows :) My project doesn't need them anyway.

My problem is that I identified 'Window' as being a good abstraction of something I'd need my application to have and a common one. And once I did that it because natural to ask does it make sense to have more than one window in an application.... Yes, it makes sense.
And then the issue of how to implement it nagged and nagged at me leading to complete coding paralysis!
 

I have decided that I have no need to implement multiple windows/contexts in my project so I will not do.
?Having decided that it seems natural to merge window and context management into my 'Game' class as they don't really need their own identity and it's natural to have a single "Game" object created in a program but not so much a 'Window'

Share this post


Link to post
Share on other sites

Thanks again all.

?Based on the comments I'm not going to try to support multiple windows :) My project doesn't need them anyway.
 

You can render to any amount of windows by their window handle being identified and provided to a context, as context can get succesfully updated to output onto a new window.

This window can be a background of a modal form etc (I once even hijacked IE browser window to output my Present(), this was in DX though)

Multiple separate contexts do not make much sense unless they make sense.

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  

  • Forum Statistics

    • Total Topics
      627782
    • Total Posts
      2979033
  • Similar Content

    • By JFT
      Hi,

      I am trying to optimize shadow mapping for an rts-view (nearly top down) with directional light.

      My approach so far is to intersect the camera view frustum with the plane of the terrain on which all the units are moving and
      fit a box around the four intersection points:

      Then I use the center of the box and the light direction to construct a view matrix.
      To construct the orthographic projection matrix I use the corners of my box. 

      With that I somehow do not get the wanted results (no shadows) /shadow map is not correctly created for the view of the camera.
      I think I am maybe missing some translation/rotation?

      Is there a better way for rts-views with a single shadow map ?

      Thanks for your help beforehand!
    • By lonewolff
      Hi guys,
      With OpenGL not having a dedicated SDK, how were libraries like GLUT and the likes ever written?
      Could someone these days write an OpenGL library from scratch? How would you even go about this?
      Obviously this question stems from the fact that there is no OpenGL SDK.
      DirectX is a bit different as MS has the advantage of having the relationship with the vendors and having full access to OS source code and the entire works.
      If I were to attempt to write the most absolute basic lib to access OpenGL on the GPU, how would I go about this?
    • By DelicateTreeFrog
      Hello! As an exercise for delving into modern OpenGL, I'm creating a simple .obj renderer. I want to support things like varying degrees of specularity, geometry opacity, things like that, on a per-material basis. Different materials can also have different textures. Basic .obj necessities. I've done this in old school OpenGL, but modern OpenGL has its own thing going on, and I'd like to conform as closely to the standards as possible so as to keep the program running correctly, and I'm hoping to avoid picking up bad habits this early on.
      Reading around on the OpenGL Wiki, one tip in particular really stands out to me on this page:
      For something like a renderer for .obj files, this sort of thing seems almost ideal, but according to the wiki, it's a bad idea. Interesting to note!
      So, here's what the plan is so far as far as loading goes:
      Set up a type for materials so that materials can be created and destroyed. They will contain things like diffuse color, diffuse texture, geometry opacity, and so on, for each material in the .mtl file. Since .obj files are conveniently split up by material, I can load different groups of vertices/normals/UVs and triangles into different blocks of data for different models. When it comes to the rendering, I get a bit lost. I can either:
      Between drawing triangle groups, call glUseProgram to use a different shader for that particular geometry (so a unique shader just for the material that is shared by this triangle group). or
      Between drawing triangle groups, call glUniform a few times to adjust different parameters within the "master shader", such as specularity, diffuse color, and geometry opacity. In both cases, I still have to call glBindTexture between drawing triangle groups in order to bind the diffuse texture used by the material, so there doesn't seem to be a way around having the CPU do *something* during the rendering process instead of letting the GPU do everything all at once.
      The second option here seems less cluttered, however. There are less shaders to keep up with while one "master shader" handles it all. I don't have to duplicate any code or compile multiple shaders. Arguably, I could always have the shader program for each material be embedded in the material itself, and be auto-generated upon loading the material from the .mtl file. But this still leads to constantly calling glUseProgram, much more than is probably necessary in order to properly render the .obj. There seem to be a number of differing opinions on if it's okay to use hundreds of shaders or if it's best to just use tens of shaders.
      So, ultimately, what is the "right" way to do this? Does using a "master shader" (or a few variants of one) bog down the system compared to using hundreds of shader programs each dedicated to their own corresponding materials? Keeping in mind that the "master shaders" would have to track these additional uniforms and potentially have numerous branches of ifs, it may be possible that the ifs will lead to additional and unnecessary processing. But would that more expensive than constantly calling glUseProgram to switch shaders, or storing the shaders to begin with?
      With all these angles to consider, it's difficult to come to a conclusion. Both possible methods work, and both seem rather convenient for their own reasons, but which is the most performant? Please help this beginner/dummy understand. Thank you!
    • By JJCDeveloper
      I want to make professional java 3d game with server program and database,packet handling for multiplayer and client-server communicating,maps rendering,models,and stuffs Which aspect of java can I learn and where can I learn java Lwjgl OpenGL rendering Like minecraft and world of tanks
    • By AyeRonTarpas
      A friend of mine and I are making a 2D game engine as a learning experience and to hopefully build upon the experience in the long run.

      -What I'm using:
          C++;. Since im learning this language while in college and its one of the popular language to make games with why not.     Visual Studios; Im using a windows so yea.     SDL or GLFW; was thinking about SDL since i do some research on it where it is catching my interest but i hear SDL is a huge package compared to GLFW, so i may do GLFW to start with as learning since i may get overwhelmed with SDL.  
      -Questions
      Knowing what we want in the engine what should our main focus be in terms of learning. File managements, with headers, functions ect. How can i properly manage files with out confusing myself and my friend when sharing code. Alternative to Visual studios: My friend has a mac and cant properly use Vis studios, is there another alternative to it?  
  • Popular Now