Printable View
Well my game IS like a Fire Emblem game, only one unit moves at a time. They are moving through units because the obstacle detection system isn't adding them for some reason when I try to test if all but one (the one that is moving at the time) have a flag that is off.
Excellent - I'll look forward to it then :)
I think for games like this it would be good to use two separate arrays (or perhaps Z-indexes) to store obstacles - one containing fixed map obstacles (rivers, mountains, etc) and another for moveable obstacles (enemy units, etc). That ought to be more efficient, as you would very rarely (if ever) need to update the first array, and it would be very quick to just store the positions of moveable objects in the second array. The fixed movement range of units should allow for quite a few optimizations too.
Here's the latest version of my pathfinding engine: http://sdrv.ms/YUNp1D
Attachment 9587
This version is mainly meant for Advance Wars / Fire Emblem style games. It can handle tile costs between 1 and 99 (instead of just "obstacle" / "not an obstacle") making it possible for terrain to slow a unit without being impassable, and will also highlight all squares within the unit's movement range.
As with previous versions, it doesn't require any extensions that aren't Android / iOS compatible.
I think the Android exporter could handle a real-time strategy game, and there are ways to make a tower defense game unique enough to be good.Quote:
Originally Posted by MuddyMole
Anyway, if you don't add multiple unit support, then your example will be pointless for me, as tower defense games and real-time strategy games are the two main reasons that I want to use pathfinding in the first place.
You know what? There really aren't. GooglePlay already has over four hundred Tower Defense clones for Android, so there must be literally thousands of them if you include all the different versions for Flash, iOS, Windows, etc. The genre is completely and utterly played out.Quote:
Originally Posted by happygreenfrog
As for an RTS - if noone has been able to make a decent one even for Windows (and many have tried), then what hope is there for underpowered Android devices without the benefits of HWA, pathfinding extensions, etc? I'm not saying it's impossible, but I just don't see it happening...
That's fine if my example is of no use to you - Crusher's excellent example ought to suit your needs. However, that does have its limitations, such as the lack of support for tile costs and the poor performance in certain situations - and that's where my example comes in.
You, sir, have to see this. No HWA, possibly Android-compatible (at least, I don't remember it requiring any objects that the Android runtime can't use (it has a bad object or two that might not be compatible with the Android runtime, though (you can build applications that have incompatible extensions, though. It just ignores the incompatible extensions))), and it runs okay (I haven't actually tested it on an Android device (or an Android emulator, or anything Android) yet, though). I made an HWA version (though I have yet to publicly share it), though, and it runs even better. Anyway, it is possible to make a good RTS (or at least a good RTS engine) using MMF2 that can run on Android.Quote:
Originally Posted by MuddyMole
Note the comments:
"...your game really seems to be too slow I was managing 40fps with only the 3 main units on screen" Uprize
"..my laptop must be really slow if you guys are getting 40 fps. I'm only getting maximum of 12" RickyRombo
"The biggest downfall is that you have no pathfinding" Uprize
"But it's too slow in my system it's unplayable for me. :/" byo
And that's on Windows PCs - on an Android powered device it's going to be a slideshow.
You missed one:Quote:
Originally Posted by MuddyMole
I had 24 units on screen and fps never dropped below 47.
Also, I've optimized it before by making it use ForEach loops when possible, and it runs even faster with that optimization.
That's still not impressive.
Bear in mind that it's not really an RTS example - it's an excellent fog-of-war example (I'm sure that's what's causing the performance issues), with map loading and unit selection (both of which are pretty trivial). However, there is no pathfinding or even local obstacle avoidance, which will slow your game. More importantly, there are no enemy units which is one of the things that really hurts performance, because instead of just performing a calculation once per unit, it will often be once per combination of units, meaning that the number of calculations required will increase exponentially. Plus you could potentially have a lot of graphical effects (projectiles, explosions, magic spells, etc) going on, without the benefit of hardware acceleration.
And you want to do all that on mobile devices with nowhere near the power of a PC / laptop...
Not necessarily. Android is Hardware Accelerated using OpenGL. I have designed engines specifically for Android that run crud in standard runtime yet maintain a constant 60fps on Android.Quote:
Originally Posted by MuddyMole