Whilst Vectors are dynamic, they bring about one annoying issue – you have to cast each entry back from an Object type to its original type on retrieval. This takes up a lot of processor cycles, and on phones processor cycles are a limited commodity. Secondly, you will have to use the Vector enumerator to iterate through your vectors. This is very processor intensive, in NaStar I found this was using around 30% of my cycles! Finally Vectors are synchronised, this means they are thread safe. Now a synchronised collection is much slower than an unsynchonised one; plus, you will most likely not need the safety benefits synchronisation brings. As you will usually be using one thread for acessing your collections in a game (in the main game loop.)

Now the J2ME Polish project gives you the chance to use some Java 1.5 features, most importantly generics are included. Second, an arraylist implementation is included, which uses generics. However, many people have had issues with integrating this plugin to their chosen IDE. I have worked out some fixes for Netbeans J2ME Polish integration, but when coding my project decided against using the tools.

So you now find yourself stuck between no generics, slow vectors, or fixing (and maintaining) a plugin.

If all you want is access to ArrayLists or generics, your best bet is to strip the ArrayList code from J2ME Polish and create your own lists. I guess you could simply find an implementation of ArrayList floating around on the web, but the J2ME Polish code is very good. You will then simply create a number of new ArrayList classes, such as SpriteList, EnemyList, et al. There will be two other classes that the ArrayList depends on, you should also clone these for each implementation; these will let you use for each loops! Let each list only deal with one defined type. Now you will no longer have to deal with Vectors and their iterators and will find your game runs a lot faster! I found around 20 – 60% of processor time was dealing with Iterators; whilst ArrayLists cut this down to under 10%. For my project this was the best performance tweak available.

Before anyone asks, no you can’t play my game! Sadly the rights are held by the University of Birmingham Whilst I doubt they care much about a J2Me game!

No related posts.

© jim for 406 Not Acceptable, 2010. | Permalink | No comment | Add to del.icio.us
Post tags: arraylists, j2me code, j2me performance, J2ME Polish, NaStar

Feed enhanced by Better Feed from Ozh

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

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