Sign in to follow this  
Vortez

OpenGL Nicer way to switch between windowed and fullscreen mode?

Recommended Posts

Vortez    2714

Hi, i have this program that i can switch from windowed mode to fullscreen and vice versa, but i don't really like the way it work.

 

For now, the only thing that work is to "shutdown" and reinitialize opengl, then reload textures, which introduce some lag when doing the switch.

Also, if i switch too fast (ie: pressing my switch mode key fast twice in a row), sometime the context failed to create so it's not very good.

 

The thing is, i've seen games like warcraft that can switch pretty fast, especially between fullscreen and a mix of fullscreen and windowed mode (how do you even do this???).

The ps2 emulator does this very nicely too when you double click on the main window.

 

Another thing that bug me is that, since im using delphi for this app, every time i change the window style from normal to a borderless fullscreen window, the window handle change, so i got a completely different window. This is not a serious problem though, since i could just use CreateWindowEx and do it myself if i really wanted to, although i dunno if i would be able to add a TScrollbox window component afterward, which is needed sometime when the image i draw is not stretched but drawn at normal size.

 

What am i doing wrong? I think someone shoud create a tutorial on that because it's a pretty common thing in games and program like mine, but the information on the subject is almost non existant...

 

Also, does DirectX handle this better?

Edited by Vortez

Share this post


Link to post
Share on other sites
_the_phantom_    11250
With OpenGL you don't, and never did on Windows, have to kill the window to resize/swap modes - using Win32 you can just resize the window, change the OpenGL viewport and carry on as before.

If your API kills the window, then yes, you are out of luck (SDL was dumb in this respect too), but you certainly don't have to destroy it to switch modes.

Share this post


Link to post
Share on other sites
Vortez    2714

I just found this thread and that seem to do the trick, except for the "fullscreen (windowed)" mixed mode like warcraft i was talking about. Guess ill have to figure that part out later.

 

It's soooo much better now cool.png

Edited by Vortez

Share this post


Link to post
Share on other sites
mhagain    13430

I believe that under older drivers (I'm talking 1990s here), killing the window and restarting was the only 100% reliable way, but nowadays - unless you need to change the pixel format - you shouldn't need to do that.

 

D3D9 and below handled it cleanly by just requiring a "Reset" of the device, but messily in that there were "lost devices" to deal with (although if you design your video code around this it wasn't such a big deal).  D3D10+ no longer have "lost devices" but the process potentially involves two mode switches (one to go fullscreen, one to set the resolution) and is really badly documented.

 

With D3D the API is more closely tied to the windowing system so it can make mode switching part of the API; with OpenGL the API is not tied to the windowing system but this disconnect means that OpenGL is at the mercy of the windowing system for switching; it does however allow OpenGL to be more cross-platform.  There are pros and cons to both.

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++.
      Question:
      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