79
edits
Changes
Jump to navigation
Jump to search
Line 16:
Line 16: + + + + + + + + + + + + + + + + + + + + + + + + Line 29:
Line 53: − + + + − Algorithm+ − + − + − +
no edit summary
I know the name is groan-worthy, but I figured if you can fit wii in the title somewhere why wouldn't you.
I know the name is groan-worthy, but I figured if you can fit wii in the title somewhere why wouldn't you.
== Controls ==
===In game===
{| class="wikitable" style="left;text-align:center;"
|-
! {{Wiimote}} !! Action
|-
| {{WiimoteAim}} || Move Cursor
|-
| {{Wiimote1Button}}+{{Wiimote2Button}} || See Gradient
|-
| {{WiimoteHomeButton}} || Exit to HBC
|}
== Progress ==
== Progress ==
I figured people might want to know how far along I am, but you have to bear in mind I have a full time job, and 2 young kids so it wont be the quickest development.
I figured people might want to know how far along I am, but you have to bear in mind I have a full time job, and 2 young kids so it wont be the quickest development.
24June2009: Started design. Got core algorithm - not tested it yet. Tracking IR position of 2 wiimotes (would be 4 but I only own 2, the code supports 4 - If anyone wants to donate a wiimote then feel free).
24June2009: Started design. Got core algorithm - not tested it yet. Tracking IR position of 2 wiimotes (would be 4 but I only own 2, the code supports 4 - If anyone wants to donate a wiimote then feel free).
26June2009: Got 2 dots painted on the screen where my 2 wiimotes point to. Added a basic timer so that I can track how many cycles my while(1) loop has done. Can now perform algorithm every X cycles. I am considering writing it all from scratch now, as modifying the algorithm would seem too much like a bodge - like the rest of my code.
26June2009: Got 2 dots painted on the screen where my 2 wiimotes point to. Added a basic timer so that I can track how many cycles my while(1) loop has done. Can now perform algorithm every X cycles. I am considering writing it all from scratch now, as modifying the algorithm would seem too much like a bodge - like the rest of my code.
29June2009: Been speaking with Christian Mauduit, the guy responsible for the latest version of LiquidWars. Helped clear a few things up. Currently, LiqwiidWars takes the 4 IR positions and -using 2 for loops- will create a "potential" for the armies.
It basically comes down to (psuedo) grid[player,x,y] = abs(wiimote(player).ir.x - x) + abs(wiimote(player).ir.y - y).
This ignores the "mesh" optimisation that might go in at a later date. All the "fighters" need to to is move to an area of equal or lower potential if they can. This algorithm is not affected by number of players or size of army - just size of map.
== Still to Do ==
== Still to Do ==
Maps
Maps - Load in a PNG and assign particular colour to the wall outline?
Algorithm - nearly done
Mesh - for v2
Army population
Army population - just add up fighters?
Music
Music - maybe play mp3's that are held in certain directory?
Menu
Menu - not even thought about yet
== External Links ==
== External Links ==