Click here to Skip to main content
13,735,397 members
Click here to Skip to main content
Add your own
alternative version

Tagged as


16 bookmarked
Posted 7 Apr 2010
Licenced CPOL

2D Collision Detection System

, 7 Apr 2010
Rate this:
Please Sign up or sign in to vote.
2D collision detection system with VB.NET


This article describes how to detect collisions between various objects in 2D environment. I created this collision detection system 2 years ago to use it in the game engine I'm currently developing. Programming is my hobby - I'm not a professional developer and I'm not familiar with all the technologies existing in the game physics and maybe that's why I've never seen such a collision detection method like mine. I suppose there is already such a collision detection system but I didn't found it yet, so please if you know articles that describe a similar collision detection method, please let me know. Also, I'll be very glad to hear your opinion and suggestions about my 2D collision detection method. Thank you.

The archive attached to this article contains a demo program that shows some of the abilities of my collision detection system. Run 'Rust_Engine.exe' executable in order to start the demo application. Here is some description how to use the demo application:


  • E - create object
  • W - move object
  • Del - delete all objects


  • Middle Button Click on object - delete current object
  • Single Left Click on object - select the current object
  • Double Left Click on object - select all objects
  • Single Right Click on object - opens the properties of the current object
  • Single Click on the playground - deselect all objects

Rust Engine demo also presents sound manipulation, animation, texture supporting, sorted drawing (isometric projection) and Act - React system, but anyway these things are not in the interests of this topic, maybe I'll explain how to create such interesting things another time :). Note that the used language is VB.NET, but the described method is universal and can be written in all languages in the Visual Studio family.


Instead of using only objects coordinates to detect a collision, my collision detection system will show you how to use mostly the playground as a source of information whether there is an object on the field or not. The collision detection method I'm about to explain doesn't need to know the exact count of objects in case of detecting collisions. Now imagine that your standing on the tiles in your bathroom. How many tiles are there under your feet? Let's suggest that there are 4.


Now let's think about this bathroom tiles as the pixels of your game world playground. Let's associate an integer array to all the pixels in your playground. To do that, we could declare an array like intWorldArr(224) As Integer. If we have playground 15 x 15 pixels then our array will contain 225 elements, one element for each pixel. And if we have an object that is 2 x 2 pixels, our object will occupy 4 pixels of the playground. If each pixel corresponds to an element into the integer array that represents the playground - intWorldArr(224) - then how to find that element the pixel refers to. It would be stupid to iterate through all 225 elements in case we need to find the element we need. To solve this problem, we will use the coordinates of the pixel and another integer array of which count of elements will be equal to the height of our playground - 15. So, we will declare another integer array - something like intStartNum(14) As Integer. Now look at the picture below - you can see that the numbers of the pixels in the first vertical column from left are colored in green. These green numbers are the values of each element in intStartNum(14) array. The first element has value 1, the second has value of 16 and so on each value grows with 15 (width of our playground) till it reach 211. Let's take a look at the purple object - its coordinates are x = 9 , y = 9 and its size is 2 x 2 pixels. Let's give a name to this object, for an example 1. Object 1 is placed on 145, 146, 160 and 161 pixel of our playground. So Object 1 will write its name into 145, 146, 160 and 161 element of intWorldArr:

intWorldArr(145) = 1
intWorldArr(146) = 1
intWorldArr(160) = 1
intWorldArr(161) = 1

That's how Object 1 will inform other objects about its presence. Looks good but how to find the number of the pixel that Object 1 stands on? Here comes to help us the second integer array intStartNum(14). If you already noticed in the picture below - adding the x coordinate of some pixel to the green number of its y coordinate will return the number of the pixel you are looking for. For an example Object 1 has coordinates x = 9, y = 9. To find the element into intWorldArr that corresponds to that location, we can do this simple task (objPrpl will be the purple object from the picture below):

intWorldArr(objPrpl.x + intStartNum(objPrpl.y)) = 1

This operation also assigns the name of the objPrpl into 145 element of intWorldArr. Now detecting collision between two or more objects is a piece of cake. You can use 0 for passable areas - if your object "see" that there is 0 or its name "into" the pixel he wanted to move, the movement will be allowed, if there is another number in the pixel in front of our object, the movement will be forbidden.


Let's now make a summary of all that was shown above:

1st: You need to make an integer array (intWorldArr) the size of which would be equal to the count of pixels in your playground.

2nd: Create another array (intStartNum) the size of which will be equal to the height (in pixels) of your playground. intStartNum will contain the first numbers of all pixels in the first left column of playground field - see the first picture above.

3rd: Create an array that will hold all your objects (objects array). It is very important that the name of each object be equal to its subscript in the objects array - this will help you to determine which of your objects collide and take proper action after collision occurs.

4th: Choose special numbers for your game world. For an example ' -1 ' = passable area. If ' 0 ' is your passable area, then when you assign names to your object, add 1 to avoid of creating one 'ghost' object that will fill the playground with passable numbers - ' 0 '.

Air Units Problem

You may say that this collision detection system is designed for detecting collisions only between ground units, and you're almost right. The biggest problem of this collision detection method is handling with the flying objects. Since there is only one layer of the playground if air unit are standing above ground unit, the positions of the ground unit shall be overwritten by the name of the flying unit above. And the ground unit shall became 'ghost' object and other units will stop notice its presence. To avoid such a confusion, you may add a second playground layer where flying units will move - for an example AirWorldArr(224). I know this is not a very elegant solution because it will lead to more memory consumption, but I'm still working on the problem. Any ideas from you are more than welcome!

Code Example

REM: the method that fills intWorldArr with the name of the moving object:

Sub FillWrldArr(ByVal HeroBody As ObjectBody, ByVal szeWrldSize As Size)

     Dim intStartPos = HeroBody.intLeft + intStartNum(HeroBody.intTop)
     Dim intEndPos = HeroBody.intRight + intStartNum(HeroBody.intTop)

     For i = 0 To HeroBody.intHeight
        For i2 = intStartPos To intEndPos
            intWorldArr(i2) = HeroBody.intName
            intStartPos += szeWrldSize.Width
            intEndPos += szeWrldSize.Width
 End Sub 


  • First release: 07.04.2010


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Bulgaria Bulgaria
Name: Ognian Gantchev Ivanov

Current Age: 27

Country: Bulgaria

City: Stara Zagora

Professional skills: fine arts, sculpture

Hobbies: Programming();

Computer Languages: VB, C#, C++

Human Languages: Bulgarian, English

About me:
I'm an enthusiast game developer. I love computers, art and science.

You may also be interested in...


Comments and Discussions

BugError Pin
Member 1192779320-Dec-15 21:01
memberMember 1192779320-Dec-15 21:01 
GeneralRe: Error Pin
OriginalGriff20-Dec-15 21:07
protectorOriginalGriff20-Dec-15 21:07 
GeneralRe: Error Pin
Member 1192779320-Dec-15 23:10
memberMember 1192779320-Dec-15 23:10 
GeneralMy vote of 5 Pin
soft weaver15-Oct-10 9:59
membersoft weaver15-Oct-10 9:59 
GeneralMy vote of 1 Pin
serzh838-Apr-10 0:58
memberserzh838-Apr-10 0:58 
GeneralRe: My vote of 1 Pin
O.G.I.8-Apr-10 3:36
memberO.G.I.8-Apr-10 3:36 
Generalhobby-talk Pin
Christ Kennedy7-Apr-10 16:43
memberChrist Kennedy7-Apr-10 16:43 
GeneralRe: hobby-talk Pin
Jitendra Zaa8-Apr-10 1:51
memberJitendra Zaa8-Apr-10 1:51 
GeneralRe: hobby-talk Pin
O.G.I.8-Apr-10 3:27
memberO.G.I.8-Apr-10 3:27 
GeneralRe: hobby-talk Pin
Shaheed Legion10-Jan-13 19:58
memberShaheed Legion10-Jan-13 19:58 
GeneralRe: hobby-talk Pin
O.G.I.12-Jan-13 2:26
memberO.G.I.12-Jan-13 2:26 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Permalink | Advertise | Privacy | Cookies | Terms of Use | Mobile
Web01-2016 | 2.8.180920.1 | Last Updated 7 Apr 2010
Article Copyright 2010 by O.G.I.
Everything else Copyright © CodeProject, 1999-2018
Layout: fixed | fluid