Exclusion collision detection is done by checking where certain parts of the two items are in correspondence to each other. Basically if the highest point of item A is lower than the lowest part of item B, it is not possible for the items to collide.

In addition, you can order your method based on which direction you are expecting collisions to usually occur from. This will then be more efficient than even the box detection method offered by the Sprite class.

public boolean collisionBetween(Sprite a, Sprite b)

{

if (a.getY() > (b.getY() + b.getHeight()))
{
//Not collided b is above a

return false;
}
else
{
if ((a.getY() + a.getHeight()) < b.getY())
{
//Not collided b is below a

return false;
}
else
{
if (a.getX() > (b.getY() + b.getWidth()))
{
//Not collided b is to the left of a

return false;
}
else
{
if ((a.getX() + a.getWidth()) < b.getX())
{
//Not collided b is to the right of a

return false;
}
}
}
}

//There is a collision

return true;

}
There might be a parenthesis error in here, as I did this in notepad at work. So I couldn’t check the syntax! From the formatting — which Wordpress kindly destroyed — it looks fine though.

Related posts:

1. ArrayList in J2ME and generics

© jim for 406 Not Acceptable, 2008. | Permalink | No comment | Add to del.icio.us
Post tags: game development, j2me, j2me code

Feed enhanced by Better Feed from Ozh

I’ve noticed that the most popular posts on this blog/waste of space on the internet, are those on the more technical subjects or problems with software. Namely J2ME Polish and Ubuntu. So maybe I should post more about them; although, I really did not intend for this blog to be heavily technical.

Related posts:

1. ArrayList in J2ME and generics
2. Annoying Turkish Script Kiddies

© jim for 406 Not Acceptable, 2008. | Permalink | No comment | Add to del.icio.us
Post tags: j2me, posts

Feed enhanced by Better Feed from Ozh

Anyway, expect this stuff in September/October. I’ll have a few articles written ready for when I finish the project.

What’s really annoying is that some people get an extra 4 days to do their coding… that’s not what I’d be calling fair…

Related posts:

1. ArrayList in J2ME and generics

© jim for 406 Not Acceptable, 2008. | Permalink | One comment | Add to del.icio.us
Post tags: games, j2me, Java

Feed enhanced by Better Feed from Ozh

Now what’s the only thing better than a poor integration plugin? No support, that’s what! A quick check on the J2ME Polish forums and you will find numerous posts asking how to fix these errors. So if you’ve tried going to the forums and had no luck (like everyone else,) you’ve come to the right place.

So here are a list of the problems and how to fix them.

 When starting NetBeans it prompts you with a message that states “org.netbeans.modules.java.platform/1 >1.10 required version found 1.9.2″(Or some other version) with options “Disable and continue or Exit”.

This one’s an annoying one, which occurs every now and again. I got this on 6.0 on Linux and 5.5 on Windows, but not with 6.5 on Windows. So how do you fix it?

Go to:

/usr/share/netbeans/platform7/modules

or in Windows (x being a version number)

Program Files\NetBeans 6.x\nb6.x\modules

If you can’t find this folder just search for  “de-enough-polish-netbeans.jar” as this is the file you need to edit. Open up “de-enough-polish-netbeans.jar” with a zip program (Winrar, rileroller, Winzip, etc) and edit the file at META-INF/MANIFEST.MF wih a text editor (notepad.) There will be a sentence that states:

org.netbeans.modules.java.platform/1 > 1.10

Change it to

org.netbeans.modules.java.platform/1 > 1.0

Reactivate the plugin in Netbeans and enjoy!

You are prompted to resolve reference problems relating to “Emulator Platform” or “SUN WTK 2.2 etc…” not being found.

This occurs to everyone…

Go to your an existing (non polish) project folder and open the folder nbproject. There should be a file called project.properties, open this with a text editor. Scroll down and there should be two lines stating:

platform.active=Sun_Java_TM__Wireless_Toolkit_2_5_2_for_CLDC
platform.active.description=Sun Java(TM) Wireless Toolkit 2.5.2 for CLDC

The versions may be different, as you may have a later Wireless Toolkit!

Now open the same file in your J2ME Polish project and replace the platform.active and platform.active.description lines with the ones from the non polish project.

Replace every occurance of “MPowerPlayer” with Sun_Java_TM__Wireless_Toolkit_2_5_2_for_CLDC (or what you had in your old project.)

Replace every occurance of “Emulator Platform” with Sun Java(TM) Wireless Toolkit 2.5.2 for CLDC  (or what you had in your old project.)

Close Netbeans and reopen and all should be fixed!

Related posts:

1. ArrayList in J2ME and generics
2. Fixing FLAC music for the N900 media player

© jim for 406 Not Acceptable, 2008. | Permalink | No comment | Add to del.icio.us
Post tags: j2me, J2ME Polish, Java, netbeans, Netbeans J2ME Polish

Feed enhanced by Better Feed from Ozh

Over the summer (read till October,) I’ll be busy working on my project; hopefully it won’t mean a massive lack of activity like my exams caused. In fact I should be able to write up some tips on using J2Me as I go along. I am rather lucky as I managed to persuade my supervisor to let me develop a game using J2Me, which should be lots of fun to make and test

I have noticed that although there are a few good sites, tutorials, and guides on developing games for J2Me; there is a distinct lack of help on how to use the Visual Game Designer and Visual Map Designer features that were introduced with Netbeans 6.0. (Correct me if I am wrong, but they weren’t in Netbeans 5.5.) Because these tools haven’t been around very long there is also a lack of books covering them. The only real useful information about using them is the sample ‘game’ included in the Netbeans Mobility pack. So when I get the time I’ll provide a guide on using these tools for a simple ‘game’.

In addition, I should be able to host the odd version of the game. As it will need testing on multiple devices and I can’t just go out and buy a load of phones! Of course the emulators are useful, but there are situations where the device can act differently. I’ve noticed this being the case when using JSR-226: The 2D Vector Graphics API. Annoying really as Vectors can be a great tool for mobile games. With their being a number of resolutions to work with vectors have a great advantage over sprites, but with the low implementation of JSR-226 in devices, I’ll be overlooking them.

Back to beer!

Related posts:

1. ArrayList in J2ME and generics

© jim for 406 Not Acceptable, 2008. | Permalink | 5 comments | Add to del.icio.us
Post tags: game, guide, j2me, mobile

Feed enhanced by Better Feed from Ozh