Sign in to follow this  

OpenGL How to tell OpenGL to ignore what's under cursor?

Recommended Posts


In my editor im drawing selectionboxes with OpenGL, they are drawn using glDrawArrays from pre calculated vertex coords.
From const array.
The box(boxes) are textured from texture loaded from file (PNG) and processed with SDL to make texture for OpenGL out of it.

The drawing and stuff works fine but there is very annoying problem (bug) for me that is really really ugly for me.

Look at the GIF.


As you see, first there are just white rectangles on red/black texture and if mouse cursor hit's the WHITE border of selection boxes, then boxes jump around (up and down).

Is it possible to tell OpenGL to ignore the selection boxes texture or the WHITE BORDER "width" in pixels or something like that?
To finally stop this jumping once and for all?

glReadPixels maybe could help, but if the textures have the same color? It will jump again?

I must tell you that it always should ignore selection boxes, but if there is anything else under the mouse cursor it shouldn't ignore it and then it is allowed to jump around.

It just must ignore the white selection boxes. That's all.

Any help, ideas, tips or hints are very very welcome.

Share this post

Link to post
Share on other sites
Um.... I don't understand the problem. It seems to me that the problem has nothing to do with openGL and rendering, but the logic.

Maybe you could show the whole code or you should explain what you want to achieve (the final goal, not the logic to achieve it).

Share this post

Link to post
Share on other sites
[b] szecs[/b]

Well, look at this gif then.


There is a mouse dragging and red selection rectangles. In this gif you see that if mouse cursor goes over the red lines, then the selection boxes are not going up like in my first gif. They go up only if there is something else under cursor (not selection boxes itself), in this case there is a little box at the right, as you see.

In first GIF, when the mouse cursor goes over the white line, the boxes will "jump up".
But they shouldn't, it must ignore the white lines as the second GIF shows, the red lines are ignored under mouse cursor.

Basically it same as telling: [b]selection shouldn't select itself![/b]

[quote name='szecs' timestamp='1313760631' post='4851195']
Um.... I don't understand the problem. It seems to me that the problem has nothing to do with openGL and rendering, but the logic.

Maybe you could show the whole code or you should explain what you want to achieve (the final goal, not the logic to achieve it).

Share this post

Link to post
Share on other sites
[quote name='Tachikoma' timestamp='1313761325' post='4851198']
How are you actually testing for selection anyway? I mean if you test the point against a rect, you are either inside, or outside, that's it. Edge cases are special and generally require extra checking.

Basically im not, most of the work is done by OpenGL with gluUnProject.
And im drawing the boxes at the coordinates, which gluUnProject returned me.

Same code as here:

I think that's the glReadPixels that finds the textures. Because i think that if there is empty "world" and i click in this world, it reads: 0,0,0.
So there is nothing under cursor.

In my case it finds anything that's not 0,0,0 and his friend gluUnproject tells me the coordinates where there is something under cursor.
And also it finds the selection boxes texture and that could be reason for jumping around.

Share this post

Link to post
Share on other sites
[s]The images only show the symptom. You still haven't explained [b]how[/b] your algorithm works.

Are you testing cursor intersection against a geometric object? Are you testing against rendered objects in a buffer?
edit: Never mind, just read your second response.

I think you should cast a ray through the cursor and explicitly test boxes intersecting against it. So instead of using buffers to perform the test, you are doing it in the geometric domain.

Share this post

Link to post
Share on other sites
I also have a bit difficulty understanding the problem; but perhaps it's because the solutions is too easy... because if
[quote name='BytePtr' timestamp='1313761607' post='4851199']
Basically it same as telling: [b]selection shouldn't select itself![/b]
then the solution is to not draw the selection geometry when selecting. Selection is only performed on what you draw when selection is enabled, so if you don't want the selection to select itself, then you don't draw the selection.

Share this post

Link to post
Share on other sites
AFAICT, the linked NeHe code uses the depth value to perform the reverse projection, so you could try disabling depth write via [b]glDepthMask(GL_FALSE)[/b] when you draw the selection box so that the box wireframes don't pollute the depth buffer.

Share this post

Link to post
Share on other sites
[quote name='JTippetts' timestamp='1313762668' post='4851208']
AFAICT, the linked NeHe code uses the depth value to perform the reverse projection, so you could try disabling depth write via [b]glDepthMask(GL_FALSE)[/b] when you draw the selection box so that the box wireframes don't pollute the depth buffer.

Wow, this is excellent. It really works.

Basically i did this:


Looks so smooth and much nicer now.
Can you explain a bit more why it helps and works?
Or could post some link where i could read about it? I want to learn also from it.

Thanks alot for you and the others here who replied.

You guys got your +

Share this post

Link to post
Share on other sites
The [url=""]Z-buffer[/url] is used by the renderer to determine which fragments to keep and which to discard, based on their Z-depth, or distance from the camera. A side-effect of this is that when rendering is done, the Z-buffer contains a depth "map" of the scene. Since any given point on-screen reverse-projects to a line-segment in world space bounded by the near and far planes, the only way to determine the exact point in world space that a screen point reverse-projects to is to read the Z-depth from the buffer and use that as the Z component of the coordinate to reverse-project. This is what the NeHe example is doing by calling [b]glReadPixels[/b] to assign the value of [b]winZ[/b].

Now, when you draw your selection boxes with depth-writing enabled, then the Z value in the depth buffer that is used to reverse-project with will be equal to the depth of the wireframe of the selection box at that location, rather than the depth of the level geometry behind it that you are trying to select. This apparently fools whatever code you use to calculate the selection boxes into thinking the level geometry depth is higher than it really is. In effect, the algorithm doesn't discriminate between the "real" stuff (level geometry) and the "fake" stuff (the selection box). By disabling depth-write when you draw the selection boxes, you are making those boxes a visual effect only; they have no presence in the depth buffer, and thus don't over-write the depth values from the level geometry. In effect, they now "don't count" for the purposes of reverse-projecting.

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  

  • Announcements

  • Forum Statistics

    • Total Topics
    • Total Posts
  • Similar Content

    • By test opty
      Hi all,
      I'm starting OpenGL using a tut on the Web. But at this point I would like to know the primitives needed for creating a window using OpenGL. So on Windows and using MS VS 2017, what is the simplest code required to render a window with the title of "First Rectangle", please?
    • By DejayHextrix
      Hi, New here. 
      I need some help. My fiance and I like to play this mobile game online that goes by real time. Her and I are always working but when we have free time we like to play this game. We don't always got time throughout the day to Queue Buildings, troops, Upgrades....etc.... 
      I was told to look into DLL Injection and OpenGL/DirectX Hooking. Is this true? Is this what I need to learn? 
      How do I read the Android files, or modify the files, or get the in-game tags/variables for the game I want? 
      Any assistance on this would be most appreciated. I been everywhere and seems no one knows or is to lazy to help me out. It would be nice to have assistance for once. I don't know what I need to learn. 
      So links of topics I need to learn within the comment section would be SOOOOO.....Helpful. Anything to just get me started. 
      Dejay Hextrix 
    • By mellinoe
      Hi all,
      First time poster here, although I've been reading posts here for quite a while. This place has been invaluable for learning graphics programming -- thanks for a great resource!
      Right now, I'm working on a graphics abstraction layer for .NET which supports D3D11, Vulkan, and OpenGL at the moment. I have implemented most of my planned features already, and things are working well. Some remaining features that I am planning are Compute Shaders, and some flavor of read-write shader resources. At the moment, my shaders can just get simple read-only access to a uniform (or constant) buffer, a texture, or a sampler. Unfortunately, I'm having a tough time grasping the distinctions between all of the different kinds of read-write resources that are available. In D3D alone, there seem to be 5 or 6 different kinds of resources with similar but different characteristics. On top of that, I get the impression that some of them are more or less "obsoleted" by the newer kinds, and don't have much of a place in modern code. There seem to be a few pivots:
      The data source/destination (buffer or texture) Read-write or read-only Structured or unstructured (?) Ordered vs unordered (?) These are just my observations based on a lot of MSDN and OpenGL doc reading. For my library, I'm not interested in exposing every possibility to the user -- just trying to find a good "middle-ground" that can be represented cleanly across API's which is good enough for common scenarios.
      Can anyone give a sort of "overview" of the different options, and perhaps compare/contrast the concepts between Direct3D, OpenGL, and Vulkan? I'd also be very interested in hearing how other folks have abstracted these concepts in their libraries.
    • By aejt
      I recently started getting into graphics programming (2nd try, first try was many years ago) and I'm working on a 3d rendering engine which I hope to be able to make a 3D game with sooner or later. I have plenty of C++ experience, but not a lot when it comes to graphics, and while it's definitely going much better this time, I'm having trouble figuring out how assets are usually handled by engines.
      I'm not having trouble with handling the GPU resources, but more so with how the resources should be defined and used in the system (materials, models, etc).
      This is my plan now, I've implemented most of it except for the XML parts and factories and those are the ones I'm not sure of at all:
      I have these classes:
      For GPU resources:
      Geometry: holds and manages everything needed to render a geometry: VAO, VBO, EBO. Texture: holds and manages a texture which is loaded into the GPU. Shader: holds and manages a shader which is loaded into the GPU. For assets relying on GPU resources:
      Material: holds a shader resource, multiple texture resources, as well as uniform settings. Mesh: holds a geometry and a material. Model: holds multiple meshes, possibly in a tree structure to more easily support skinning later on? For handling GPU resources:
      ResourceCache<T>: T can be any resource loaded into the GPU. It owns these resources and only hands out handles to them on request (currently string identifiers are used when requesting handles, but all resources are stored in a vector and each handle only contains resource's index in that vector) Resource<T>: The handles given out from ResourceCache. The handles are reference counted and to get the underlying resource you simply deference like with pointers (*handle).  
      And my plan is to define everything into these XML documents to abstract away files:
      Resources.xml for ref-counted GPU resources (geometry, shaders, textures) Resources are assigned names/ids and resource files, and possibly some attributes (what vertex attributes does this geometry have? what vertex attributes does this shader expect? what uniforms does this shader use? and so on) Are reference counted using ResourceCache<T> Assets.xml for assets using the GPU resources (materials, meshes, models) Assets are not reference counted, but they hold handles to ref-counted resources. References the resources defined in Resources.xml by names/ids. The XMLs are loaded into some structure in memory which is then used for loading the resources/assets using factory classes:
      Factory classes for resources:
      For example, a texture factory could contain the texture definitions from the XML containing data about textures in the game, as well as a cache containing all loaded textures. This means it has mappings from each name/id to a file and when asked to load a texture with a name/id, it can look up its path and use a "BinaryLoader" to either load the file and create the resource directly, or asynchronously load the file's data into a queue which then can be read from later to create the resources synchronously in the GL context. These factories only return handles.
      Factory classes for assets:
      Much like for resources, these classes contain the definitions for the assets they can load. For example, with the definition the MaterialFactory will know which shader, textures and possibly uniform a certain material has, and with the help of TextureFactory and ShaderFactory, it can retrieve handles to the resources it needs (Shader + Textures), setup itself from XML data (uniform values), and return a created instance of requested material. These factories return actual instances, not handles (but the instances contain handles).
      Is this a good or commonly used approach? Is this going to bite me in the ass later on? Are there other more preferable approaches? Is this outside of the scope of a 3d renderer and should be on the engine side? I'd love to receive and kind of advice or suggestions!
    • By nedondev
      I 'm learning how to create game by using opengl with c/c++ coding, so here is my fist game. In video description also have game contain in Dropbox. May be I will make it better in future.
  • Popular Now