Jump to content
  • Advertisement
Sign in to follow this  
daviddoria

OpenGL Simple Picking

This topic is 3606 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

I've seen code (namely: http://jerome.jouvie.free.fr/OpenGl/Tutorials/Tutorial27.php) that has zillions (ok, 50) lines for picking objects. The main part seems to be saving the projection matrix, setting the pick matrix to a very small window, and then resetting the projection matrix. If I have a very simply scene - maybe 10 objects - this all seems unnecessary. I thought I could just pick with the same view that I am displaying on the screen. I tried to do a very much simpler version:

void Pick(GLdouble x, GLdouble y)
{
   GLuint buffer[1024];
   const int bufferSize = sizeof(buffer)/sizeof(GLuint);

   GLint hits;
   
   GLint  min  = -1;
   GLuint minZ = -1;

   glSelectBuffer(bufferSize,buffer); 
   glRenderMode(GL_SELECT);           
   glInitNames();                     
	display();
   hits = glRenderMode(GL_RENDER);    

   /* Determine the nearest hit */

int i=0, j=0;
   if (hits)
   {
      for (i=0, j=0; i<hits; i++)
      {
         if (buffer[j+1]<minZ)
         {
            /* If name stack is empty, return -1                */
            /* If name stack is not empty, return top-most name */

            if (buffer[j]==0)
               min = -1;
            else
               min  = buffer[j+2+buffer[j]];

            minZ = buffer[j+1];
         }

         j += buffer[j] + 3;
      }
   }

cout << "Name: " << min << endl;

}
but it doesn't work - the picked values are all wrong. Is there any reason this wouldn't work? Dave

Share this post


Link to post
Share on other sites
Advertisement
Setting up the scene is just as relevant as processing the hits, so post that code also. And in what way does your present code not work? You should tell us what's wrong with it also. "Wrong values" is not a description of the problem.

Share this post


Link to post
Share on other sites
Here are the relevant functions: I don't know how else to describe the "wrong values" other than when I click a surface that I expect to be 1, it is not 1. Sometimes clicking no surface at all returns a hit when it clearly should not. (is there not a "code tag" on this forum?)

void display()
{
glClear( GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT );
glEnable(GL_DEPTH_TEST);
DrawCube();

glutSwapBuffers();
}

void DrawCube()
{
glPushName(1);

glLoadName(1);
glColor3f(1.0f, 0.0f, 0.0f); // Color Red
polygon(0,3,2,1);

glLoadName(2);
glColor3f(0.0f,1.0f,0.0f); // Color Green
polygon(2,3,7,6);

glLoadName(3);
glColor3f(0.0f, 0.0f, 1.0f); // Color Blue
polygon(0,4,7,3);

glLoadName(4);
glColor3f(1.0f,1.0f,0.0f); // Color Yellow
polygon(1,2,6,5);

glLoadName(5);
glColor3f(0.0f,1.0f,1.0f); // Color Cyan
polygon(4,5,6,7);

glLoadName(6);
glColor3f(1.0f,0.0f,1.0f); // Color Magenta
polygon(0,1,5,4);

}



GLfloat vertices[][3] = {{-1.0,-1.0,-1.0},{1.0,-1.0,-1.0},
{1.0,1.0,-1.0}, {-1.0,1.0,-1.0}, {-1.0,-1.0,1.0},
{1.0,-1.0,1.0}, {1.0,1.0,1.0}, {-1.0,1.0,1.0}};


void polygon(int a, int b, int c , int d)
{
glBegin(GL_QUADS);
glVertex3fv(vertices[a]);
glVertex3fv(vertices);
glVertex3fv(vertices[c]);
glVertex3fv(vertices[d]);
glEnd();
}

Share this post


Link to post
Share on other sites
You're not setting the pick region anywhere, so the whole original viewport is the pick region at the moment. That means anything you see on the screen when rendering normally will record a hit. You can easily realize something is wrong with the pick region as the X and Y parameters (which I assume is the desired pick location) are never used. The tutorial you linked mentions the pick region.

When describing the problem, you have to provide as much details as you can; relevant or not. So you expect 1 and don't get 1... but what do you get? You get zero hits? You get a single hit with another hit than you expect? You get a hit with a number that you don't even use? You get a multiple hits when you expect a single hit? You get totally bogus values which doesn't even form a valid hit record?

All these questions can be described as you described the problem, but all of them provides other information that narrows the problem further, and all of them indicates different problems possibly with different solutions. You have to be aware that all we can use to help you is what you give us.

Share this post


Link to post
Share on other sites
so with gluUnProject, I just provide the window coordinate (i dont understand why it wants x, y, and Z?? instead of just x and y), the current projection matrix, the current modelview matrix, and the region that I want to select (a viewport?)

ie. if I want to see which object is at window coords 50,60 I would pass as the viewport parameter

glViewport(50, 60, 3, 3)

Thoughts?
Dave

Share this post


Link to post
Share on other sites
I would suggest you to look into color picking, which seems to be the contemporary method of opengl picking.
Basically you set up a FrameBufferObject for offscreen rendering, assign a picking id to each object and render the objects into the offscreen buffer using the picking id as color.
After the rendering you may read the buffer via glReadPixels at the position of the mouse cursor perform a lookup in a hashtable to retrieve the actual object, that has been picked.
The downside is you may not retrieve all objects in a position, only the topmost one, which should be the object nearest to the camera. But thats maybe what you want =)

I have done this and it works really well.

Good luck,
Frederick

Share this post


Link to post
Share on other sites
Quote:
Original post by daviddoria
so with gluUnProject, I just provide the window coordinate (i dont understand why it wants x, y, and Z?? instead of just x and y), the current projection matrix, the current modelview matrix, and the region that I want to select (a viewport?)

ie. if I want to see which object is at window coords 50,60 I would pass as the viewport parameter

glViewport(50, 60, 3, 3)
Nope. You render the scene to the depth buffer, and then feed gluUnproject() the x and y of the mouse, and the z from the depth-buffer under the mouse (use glReadPixels). You also feed it the current modelview and projection matrices, and the current viewport.

The huge advantage of this method is that rather than obtaining the object under the mouse, you will instead obtain the exact x, y, z point in the 3d scene under the mouse. You can compare this point with your objects to find the selected object, or you can use the exact position for texture painting, etc.

Also, if you pick an object using this method, and then move the mouse and pick again, using the exact same depth value, you will obtain the correct result of dragging the selected object (i.e. parallel to the screen, for any projection and transformation).

Share this post


Link to post
Share on other sites
hmmm so it seems gluUnProject is not really a replacement for the selection buffer because it gives back a coordinate in 3D space, not an object ID, which is what I am looking for in this case. I was reading that you have to ensure the monitor is in "truecolor" mode for color picking to work - is that really a problem?

Share this post


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

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!