Sign in to follow this  
Flawe

OpenGL 2D pixel collision detection

Recommended Posts

Flawe    114
so I'm trying to play around with some small game thingy in OpenGL in 2D and I was wondering how can one do pixel-sensitive collision detection? I was thinking of having two layers, one for the background of the scene and one for the foreground with the objects that should collide. What's the best way of doing this? Is it by having multiple quads with a texture each or is it multi-texturing? Can you still do pixel-collision if you use multi-textures? Thanx

Share this post


Link to post
Share on other sites
MARS_999    1627
I guess I am lost by what do you mean by pixel collision? If you mean that you want a object e.g. ship to collide with a wall? If so use a 2D array that holds all the objects locations and then you just test the current object's location to see if it hit with the other objects locations. But like I said I am unsure if thats what you are asking. HTH

Share this post


Link to post
Share on other sites
Flawe    114
Well I'm using sprites so I'd like to test the pixels and not the bounding box/sphere. The alpha part of the texture should not be consider when doing the detection.

Share this post


Link to post
Share on other sites
Flawe    114
I guess that's one way of doing it. Won't it be hard to keep track of the bounding boxes if I have complex animations which need that bounding boxes to move around a lot?

What other options do I have? Haven't done this sort of thing before so I'm greatfully for any ideas.

Share this post


Link to post
Share on other sites
Kada2k6    108
Hidden
Quote:
Original post by Flawe
Well I'm using sprites so I'd like to test the pixels and not the bounding box/sphere. The alpha part of the texture should not be consider when doing the detection.

In my humble opinion, this is a bit overkill. Not many classic 2D games have this type of collision detection which is done by looking at pixels, but if you insist then I think you must do this:

First, do the standard box/rectangle-overlapping type of collision detection. If this is true, then you can proceed to look at what pixels are in the colliding zones (you must look at both). If they are transparent, return false... if not return true.

This is the quickest solution I can come up with right now, but I think it's pretty slow if you need to do it many times per frame.

Share this post


Link to post
Ezbez    1164
Plenty of information out there about this, [google] "pixel-perfect collision detection" and you'll get more than enough articles.

But, it's generally not necessary. You could use the 80% rule, where you just use a bounding box that is 80% of the size of actual image. It works pretty darn well, and is much easier. And note that this also has the advantage that you can now resolve the collision, where as with pixel-perfect collision, you don't actually have any information with which to bounce objects around, or even to push them apart so that they don't collide anymore.

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 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.
    • By markshaw001
      Hi i am new to this forum  i wanted to ask for help from all of you i want to generate real time terrain using a 32 bit heightmap i am good at c++ and have started learning Opengl as i am very interested in making landscapes in opengl i have looked around the internet for help about this topic but i am not getting the hang of the concepts and what they are doing can some here suggests me some good resources for making terrain engine please for example like tutorials,books etc so that i can understand the whole concept of terrain generation.
       
  • Popular Now