poebel / fceugc

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

Zapper cursor controlled by WiiMote 1 and buttons controlled by WiiMote 2 #211

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Play a standard NES zapper game on the Wii.

What is the expected output? What do you see instead?
I would expect the IR cursor and the trigger to be controlled by the same
WiiMote (WiiMote 2 for NES games), but instead the cursor is controlled by
WiiMote 1 and the buttons are on WiiMote 2.

What version are you using? On GameCube or Wii?
Wii

Are you using the official build (from the downloads page or auto-update)?
yes

Please provide any additional information below.
I just briefly looked at the code, but I would guess that line 

http://code.google.com/p/fceugc/source/browse/trunk/source/ngc/pad.cpp#523

should use the variable z instead of the constant 0 for choosing the
WiiMote to update the posx and posy for.

Original issue reported on code.google.com by sfriedma...@gmail.com on 25 Oct 2009 at 7:55

GoogleCodeExporter commented 9 years ago
actually that is hard coded to Wiimote 1 like that because that way people 
aren't 
confused about needing to use Wiimote 2 (plus if you don't have a second one 
handy 
to sync up!)

but there was a bug somewhere else in the code that I introduced recently, it's 
fixed now.

Original comment by dborth@gmail.com on 28 Oct 2009 at 12:12

GoogleCodeExporter commented 9 years ago

Original comment by dborth@gmail.com on 30 Nov 2009 at 8:15