Sign in to follow this  
Vekta

OpenGL What exactly is an "OpenGL Context"? How does it work?

Recommended Posts

Vekta    104
Hello, im in the process of attempting to teach myself OpenGL programming but so far all i've managed to do is become extremely confused. I have a few questions, they are probably pretty silly and i apologize but still, any help would be appreciated!

From my experiments and what i've read before using any OpenGL function calls and such an "OpenGL context" is required. Im a bit puzzled as to what this actually means, my initial thought was that this would just be a window capable of displaying pixel data, but clearly there is something more to it.

What actually defines a window as being an OpenGL context?
How does OpenGL know if a window is a valid OpenGL context?

Lets say on operating system X i've used the native API to create a window, what steps would i then need to take to make it capable of displaying openGL data, do native api's include special openGL settings or something?

Currently im using SFML to abstract the creation of an OpenGL context and it works perfectly but i'd still like to have a at least vague idea of the inner working that are going on...

For example SFML 1.6 does not work with OpenGL 3.0+ whereas SFML 2.0 does, i don't understand this, why is displaying the pixels rendered by OpenGL so complicated that compatibility becomes an issue?

Thank you for any help, and im sorry that my writing is not very good!

Share this post


Link to post
Share on other sites
dpadam450    2357
Your GPU draws stuff. Windows owns part of that, your game owns part of that, and your applications such as web browsers own stuff. Say you call glClear() to clear your current drawing frame. It does not clear windows desktop and other stuff. So each time you open a GL application, it needs its own stack of states. Say you call glColor3f(1,1,1) in one instance of your game and then open a 2nd copy of your game calling glColor3f(0,0,0) in the other. There are two contexts and two glColors being tracked separately.

Share this post


Link to post
Share on other sites
V-man    813
Unless you plan on become a programmer in a team that makes GL drivers and you want to work at nVidia, it doesn't matter what a GL context is.

You just need to 1. setup a pixelformat 2. make a GL context 3. make the GL context current.
SFML, GLUT, freeGLUT, QT, SDL and the many others do that for you.

and render away until you need to destroy resources and destroy the GL context and close the window.

Share this post


Link to post
Share on other sites
EternityZA    1226
[quote name='V-man' timestamp='1307489840' post='4820735']<BR>Unless you plan on become a programmer in a team that makes GL drivers and you want to work at nVidia, it doesn't matter what a GL context is.<BR>[/quote]Quite right. ATI driver developers dont need to know what a opengl context is among other things.

Share this post


Link to post
Share on other sites
Tachikoma    575
The OpenGL graphics driver has a resource management system, called the OpenGL context. You can think of it as a sandbox for your application to use; where your program stores textures, buffers, meshes, etc. Therefore, each application utilising OpenGL will communicate with the driver and requests their own context, so that the resources are not mixed up between applications. Sometimes you can allocate more than one contexts per application.

Anyway, when a context is created, it is tied to your application's process, usually to the main Window's paint area. Often creating Window paint surface and creating an OpenGL context goes hand in hand. Therefore, destroying the Window may also destroy the context.

1. Create window
2. Create OpenGL context
3. Attach context to window and current process
4. Switch to created context

5. Render stuff

6. Release context
7. Destroy window

This is the general process for setting up OpenGL on most systems. I'm not familiar with X specifically, but I assume the steps would be quite similar.

Share this post


Link to post
Share on other sites
Aks9    1499
[left][left][size="3"][size="2"][i]If you can define something then you don’t understand it![/i][/size][/size][/left][/left]
[left][left] [/left][/left]
[left][left][size="3"][size="2"]Sadly, nobody before Tachikoma tried to answer to the question. Although it is not crucial for programmers to know how rendering context is implemented, it is important to understand what it is in order to know how to use it.[/size][/size][/left][/left]
[left][left] [/left][/left]
[left][left][size="3"][size="2"]An OpenGL [/size][i][size="2"]context[/size][i] [/i][/i][size="2"]is the data structure that collects all states needed by server to render an image. It contains references to buffers, textures, shaders, etc. OpenGL API doesn’t define how rendering context is defined, it is up to the native window system; but none of OpenGL commands can be executed until rendering context is created and made current.[/size][/size][/left][/left]
[left][left] [/left][/left]
[left][left][size="3"][size="2"]A rendering context should be compatible with a window it will render to. There can be several contexts per application, or even per window. On the other hand, the same context can be used for rendering in multiple windows, but in that case all windows using the same context must have the same pixel format. Now we have come to another important aspect of rendering context: its rendering surface must be adequate for appropriate window. In order to achieve that we have to choose and set appropriate pixel format of the window that have to be created. The rendering surface is the surface to which primitives are drawn. It defines types of buffers that are required for rendering such as a color buffer, depth buffer, and stencil buffer.[/size][/size][/left][/left]
[left][left] [/left][/left]
[left][left][size="3"][size="2"]Choosing pixel format must be performed in order to verify support for defined pixel format. The system would return ID of appropriate pixel format, or the closest match. Setting pixel format that is not previously returned from the system would almost certainly fail. It is not recommended to set pixel format for the window more than once.[/size][/size] [/left][/left]
[left][left] [/left][/left]
[left][left][size="3"][size="2"]In order to issue any OpenGL command we have to make OpenGL context active (i.e. “current”). By making active we assume binding OpenGL context to a window’s DC. It is done from a certain thread. Only one context can be made current for a single thread at a moment. Calling OpenGL commands from another thread (different from that made the context current) fails. If we want to make use of multithreading update of OpenGL resources, we have to make a share-group. All contexts from the share-group share resources like textures, buffers, etc. Although multithreading update can be useful in some cases, we have to be aware that most OpenGL drivers serialize access to the GPU. OpenGL guarantees that all commands in the single context will be executed in the order in which they are issued, but there is no guarantee for multiple contexts. Since OpenGL 3.2 synchronization is enabled through sync objects.[/size][/size] [/left][/left]
[left][left] [/left][/left]
[left][left][size="3"][size="2"]Prior to OpenGL 3.0, there was just one type of OpenGL rendering contexts; the context that contains full functionality. OpenGL3.0 introduced forward compatibility, and 3.2 introduced concept of profiles. If anyone is interested in further discussion, we could proceed, but I think it is a bit out of the scope of the OP’s question. I was already too comprehensive. [/size][/size] :rolleyes:[/left][/left]

Share this post


Link to post
Share on other sites
swilkewitz    128
This isn't a direct answer to your question, but I would recommend the NeHe tutorial for learning openGL. It will take you through creating a Window, setting up openGL, drawing on the Window, and much more.

[url="http://nehe.gamedev.net/lesson.asp?index=01"]http://nehe.gamedev.net/lesson.asp?index=01[/url]

Share this post


Link to post
Share on other sites
bluntman    255
[quote name='swilkewitz' timestamp='1307676925' post='4821581']
This isn't a direct answer to your question, but I would recommend the NeHe tutorial for learning openGL. It will take you through creating a Window, setting up openGL, drawing on the Window, and much more.

[url="http://nehe.gamedev.net/lesson.asp?index=01"]http://nehe.gamedev....on.asp?index=01[/url]
[/quote]

Just remember that following a tutorial is no substitute for reading the documentation. A tutorial shows you how to use a hammer to drive in a nail. If someone then gives you a screw you will think to yourself "this looks a lot like a nail, better use a hammer!". Read the documentation on nails, screws and hammers is all I'm saying :D

Share this post


Link to post
Share on other sites
V-man    813
For your review, I just added this section to the Wiki FAQ
http://www.opengl.org/wiki/FAQ#GL_context

I am keeping it short. I did not go into the actual calls needed since these are OS specific and you can get that info from other parts of the web.

You can give feedback. Modify the Wiki to your liking, etc.

Share this post


Link to post
Share on other sites
Aks9    1499
No offense V-man, but you didn't write about any important aspect of the rendering context except that we need it in order to execute any GL code. You didn't even answer on your own question (why do we need a window?). Anyway it is good that beginners can read something, although I don't think they really read wiki. It is easier to ask a question on the forum. :)

Share this post


Link to post
Share on other sites
V-man    813
You need a window because that is how it is designed. It is as simple as that. I have made a slight modification to that section.
You can of course modify it or make suggestions right here if you want things worded differently.

[quote]Anyway it is good that beginners can read something, although I don't think they really read wiki.[/quote]
You can say that about any other webpage.
The Wiki is not for stopping people from asking questions.

Before the Wiki was around, people asked questions and received many nice answers and that followed by "Why isn't this documented somewhere?". At some point, whoever manages opengl.org decided that a Wiki would be a good idea.

Share this post


Link to post
Share on other sites
Aks9    1499
[quote name='V-man' timestamp='1307720994' post='4821743'] You need a window because that is how it is designed. It is as simple as that.[/quote]

No comment. (Or to be more precise, I've already commented such answers)


[quote name='V-man' timestamp='1307720994' post='4821743'] You can of course modify it or make suggestions right here if you want things worded differently. [/quote]

I don't like writing wikis, because they are so impersonal. Although I have to admit that Wikipedia is really great.


Concerning OpenGL rendering context (RC), I think I've said what I have to say. The most important aspects are: what it is, how it can be created, what the scope of RC is, how resources can be shared, profiles and forward compatibility. But since OP hasn't reacted on our posts, we are probably uselessly fiddling. :D

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 Arulbabu Donbosco
      There are studios selling applications which is just copying any 3Dgraphic content and regenerating into another new window. especially for CAVE Virtual reality experience. so that the user opens REvite or CAD or any other 3D applications and opens a model. then when the user selects the rendered window the VR application copies the 3D model information from the OpenGL window. 
      I got the clue that the VR application replaces the windows opengl32.dll file. how this is possible ... how can we copy the 3d content from the current OpenGL window.
      anyone, please help me .. how to go further... to create an application like VR CAVE. 
       
      Thanks
    • By cebugdev
      hi all,

      i am trying to build an OpenGL 2D GUI system, (yeah yeah, i know i should not be re inventing the wheel, but this is for educational and some other purpose only),
      i have built GUI system before using 2D systems such as that of HTML/JS canvas, but in 2D system, i can directly match a mouse coordinates to the actual graphic coordinates with additional computation for screen size/ratio/scale ofcourse.
      now i want to port it to OpenGL, i know that to render a 2D object in OpenGL we specify coordiantes in Clip space or use the orthographic projection, now heres what i need help about.
      1. what is the right way of rendering the GUI? is it thru drawing in clip space or switching to ortho projection?
      2. from screen coordinates (top left is 0,0 nd bottom right is width height), how can i map the mouse coordinates to OpenGL 2D so that mouse events such as button click works? In consideration ofcourse to the current screen/size dimension.
      3. when let say if the screen size/dimension is different, how to handle this? in my previous javascript 2D engine using canvas, i just have my working coordinates and then just perform the bitblk or copying my working canvas to screen canvas and scale the mouse coordinates from there, in OpenGL how to work on a multiple screen sizes (more like an OpenGL ES question).
      lastly, if you guys know any books, resources, links or tutorials that handle or discuss this, i found one with marekknows opengl game engine website but its not free,
      Just let me know. Did not have any luck finding resource in google for writing our own OpenGL GUI framework.
      IF there are no any available online, just let me know, what things do i need to look into for OpenGL and i will study them one by one to make it work.
      thank you, and looking forward to positive replies.
    • By fllwr0491
      I have a few beginner questions about tesselation that I really have no clue.
      The opengl wiki doesn't seem to talk anything about the details.
       
      What is the relationship between TCS layout out and TES layout in?
      How does the tesselator know how control points are organized?
          e.g. If TES input requests triangles, but TCS can output N vertices.
             What happens in this case?
      In this article,
      http://www.informit.com/articles/article.aspx?p=2120983
      the isoline example TCS out=4, but TES in=isoline.
      And gl_TessCoord is only a single one.
      So which ones are the control points?
      How are tesselator building primitives?
    • By Orella
      I've been developing a 2D Engine using SFML + ImGui.
      Here you can see an image
      The editor is rendered using ImGui and the scene window is a sf::RenderTexture where I draw the GameObjects and then is converted to ImGui::Image to render it in the editor.
      Now I need to create a 3D Engine during this year in my Bachelor Degree but using SDL2 + ImGui and I want to recreate what I did with the 2D Engine. 
      I've managed to render the editor like I did in the 2D Engine using this example that comes with ImGui. 
      3D Editor preview
      But I don't know how to create an equivalent of sf::RenderTexture in SDL2, so I can draw the 3D scene there and convert it to ImGui::Image to show it in the editor.
      If you can provide code will be better. And if you want me to provide any specific code tell me.
      Thanks!
    • By Picpenguin
      Hi
      I'm new to learning OpenGL and still learning C. I'm using SDL2, glew, OpenGL 3.3, linmath and stb_image.
      I started following through learnopengl.com and got through it until I had to load models. The problem is, it uses Assimp for loading models. Assimp is C++ and uses things I don't want in my program (boost for example) and C support doesn't seem that good.
      Things like glVertexAttribPointer and shaders are still confusing to me, but I have to start somewhere right?
      I can't seem to find any good loading/rendering tutorials or source code that is simple to use and easy to understand.
      I have tried this for over a week by myself, searching for solutions but so far no luck. With tinyobjloader-c and project that uses it, FantasyGolfSimulator, I was able to actually load the model with plain color (always the same color no matter what I do) on screen and move it around, but cannot figure out how to use textures or use its multiple textures with it.
      I don't ask much: I just want to load models with textures in them, maybe have lights affect them (directional spotlight etc). Also, some models have multiple parts and multiple textures in them, how can I handle those?
      Are there solutions anywhere?
      Thank you for your time. Sorry if this is a bit confusing, English isn't my native language
  • Popular Now