Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
Clarify that GCIR doesn't require a DInput device
  • Loading branch information
MissingNO123 authored Sep 24, 2017
1 parent a693d08 commit f6aa091
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,12 @@
# GCIR - Gamecube Controller Input Redirect
Fully re-mappable DInput GCN controller to Luma InputRedirect.
Also supports keyboard inputs.
Fully re-mappable GCN controller to Luma InputRedirect.
Also supports remappable keyboard inputs.

Technically supports any DInput device (i.e. Windows joystick), or any device that PyGame natively supports, but is currently mapped for a Gamecube Controller via a USB adapter.
Technically supports any DInput device (i.e. Windows joystick), or any device that PyGame supports (i.e. XBox 360 Controller), but is currently mapped for a Gamecube Controller via a USB adapter.

To remap controls, just edit the buttonMappings array or KBDButtons class in gamepad.py (or two.py if using multiple systems).

The buttonMappings array is just every button on your controller in order from 0, so if you want button 0 on your controller to be button A on the 3DS, put `HIDButtons.A` first in the list.
The buttonMappings array is a list of every button on your controller in order from 0 mapped to a 3DS button, so if you want button 0 on your controller to be button A on the 3DS, put `HIDButtons.A` first in the list.
Likewise, if you want button 3 to be A, put `HIDButtons.A` as the 4th item in the list.
If you want a high-numbered button (like the XBox 360 Guide button, 15 on some OSes) to be bound to a 3DS button, just add empty list entries (zero) in between the last button map and the one you want.

Expand Down

0 comments on commit f6aa091

Please sign in to comment.