Closed GoogleCodeExporter closed 9 years ago
The fact nunchuk only has 2 buttons would complicate a lot of things,
especially for button mapping (how would the emulator knows which button you
want to ignore) but also an important part of the input code would need to be
rewritten with that in mind and i don't want to do that, especially when it can
easily be bypassed on user side by getting a 2nd wiimote...
Original comment by ekeeke31@gmail.com
on 17 Sep 2013 at 6:08
Original comment by ekeeke31@gmail.com
on 17 Sep 2013 at 6:09
[deleted comment]
Regarding the controls "issue" with the Zero Tolerance hack, I can think of two
solutions that I'm not sure would require way too many changes in the code or
not, but will explain in case they're feasable:
-Currently, playing it as described would require two Wiimotes with one Nunchuk
connected to each (just so the first Wiimote can be held vertically), so the
need for this required yet unused Nunchuk can be solved by adding a new
controller option for "Wiimote (Vertical)".
This would be useful for RPGs and menu-based games as well (I think I even
opened a feature request for it some time ago), so it wouldn't be just a
specific "patch" for this situation, in any case.
-The other solution I can think of would be being able to assign separately
each controller and its attached device, as follows:
Imagine you have a Wiimote+Nunchuk and a Wiimote+Classic Controller currently
being detected by the console. When clicking on the assigned device for Player
1, the emulator would cycle between the currently detected individual devices
and the Wiimote+Nunchuk combination when found:
--None
--Wiimote+Nunchuk (1)
--Wiimote (1)
--Nunchuk (1)
--Wiimote (2)
--Classic Controller (2)
In the case of the opening post, the controls would just have to be assigned as:
PLAYER 1: Wiimote (1)
PLAYER 2: Nunchuk (1)
This would also make 4-player games possible with just two Wiimotes and two
Classic Controllers, for example (or even Nunchuks, for games that don't
require three buttons like Sonic or Bomberman).
As for how to ignore a button when defining the controls, perhaps there could
be a "HOME to skip" notice while it prompts for the button press (after all,
it's the only button that's never going to be mapped to anything else).
Original comment by iceknigh...@gmail.com
on 23 Sep 2013 at 4:18
Original issue reported on code.google.com by
vaguerant
on 17 Sep 2013 at 8:03