• Advertisement
Sign in to follow this  

OpenGL DualMonitors ?

This topic is 3133 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Just wondering how you would add support for dualmonitor display with opengl. I don't have a second monitor, so I cant try it, just would like to find some resources to get started and then test it somewhere else. I have googled quite a bit, but couldn't find anything. could it be that you just size the window-width to the double size of the screen ? Or do you have to use multiple windows and move the second window to the center of both monitors ? Question goes for Win32, Linux, MacOsX.

Share this post


Link to post
Share on other sites
Advertisement
It is a very platform specific topic, I am afraid, although some high-end windowing toolkits provide support for it. Look around for windowing solutions which also target Virtual Reality applications, and you should have some luck.

Share this post


Link to post
Share on other sites
I know its a platform specific topic, thats why I asked for win32, linux and macosx.
and another toolkit is no solution for me.

Share this post


Link to post
Share on other sites
Create one OpenGL window/context/whatever for each monitor =P It's as simple as that, although it can lead to headaches if you have to adapt code that was originally made for a single monitor (normally it's just a matter of setting what context to render next, but you never know what stupid quirk the code may have...).

Share this post


Link to post
Share on other sites
You might run into a problem too...

In all the dual monitor setups I've seen, only one monitor had hardware accelerated graphics.

IE if you had a windowed game running, you'd get a lot higher FPS on one monitor vs the other.

Just somethin to be aware of!

Share this post


Link to post
Share on other sites
It also depends how the user has configured their dual monitors.

Most often it's set up as "dual view", where they are two independent displays. However, the user may have configured them to act as a single (Large) monitor with a weird resolution, in which case you just have to support this large-resolution and know where the split occurs.
I've worked on a system that used this mode in the past, and found that only one half of the large virtual-screen (i.e. one physical screen) would use quality-enhancements such as AA or Aniso-filtering...

To get around the "only one monitor is HW accelerated" problem mentioned above, you can render the slow screen's content to a texture using the accelerated context. The slow context then just has to blit this texture to the screen.

Share this post


Link to post
Share on other sites
All dual monitor setups I've seen so far (and including mine) had a) hardware acceleration for all screens and b) consisted of a single desktop area that was not rectangular (eg. 1600x1200 with the right border leading into a 1920x1080 screen). Does anyone really use it as mirrored or separate screens?

Supreme Commander supports this nicely, you have two fully functional game screens, usually I leave the left one zoomed out to act as an overhead map and use the right one to play. Or zoom the left one to my army and the right one to the place I want to arrange them at, so I don't need to scroll to select the different units.

It's a D3D game, though. In Direct3D, a dual-head graphics card with two monitors attached simply appears as two Direct3D devices with different supported resolutions. I guess it's similar in OpenGL, you'd just create two windows and two contexts.

The only problem is if you move a 3D rendering window between the two screens. The application needs to detect this and recreate another D3D device / OGL context for the other screen. And if the window is placed in the middle between two screens, you either have to do a slow memory copy (that's what XNA does) or keep two devices/contexts around.

Share this post


Link to post
Share on other sites
Quote:
Original post by Cygon
All dual monitor setups I've seen so far (and including mine) had a) hardware acceleration for all screens and b) consisted of a single desktop area that was not rectangular (eg. 1600x1200 with the right border leading into a 1920x1080 screen). Does anyone really use it as mirrored or separate screens?
What you just described is two separate screens. The "single virtual screen" setting would show up as a single device, e.g. 3200x1200.
Also, in the case I mentioned, both screens were accelerated, but one still took shortcuts (ignoring quality hints/preferences).

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By LifeArtist
      Good Evening,
      I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
      First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
      I am really stucked right now because of the fundamental question:
      Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
      If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on. 
      In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
      Should I treat those debug objects as entities/components?
      For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
      Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
      Regards,
      LifeArtist
    • By QQemka
      Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
      Let's go:
      Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
      Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
      Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
      What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
      There were several more but i forgot/solved them at time of writing
      Thanks in advance
    • By RenanRR
      Hi All,
      I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
      I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
      Vertex Shader:
      #version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
      ..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);  
      So, some doubts:
      - Why use it like that?
      - Is it okay to manipulate the camera that way?
      -in this way, are not the vertex's positions that changes instead of the camera?
      - I need to pass MVP to all shaders of object in my scenes ?
       
      What it seems, is that the camera stands still and the scenery that changes...
      it's right?
       
       
      Thank you
       
    • By dpadam450
      Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

      int rgbValue = int(textureSample.w);//4 bytes of data packed as color
      // algorithm might not be correct and endianness might need switching.
      vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
      extractedData /= 255.0f;
    • By Devashish Khandelwal
      While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
      Anyone has any idea .. what should I do?
  • Advertisement