Sign in to follow this  

OpenGL help: problem resizing GLX window

Recommended Posts

bootstrap    100
I just ported my 3D engine from OpenGL on Windows to OpenGL on Linux. But now that I have the core running, I have a couple problems I do not understand. Here is one of them. When I grab the boundary of the graphics window with the mouse and resize it to a larger size, the area inside the window that is cleared each frame does not change size from the original size. The rest of the area inside the frame is not cleared or drawn. The objects in the window get larger as the window is made larger and larger, so the viewport and the projection matrices are being altered correctly (it seems). Then when I resize the window smaller again, some of the window along the top is not being drawn - as if the viewport is offset downward (but not rightward). I do not understand in any significant way what the distinction between the XWindow and GLXWindow are. When my code creates a window, it first calls XCreateWindow() to create an XWindow, then calls glXCreateWindow() to create (and associate) a corresponding GLXWindow. That's what the GLX sample code that I found seems to want. Not sure whether perhaps the XWindow is being resized but not the GLXWindow - but I do not see any GLX resize functions. Furthermore, when I try to resize the GLXWindow with xlib functions, my applications blows up (and XWindows prints a nasty error message). So that doesn't seem to be how this should be handled. Any ideas? video card = nvidia 8600GT + 512MB. The nvidia drivers are up to date.

Share this post

Link to post
Share on other sites
zedz    291
sorry no idea, if u used SDL u wouldnt have this problem ( sorry not helpful ), though what u can do is check out the source code of SDL included with the development download + see how it handles window resizing

Share this post

Link to post
Share on other sites
Fiddler    860
What I do in OpenTK is this:
- glXChooseVisual
- XCreateColormap (from the visual above)
- XCreateWindow (make sure you request to be informed about size/move events)
- glXCreateContext
- glXMakeCurrent

Works perfectly, as long as you call glViewport inside the resize event handler.

I don't know what glXCreateWindow does, and I've never seen it used either. :)

Check the glxgears source code (scroll to the end of the file, and check main() and make_window()). You can also take a look at the source of GLFW (zlib licensed, check lib/x11/x11_window.c) and the source of SDL (LGPL licensed, careful!)

Share this post

Link to post
Share on other sites
bootstrap    100
Thanks for the information, fiddler.

I had the same problem with the GLX 1.2 functions you list in your message. After having so much trouble finding the cause of this problem, I decided to switch to the newer GLX 1.3 functions out of desparation!

I did finally solve the problem. To my surprise, the bug was in XWindows, not my code! I did not expect that!

Specifically, the problem was caused (by coincidence - or pure bad luck) by my decision to capture the width and height of the resized window in the XWindows ResizeRequest event. I found that the mere fact of selecting to receive that event (when calling the XCreateWindow() function) was sufficient to cause this problem. No kidding!

I moved my code that captures the resized width and height of the window into the ConfigureNotify event, and simply returned from function when the event was a ResizeRequest --- but the problem persisted, even though my code was doing nothing whatsoever in response to the ResizeRequest event. However, if I simply cleared the bit in the "event_mask" in the XSetWindowAttributes structure argument to XCreateWindow() --- poof --- problem gone. Yikes!

I bet you a dime if you simply set this one bit into your code that you encounter the identical problem --- even though you do not handle the event!

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