MathewWi / freespace2wii

Automatically exported from code.google.com/p/freespace2wii
Other
0 stars 0 forks source link

Energy management needs some special binding #6

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
For the PC version Freespace 2 uses 6 or 7 keys to deal with energy
management.  That is not acceptable for the Wii port.  Some kind of scheme
with a stick could work.  It needs to be implemented.

Original issue reported on code.google.com by litgh...@gmail.com on 17 May 2009 at 9:20

GoogleCodeExporter commented 9 years ago
would it be possible to set say the 'c' button as 'alt' or shift' that way you 
could
almost double the number of button bindings?

power management could then bound to the cursor & 1,2 buttons while holding 'c'

Original comment by godsa...@gmail.com on 19 May 2009 at 9:23

GoogleCodeExporter commented 9 years ago
That's a good idea. I'll need to look around the source, but I think that is 
doable.

Original comment by litgh...@gmail.com on 20 May 2009 at 12:16

GoogleCodeExporter commented 9 years ago
if possible here's a quick suggestion for bindings:

 * A - Fire primary (+C Target in recticle)
 * B - Fire secondary (+C Target hitpoint)
 * - - Target next enemy (+C Target next)
 * + - Toggle auto-speed (+C Target next bomber or bomb)
 * 1 - Switch secondaries (+C Switch primaries)
 * 2 - Equalise shield (+C Call support ship)
 * D-pad down - Countermeasure 
 * D-pad left - Increase weapon energy (+C decrease weapon energy)
 * D-pad right - Increase engine energy (+C decrease engine energy)
 * D-pad up - Increase shield energy (+C decrease shield energy)
 * Nunchunk Z - Afterburners
 * Nunchuck C - N/A 
 * Wiimote Pitch axis - Inverted Pitch control
 * Wiimote Yaw axis - Yaw control 
 * Nunchuck Y - Relative throttle (+C look back)
 * Nunchuck X - Bank (+C look left/right)
 * Home - esc (+C activate jump drive)

Original comment by godsa...@gmail.com on 21 May 2009 at 11:53

GoogleCodeExporter commented 9 years ago
Would adding a 2nd controller be a temporary possible fix?  Say you have your
wiimote/nunchuck, gamecube control, or a classic control, and you plug in a 2nd
gamecube control.  Add player 2's buttons to your?  Sounds stupid honestly 
hehe, you
tell me :D.

Original comment by Lunacine...@gmail.com on 23 May 2009 at 2:54

GoogleCodeExporter commented 9 years ago
Along the lines of the second controller it may also be possible to use the 
classic controller with the Wiimote.  
I pointed out in a different issue the A & B buttons only work on the Wiimote 
when the classic controller is 
connected.  I use the classic controller at the moment and use the Wiimote for 
commands I don't want to 
accidentally hit.  My current key config:

Wiimote:
* A - Call support Ship
* B - Engage subspace drive

Classic Controller:
* Left stick: Pitch and Yaw
* Right stick: Throttle and Roll
 * - - Target next hostile ship
 * + - Target next ship
 * X - Afterburner
 * Y - Target ship in reticle
 * D-pad down - Countermeasure 
 * D-pad left - Target next attacking ship
 * D-pad right - Equalize shields
 * D-pad up - Target next bomb or bomber
 * R Trigger - Fire Primary
 * ZR Trigger - Switch Primary
 * L Trigger - Secondary
 * ZL Trigger - Switch Secondary

Adding the A & B buttons to the classic controller would allow for a couple 
more commands (cover me, attack 
my target, target next subsystem....).

Also, if you could make some of the buttons on the Wiimote seperate from the 
classic (eg. the D-Pad comes 
up as the same input from both) then you could use it for even more commands.

Original comment by thet...@gmail.com on 25 May 2009 at 7:24

GoogleCodeExporter commented 9 years ago
So is there still hope of c = alt coming to light?  I don't think their could 
be a
better solution for quick buttons.  I still think we need the extra input of a 
2nd
controller for comm chat and other stuff.

Original comment by Lunacine...@gmail.com on 27 May 2009 at 12:39

GoogleCodeExporter commented 9 years ago
It should be possible, but I have been working on some regressions in the code 
first.

Original comment by litgh...@gmail.com on 27 May 2009 at 5:19

GoogleCodeExporter commented 9 years ago
In addition, what about keyboard support?  It might be a little awkward, but for
things you don't use very often (jump out, target next subsytem, comm menus, 
etc) it
would probably work awesome!

Original comment by Athe...@gmail.com on 23 Jun 2009 at 7:34