Pandora Wiki - User contributions [en]

Controllers

2015-02-01T23:32:18Z

Edgex004: Correct SNES in table. All version of the SNES EX emulator should work, but power save settings should be adjusted.

==Nintendo Wiimote==

This includes instructions on installing software and configuration to pair Nintendo Wii Wiimotes using [[Bluetooth]] to the Pandora, and using them as joystick controllers. This was done under the base install of Angstrom Linux provided on the Pandora, using Hotfix 4. This does not include setting up a sensor bar type setup, but should allow you to use classic controllers that plug into the Wiimote.

=== Installing the Drivers ===

Open a Terminal, and run the command
<source lang="bash">sudo opkg update</source>
It will give you a warning about responsibility, and asks for your user password. This will update the Angstrom packages stored on [[NAND]].

Then install the Wiimote drivers and software, cwiid, using the command
<source lang="bash">sudo opkg install cwiid</source>

=== Pairing the Wiimote ===

Make sure [[Bluetooth]] is enabled. In Hotfix 4, there's a script to "Toggle Bluetooth Status" in the Pandora menu under the "System" category. A light will turn on on the left hand side of the Pandora if [[Bluetooth]] is on, next to the network light.

Open a Terminal, and run the command and follow the directions.
<source lang="bash">wminput</source>
It will tell you to press 1+2 on the Wiimote to connect. On my Wiimotes, the lights flash and the fourth light on the Wiimote lights solid once paired. If you then quit the wminput application (for instance, by hitting CTRL-C), your Wiimote will un-pair and turn off. I usually just hide the Terminal in the background by minimizing the window while I run game emulators.

You can pair multiple Wiimotes, just run wminput a second time and follow the instructions to pair it. I only have two, and both lit the fourth light.

In [[PicoDrive]], the Sega Genesis emulator, in the controller settings, if you push left or right it will display different joysticks configured. You can set up the buttons for different players there. The Wiimotes appeared as joysticks 1 and 2, in the order in which I paired them.

=== Changing the Wiimote Configuration ===

You can edit ''/etc/cwiid/wminput/default'' and ''/etc/cwiid/wminput/buttons'' to map the buttons of the Wiimote. You should quit wminput and restart them for these changes to take effect. They are plain text files. I edited them using vim from the command line, which is not the most user friendly thing to describe. Because they're system files, I needed to use sudo again, so I ran
<source lang="bash">sudo vim /etc/cwiid/wminput/default</source>

By default, the Wiimote is set up to control the mouse with the accelerometer. This means, as you tilt the Wiimote left and right, your mouse will shift around. I found it a bit distracting, and so I commented out two lines in /etc/cwiid/wminput/default so they look like this:

<pre>
#Plugin.acc.X = REL_X
#Plugin.acc.Y = REL_Y
</pre>

Also, I use the Wiimote "sideways", like a traditional Nintendo controller. I changed the direction pad to reflect this. Though you can do that within emulator configurations, it seemed handier to just have that set up by default. To do this, make these changes in /etc/cwiid/wminput/buttons

<pre>
Wiimote.Up = KEY_LEFT
Wiimote.Down = KEY_RIGHT
Wiimote.Left = KEY_DOWN
Wiimote.Right = KEY_UP
</pre>

It is also possible to map the Wiimote or extension buttons to a virtual gamepad. See below for instructions.

== Nintendo Wii Classic Controller ==

There are two ways to use a Wiimote or Classic Controller with the Pandora:
* As a virtual gamepad. This means you can use it in games that support gamepads, and allows multiplayer in games that support it, but won't work in games that don't support gamepads.

* As a clone of the Pandora's gaming controls, by mapping it to the same keys. This theoretically means it would work in games that don't have gamepad support, or allow you to change the controls at all, as long as they are using the Pandora controls. However, currently, not all games will register the input with this method. SuperTux, OpenTyrian, PandoraPanic and Snes9X4D4P will. Giana's Return, Sqrxz and psx4pandora won't. Additionally, Mupen64Plus with the default PPSP Input Plugin won't - but the Blight Input Plugin will.

=== As a virtual gamepad ===

The default profile doesn't have classic controller buttons defined, but cwiid comes with a gamepad profile which does. You can load it in wminput like this using a terminal:
<source lang="bash">wminput -c gamepad</source>
Then connect your Wiimote and Classic Controller. You do not have to connect the Classic Controller before you connect the Wiimote.

However the analog sticks/dpad seemed to be set up wrong in the gamepad profile (''/etc/cwiid/wminput/gamepad''):
<pre>
Classic.Dpad.X = ABS_X
Classic.Dpad.Y = ABS_Y
Classic.LStick.X = ABS_HAT0X
Classic.LStick.Y = ABS_HAT0Y
Classic.RStick.X = ABS_HAT1X
Classic.RStick.Y = ABS_HAT1Y
</pre>

should be replaced with:
<pre>
Classic.Dpad.X = ABS_HAT0X
Classic.Dpad.Y = ABS_HAT0Y
Classic.LStick.X = ABS_X
Classic.LStick.Y = ABS_Y
Classic.RStick.X = ABS_RX
Classic.RStick.Y = ABS_RY
</pre>

Otherwise, you won't get proper analog input from the sticks, since PoV hats aren't analog.

=== As a clone of the Pandora's gaming controls ===

This method works well where it does, you get a clone of the Pandora's gaming controls (minus the nubs), that should theoretically work in all games that support the Pandora's gaming controls. However, because of differences in how the games receive input, not all will detect the "fake" input.

Here is the profile for the Pandora gaming controls:
<pre>
# D-Pad
Classic.Up = KEY_UP
Classic.Down = KEY_DOWN
Classic.Left = KEY_LEFT
Classic.Right = KEY_RIGHT

# Select, Start and Space
Classic.Minus = KEY_LEFTCTRL
Classic.Plus = KEY_LEFTALT
Classic.Home = KEY_SPACE

# BXYA on Pandora
Classic.A = KEY_END
Classic.B = KEY_PAGEDOWN
Classic.X = KEY_PAGEUP
Classic.Y = KEY_HOME
Classic.ZL = KEY_Q
Classic.ZR = KEY_P
Classic.L = KEY_RIGHTSHIFT
Classic.R = KEY_RIGHTCTRL
</pre>

Save that in /etc/cwiid/wminput - you can name it whatever you want, as long as you load it in wminput using "wminput -c filename" - and make sure to save it using UNIX line endings (LF).

Once the profile is loaded and your Wiimote/Classic Controller is connected, it will automatically work in some games, but not in others. This might be possible to change to work in all games by modifying the wminput source code.

=== Extra Information ===

* [http://abstrakraft.org/cwiid/browser/wminput/action_enum.txt List of bindable buttons, axises and keys for wminput]

== MS Xbox360 controller ==
[http://boards.openpandora.org/index.php?/topic/430-xboxdrv-support-for-xbox-and-xbox-360-wired-and-wireless-controllers/ link]

== Sony PS3 controller ==
[http://boards.openpandora.org/index.php?/topic/1136-sony-ps3-wireless-controller-and-pandora/ link]

== OUYA Controller ==

The OUYA controller plays extremely well with the Pandora. As with the Wii controller above, many games that support joystick input will work automatically or by using in game mappers. For most other games, [http://repo.openpandora.org/?page=detail&app=qjoypad-001 QJoyPad] allows the OUYA controller to mimic the Pandora controls. The controller has enough excess buttons to map keys that are helpful in navigation, such as Enter, Escape, Start, Select, and Right Click.

The touch pad on the OUYA controller can control mouse movement and perform Left Click/Drag.

=== How to Connect ===

1. Turn on Bluetooth Hardware.

2. Hold down the OUYA button on the gamepad(s) until two lights are flashing.

3. Enter the following into a terminal:
<source lang ="bash">hcitool scan</source>
Output should look like:
<source lang="bash">AD:DR:ES:SO:UY:A1 Broadcom Keyboard
AD:DR:ES:SO:UY:A2 Broadcom Keyboard1</source>
4. Then, for each of the controllers you would like to pair, use the hidd command with the address output from your terminal. For example, the first controller listed above:
<source lang="bash">sudo hidd --connect AD:DR:ES:SO:UY:A1</source>
If all goes well, there should be no output, and the first light on the controller should be lit.

== Mayflash GameCube to USB Adaptor ==

These adapters must be plugged in through a USB 2.0 hub, but are plug n' play after that. As with other controllers, QJoyPad is necessary for some programs in order to mimic the Pandora Controls.

== Program Specific Compatibility ==

After a controller is paired and found to be working with the Pandora, the following compatibility list can be used as a guide:

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Program
! Link
! Button Mapping
! [http://repo.openpandora.org/?page=detail&app=qjoypad-001 QJoyPad] Compatible
! Additional comments
|-
| DraStic
| [http://repo.openpandora.org/?page=detail&app=DraStic repo]
| {{No}}
| {{No}}
| No method found yet for using external controllers
|-
| PanMAME
| [http://repo.openpandora.org/?page=detail&app=panmame-advmenu-7927 repo]
| {{Yes}}
| n/a
|
|-
| SNES9x EX+
| [http://repo.openpandora.org/?page=detail&app=com.explusalpha.Snes9xPlus repo]
| {{Yes}}
| n/a
| Custom key maps work great. Bluetooth controller input does not currently prevent the Pandora from going to low poer mode, and the emulator will begin to freeze after the Pandora thinks that it is idle and turns on power saving. Suggest turning off idling power save while you play with a controller.
|-
| Not Tetris
| [http://repo.openpandora.org/?page=detail&app=nottetris_ptitseb repo]
| {{No}}
| {{Yes}}
| QJoyPad works fine. Map Escape and Enter to help with pausing and selections.
|-
| Flying Snake
| [http://repo.openpandora.org/?page=detail&app=flyingsnake_undexsym repo]
| {{No}}
| {{Yes}}
| QJoyPad works fine. Map Start in order to help you begin a new round.
|-
| Mini Slug Project
| [http://repo.openpandora.org/?page=detail&app=minislug_ptitseb repo]
| {{Maybe | Works with issues}}
| {{No}}
| Game auto maps the OUYA controller fine, but maps the directional to the left stick. Have not found a way to use the D-Pad. QJoyPad is ignored.
|-
| Mupen64plus v2.1
| [http://repo.openpandora.org/?page=detail&app=mupen64plus repo]
| {{Yes}}
| n/a
| If your controller is not already supported, it can be mapped by editing InputAutoConfig.ini - OUYA controllers and Mayflash GameCube-to-USB can be mapped and auto-detected using the following [https://drive.google.com/file/d/0B7nHCkhKNgw3cXhNVlc0WldGSUk/view?usp=sharing InputAutoCfg.ini]
|-
| Jedi Knight II: Jedi Outcast
| [http://repo.openpandora.org/?page=detail&app=jedioutcast_ptitseb repo]
| {{Maybe | Works With Issues}}
| {{No}}
| Can map buttons easily in-game, but have not found a way to map mouse look to the Right Analog Stick. Using QJoyPad to mimic mouse movement crashes the game. Playable with the OUYA Controller if you use the trackpad instead to control mouse look.
|-
| Duck Marines
| [http://repo.openpandora.org/?page=detail&app=duckmarines_ptitseb repo]
| {{Maybe | Automap Is Not Playable}}
| {{No}}
| Game detects external controllers and automaps, but the mapped controls are not usable for some controllers, and I have not yet found a way to correctly remap them.
|-
| PCSX ReARMed
| [http://repo.openpandora.org/?page=detail&app=package.pcsx_rearmed.notaz repo]
| {{Yes}}
| n/a
| Custom control maps work wonderfully.
|}

[[Category:Tutorials]]
[[Category:Bluetooth]]
[[Category:Keyboard]]

Controllers

2015-01-20T19:03:17Z

Edgex004: Double entered "Jedi Knight II"

==Nintendo Wiimote==

This includes instructions on installing software and configuration to pair Nintendo Wii Wiimotes using [[Bluetooth]] to the Pandora, and using them as joystick controllers. This was done under the base install of Angstrom Linux provided on the Pandora, using Hotfix 4. This does not include setting up a sensor bar type setup, but should allow you to use classic controllers that plug into the Wiimote.

=== Installing the Drivers ===

Open a Terminal, and run the command
<source lang="bash">sudo opkg update</source>
It will give you a warning about responsibility, and asks for your user password. This will update the Angstrom packages stored on [[NAND]].

Then install the Wiimote drivers and software, cwiid, using the command
<source lang="bash">sudo opkg install cwiid</source>

=== Pairing the Wiimote ===

Make sure [[Bluetooth]] is enabled. In Hotfix 4, there's a script to "Toggle Bluetooth Status" in the Pandora menu under the "System" category. A light will turn on on the left hand side of the Pandora if [[Bluetooth]] is on, next to the network light.

Open a Terminal, and run the command and follow the directions.
<source lang="bash">wminput</source>
It will tell you to press 1+2 on the Wiimote to connect. On my Wiimotes, the lights flash and the fourth light on the Wiimote lights solid once paired. If you then quit the wminput application (for instance, by hitting CTRL-C), your Wiimote will un-pair and turn off. I usually just hide the Terminal in the background by minimizing the window while I run game emulators.

You can pair multiple Wiimotes, just run wminput a second time and follow the instructions to pair it. I only have two, and both lit the fourth light.

In [[PicoDrive]], the Sega Genesis emulator, in the controller settings, if you push left or right it will display different joysticks configured. You can set up the buttons for different players there. The Wiimotes appeared as joysticks 1 and 2, in the order in which I paired them.

=== Changing the Wiimote Configuration ===

You can edit ''/etc/cwiid/wminput/default'' and ''/etc/cwiid/wminput/buttons'' to map the buttons of the Wiimote. You should quit wminput and restart them for these changes to take effect. They are plain text files. I edited them using vim from the command line, which is not the most user friendly thing to describe. Because they're system files, I needed to use sudo again, so I ran
<source lang="bash">sudo vim /etc/cwiid/wminput/default</source>

By default, the Wiimote is set up to control the mouse with the accelerometer. This means, as you tilt the Wiimote left and right, your mouse will shift around. I found it a bit distracting, and so I commented out two lines in /etc/cwiid/wminput/default so they look like this:

<pre>
#Plugin.acc.X = REL_X
#Plugin.acc.Y = REL_Y
</pre>

Also, I use the Wiimote "sideways", like a traditional Nintendo controller. I changed the direction pad to reflect this. Though you can do that within emulator configurations, it seemed handier to just have that set up by default. To do this, make these changes in /etc/cwiid/wminput/buttons

<pre>
Wiimote.Up = KEY_LEFT
Wiimote.Down = KEY_RIGHT
Wiimote.Left = KEY_DOWN
Wiimote.Right = KEY_UP
</pre>

It is also possible to map the Wiimote or extension buttons to a virtual gamepad. See below for instructions.

== Nintendo Wii Classic Controller ==

There are two ways to use a Wiimote or Classic Controller with the Pandora:
* As a virtual gamepad. This means you can use it in games that support gamepads, and allows multiplayer in games that support it, but won't work in games that don't support gamepads.

* As a clone of the Pandora's gaming controls, by mapping it to the same keys. This theoretically means it would work in games that don't have gamepad support, or allow you to change the controls at all, as long as they are using the Pandora controls. However, currently, not all games will register the input with this method. SuperTux, OpenTyrian, PandoraPanic and Snes9X4D4P will. Giana's Return, Sqrxz and psx4pandora won't. Additionally, Mupen64Plus with the default PPSP Input Plugin won't - but the Blight Input Plugin will.

=== As a virtual gamepad ===

The default profile doesn't have classic controller buttons defined, but cwiid comes with a gamepad profile which does. You can load it in wminput like this using a terminal:
<source lang="bash">wminput -c gamepad</source>
Then connect your Wiimote and Classic Controller. You do not have to connect the Classic Controller before you connect the Wiimote.

However the analog sticks/dpad seemed to be set up wrong in the gamepad profile (''/etc/cwiid/wminput/gamepad''):
<pre>
Classic.Dpad.X = ABS_X
Classic.Dpad.Y = ABS_Y
Classic.LStick.X = ABS_HAT0X
Classic.LStick.Y = ABS_HAT0Y
Classic.RStick.X = ABS_HAT1X
Classic.RStick.Y = ABS_HAT1Y
</pre>

should be replaced with:
<pre>
Classic.Dpad.X = ABS_HAT0X
Classic.Dpad.Y = ABS_HAT0Y
Classic.LStick.X = ABS_X
Classic.LStick.Y = ABS_Y
Classic.RStick.X = ABS_RX
Classic.RStick.Y = ABS_RY
</pre>

Otherwise, you won't get proper analog input from the sticks, since PoV hats aren't analog.

=== As a clone of the Pandora's gaming controls ===

This method works well where it does, you get a clone of the Pandora's gaming controls (minus the nubs), that should theoretically work in all games that support the Pandora's gaming controls. However, because of differences in how the games receive input, not all will detect the "fake" input.

Here is the profile for the Pandora gaming controls:
<pre>
# D-Pad
Classic.Up = KEY_UP
Classic.Down = KEY_DOWN
Classic.Left = KEY_LEFT
Classic.Right = KEY_RIGHT

# Select, Start and Space
Classic.Minus = KEY_LEFTCTRL
Classic.Plus = KEY_LEFTALT
Classic.Home = KEY_SPACE

# BXYA on Pandora
Classic.A = KEY_END
Classic.B = KEY_PAGEDOWN
Classic.X = KEY_PAGEUP
Classic.Y = KEY_HOME
Classic.ZL = KEY_Q
Classic.ZR = KEY_P
Classic.L = KEY_RIGHTSHIFT
Classic.R = KEY_RIGHTCTRL
</pre>

Save that in /etc/cwiid/wminput - you can name it whatever you want, as long as you load it in wminput using "wminput -c filename" - and make sure to save it using UNIX line endings (LF).

Once the profile is loaded and your Wiimote/Classic Controller is connected, it will automatically work in some games, but not in others. This might be possible to change to work in all games by modifying the wminput source code.

=== Extra Information ===

* [http://abstrakraft.org/cwiid/browser/wminput/action_enum.txt List of bindable buttons, axises and keys for wminput]

== MS Xbox360 controller ==
[http://boards.openpandora.org/index.php?/topic/430-xboxdrv-support-for-xbox-and-xbox-360-wired-and-wireless-controllers/ link]

== Sony PS3 controller ==
[http://boards.openpandora.org/index.php?/topic/1136-sony-ps3-wireless-controller-and-pandora/ link]

== OUYA Controller ==

The OUYA controller plays extremely well with the Pandora. As with the Wii controller above, many games that support joystick input will work automatically or by using in game mappers. For most other games, [http://repo.openpandora.org/?page=detail&app=qjoypad-001 QJoyPad] allows the OUYA controller to mimic the Pandora controls. The controller has enough excess buttons to map keys that are helpful in navigation, such as Enter, Escape, Start, Select, and Right Click.

The touch pad on the OUYA controller can control mouse movement and perform Left Click/Drag.

=== How to Connect ===

1. Turn on Bluetooth Hardware.

2. Hold down the OUYA button on the gamepad(s) until two lights are flashing.

3. Enter the following into a terminal:
<source lang ="bash">hcitool scan</source>
Output should look like:
<source lang="bash">AD:DR:ES:SO:UY:A1 Broadcom Keyboard
AD:DR:ES:SO:UY:A2 Broadcom Keyboard1</source>
4. Then, for each of the controllers you would like to pair, use the hidd command with the address output from your terminal. For example, the first controller listed above:
<source lang="bash">sudo hidd --connect AD:DR:ES:SO:UY:A1</source>
If all goes well, there should be no output, and the first light on the controller should be lit.

== Mayflash GameCube to USB Adaptor ==

These adapters must be plugged in through a USB 2.0 hub, but are plug n' play after that. As with other controllers, QJoyPad is necessary for some programs in order to mimic the Pandora Controls.

== Program Specific Compatibility ==

After a controller is paired and found to be working with the Pandora, the following compatibility list can be used as a guide:

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Program
! Link
! Button Mapping
! [http://repo.openpandora.org/?page=detail&app=qjoypad-001 QJoyPad] Compatible
! Additional comments
|-
| DraStic
| [http://repo.openpandora.org/?page=detail&app=DraStic repo]
| {{No}}
| {{No}}
| No method found yet for using external controllers
|-
| PanMAME
| [http://repo.openpandora.org/?page=detail&app=panmame-advmenu-7927 repo]
| {{Yes}}
| n/a
|
|-
| SNES9x EX+
| [http://repo.openpandora.org/?page=detail&app=com.explusalpha.Snes9xPlus repo]
| {{Yes}}
| n/a
| Custom key maps work great. Make sure to use the linked version of the PND. Other versions in the Repo suffer from crashes when external controllers are set up.
|-
| Not Tetris
| [http://repo.openpandora.org/?page=detail&app=nottetris_ptitseb repo]
| {{No}}
| {{Yes}}
| QJoyPad works fine. Map Escape and Enter to help with pausing and selections.
|-
| Flying Snake
| [http://repo.openpandora.org/?page=detail&app=flyingsnake_undexsym repo]
| {{No}}
| {{Yes}}
| QJoyPad works fine. Map Start to help you begin a new round.
|-
| Mini Slug Project
| [http://repo.openpandora.org/?page=detail&app=minislug_ptitseb repo]
| {{Maybe | Works with issues}}
| {{No}}
| Game auto maps the OUYA controller fine, but maps the directional to the left stick. Have not found a way to use the D-Pad. QJoyPad is ignored.
|-
| Mupen64plus v2.1
| [http://repo.openpandora.org/?page=detail&app=mupen64plus repo]
| {{Yes}}
| n/a
| If your controller is not already supported, it can be mapped by editing InputAutoConfig.ini - OUYA controllers and Mayflash GameCube-to-USB can be mapped and auto-detected using the following [https://drive.google.com/file/d/0B7nHCkhKNgw3cXhNVlc0WldGSUk/view?usp=sharing InputAutoCfg.ini]
|-
| Jedi Knight II: Jedi Outcast
| [http://repo.openpandora.org/?page=detail&app=jedioutcast_ptitseb repo]
| {{Maybe | Works With Issues}}
| {{No}}
| Can map buttons easily in-game, but have not found a way to map mouse look to the Right Analog Stick. Using QJoyPad to mimic mouse movement crashes the game. Playable with the OUYA Controller if you use the trackpad instead to control mouse look.
|-
| Duck Marines
| [http://repo.openpandora.org/?page=detail&app=duckmarines_ptitseb repo]
| {{Maybe | Automap Is Not Playable}}
| {{No}}
| Game detects external controllers and automaps, but the mapped controls are not usable for some controllers, and I have not yet found a way to correctly remap them.
|-
| PCSX ReARMed
| [http://repo.openpandora.org/?page=detail&app=package.pcsx_rearmed.notaz repo]
| {{Yes}}
| n/a
| Custom control maps work wonderfully.
|}

[[Category:Tutorials]]
[[Category:Bluetooth]]
[[Category:Keyboard]]

Controllers

2015-01-20T19:01:35Z

Edgex004: Changed "Custom Mapping" to "Button Mapping"

==Nintendo Wiimote==

This includes instructions on installing software and configuration to pair Nintendo Wii Wiimotes using [[Bluetooth]] to the Pandora, and using them as joystick controllers. This was done under the base install of Angstrom Linux provided on the Pandora, using Hotfix 4. This does not include setting up a sensor bar type setup, but should allow you to use classic controllers that plug into the Wiimote.

=== Installing the Drivers ===

Open a Terminal, and run the command
<source lang="bash">sudo opkg update</source>
It will give you a warning about responsibility, and asks for your user password. This will update the Angstrom packages stored on [[NAND]].

Then install the Wiimote drivers and software, cwiid, using the command
<source lang="bash">sudo opkg install cwiid</source>

=== Pairing the Wiimote ===

Make sure [[Bluetooth]] is enabled. In Hotfix 4, there's a script to "Toggle Bluetooth Status" in the Pandora menu under the "System" category. A light will turn on on the left hand side of the Pandora if [[Bluetooth]] is on, next to the network light.

Open a Terminal, and run the command and follow the directions.
<source lang="bash">wminput</source>
It will tell you to press 1+2 on the Wiimote to connect. On my Wiimotes, the lights flash and the fourth light on the Wiimote lights solid once paired. If you then quit the wminput application (for instance, by hitting CTRL-C), your Wiimote will un-pair and turn off. I usually just hide the Terminal in the background by minimizing the window while I run game emulators.

You can pair multiple Wiimotes, just run wminput a second time and follow the instructions to pair it. I only have two, and both lit the fourth light.

In [[PicoDrive]], the Sega Genesis emulator, in the controller settings, if you push left or right it will display different joysticks configured. You can set up the buttons for different players there. The Wiimotes appeared as joysticks 1 and 2, in the order in which I paired them.

=== Changing the Wiimote Configuration ===

You can edit ''/etc/cwiid/wminput/default'' and ''/etc/cwiid/wminput/buttons'' to map the buttons of the Wiimote. You should quit wminput and restart them for these changes to take effect. They are plain text files. I edited them using vim from the command line, which is not the most user friendly thing to describe. Because they're system files, I needed to use sudo again, so I ran
<source lang="bash">sudo vim /etc/cwiid/wminput/default</source>

By default, the Wiimote is set up to control the mouse with the accelerometer. This means, as you tilt the Wiimote left and right, your mouse will shift around. I found it a bit distracting, and so I commented out two lines in /etc/cwiid/wminput/default so they look like this:

<pre>
#Plugin.acc.X = REL_X
#Plugin.acc.Y = REL_Y
</pre>

Also, I use the Wiimote "sideways", like a traditional Nintendo controller. I changed the direction pad to reflect this. Though you can do that within emulator configurations, it seemed handier to just have that set up by default. To do this, make these changes in /etc/cwiid/wminput/buttons

<pre>
Wiimote.Up = KEY_LEFT
Wiimote.Down = KEY_RIGHT
Wiimote.Left = KEY_DOWN
Wiimote.Right = KEY_UP
</pre>

It is also possible to map the Wiimote or extension buttons to a virtual gamepad. See below for instructions.

== Nintendo Wii Classic Controller ==

There are two ways to use a Wiimote or Classic Controller with the Pandora:
* As a virtual gamepad. This means you can use it in games that support gamepads, and allows multiplayer in games that support it, but won't work in games that don't support gamepads.

* As a clone of the Pandora's gaming controls, by mapping it to the same keys. This theoretically means it would work in games that don't have gamepad support, or allow you to change the controls at all, as long as they are using the Pandora controls. However, currently, not all games will register the input with this method. SuperTux, OpenTyrian, PandoraPanic and Snes9X4D4P will. Giana's Return, Sqrxz and psx4pandora won't. Additionally, Mupen64Plus with the default PPSP Input Plugin won't - but the Blight Input Plugin will.

=== As a virtual gamepad ===

The default profile doesn't have classic controller buttons defined, but cwiid comes with a gamepad profile which does. You can load it in wminput like this using a terminal:
<source lang="bash">wminput -c gamepad</source>
Then connect your Wiimote and Classic Controller. You do not have to connect the Classic Controller before you connect the Wiimote.

However the analog sticks/dpad seemed to be set up wrong in the gamepad profile (''/etc/cwiid/wminput/gamepad''):
<pre>
Classic.Dpad.X = ABS_X
Classic.Dpad.Y = ABS_Y
Classic.LStick.X = ABS_HAT0X
Classic.LStick.Y = ABS_HAT0Y
Classic.RStick.X = ABS_HAT1X
Classic.RStick.Y = ABS_HAT1Y
</pre>

should be replaced with:
<pre>
Classic.Dpad.X = ABS_HAT0X
Classic.Dpad.Y = ABS_HAT0Y
Classic.LStick.X = ABS_X
Classic.LStick.Y = ABS_Y
Classic.RStick.X = ABS_RX
Classic.RStick.Y = ABS_RY
</pre>

Otherwise, you won't get proper analog input from the sticks, since PoV hats aren't analog.

=== As a clone of the Pandora's gaming controls ===

This method works well where it does, you get a clone of the Pandora's gaming controls (minus the nubs), that should theoretically work in all games that support the Pandora's gaming controls. However, because of differences in how the games receive input, not all will detect the "fake" input.

Here is the profile for the Pandora gaming controls:
<pre>
# D-Pad
Classic.Up = KEY_UP
Classic.Down = KEY_DOWN
Classic.Left = KEY_LEFT
Classic.Right = KEY_RIGHT

# Select, Start and Space
Classic.Minus = KEY_LEFTCTRL
Classic.Plus = KEY_LEFTALT
Classic.Home = KEY_SPACE

# BXYA on Pandora
Classic.A = KEY_END
Classic.B = KEY_PAGEDOWN
Classic.X = KEY_PAGEUP
Classic.Y = KEY_HOME
Classic.ZL = KEY_Q
Classic.ZR = KEY_P
Classic.L = KEY_RIGHTSHIFT
Classic.R = KEY_RIGHTCTRL
</pre>

Save that in /etc/cwiid/wminput - you can name it whatever you want, as long as you load it in wminput using "wminput -c filename" - and make sure to save it using UNIX line endings (LF).

Once the profile is loaded and your Wiimote/Classic Controller is connected, it will automatically work in some games, but not in others. This might be possible to change to work in all games by modifying the wminput source code.

=== Extra Information ===

* [http://abstrakraft.org/cwiid/browser/wminput/action_enum.txt List of bindable buttons, axises and keys for wminput]

== MS Xbox360 controller ==
[http://boards.openpandora.org/index.php?/topic/430-xboxdrv-support-for-xbox-and-xbox-360-wired-and-wireless-controllers/ link]

== Sony PS3 controller ==
[http://boards.openpandora.org/index.php?/topic/1136-sony-ps3-wireless-controller-and-pandora/ link]

== OUYA Controller ==

The OUYA controller plays extremely well with the Pandora. As with the Wii controller above, many games that support joystick input will work automatically or by using in game mappers. For most other games, [http://repo.openpandora.org/?page=detail&app=qjoypad-001 QJoyPad] allows the OUYA controller to mimic the Pandora controls. The controller has enough excess buttons to map keys that are helpful in navigation, such as Enter, Escape, Start, Select, and Right Click.

The touch pad on the OUYA controller can control mouse movement and perform Left Click/Drag.

=== How to Connect ===

1. Turn on Bluetooth Hardware.

2. Hold down the OUYA button on the gamepad(s) until two lights are flashing.

3. Enter the following into a terminal:
<source lang ="bash">hcitool scan</source>
Output should look like:
<source lang="bash">AD:DR:ES:SO:UY:A1 Broadcom Keyboard
AD:DR:ES:SO:UY:A2 Broadcom Keyboard1</source>
4. Then, for each of the controllers you would like to pair, use the hidd command with the address output from your terminal. For example, the first controller listed above:
<source lang="bash">sudo hidd --connect AD:DR:ES:SO:UY:A1</source>
If all goes well, there should be no output, and the first light on the controller should be lit.

== Mayflash GameCube to USB Adaptor ==

These adapters must be plugged in through a USB 2.0 hub, but are plug n' play after that. As with other controllers, QJoyPad is necessary for some programs in order to mimic the Pandora Controls.

== Program Specific Compatibility ==

After a controller is paired and found to be working with the Pandora, the following compatibility list can be used as a guide:

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Program
! Link
! Button Mapping
! [http://repo.openpandora.org/?page=detail&app=qjoypad-001 QJoyPad] Compatible
! Additional comments
|-
| DraStic
| [http://repo.openpandora.org/?page=detail&app=DraStic repo]
| {{No}}
| {{No}}
| No method found yet for using external controllers
|-
| PanMAME
| [http://repo.openpandora.org/?page=detail&app=panmame-advmenu-7927 repo]
| {{Yes}}
| n/a
|
|-
| SNES9x EX+
| [http://repo.openpandora.org/?page=detail&app=com.explusalpha.Snes9xPlus repo]
| {{Yes}}
| n/a
| Custom key maps work great. Make sure to use the linked version of the PND. Other versions in the Repo suffer from crashes when external controllers are set up.
|-
| Not Tetris
| [http://repo.openpandora.org/?page=detail&app=nottetris_ptitseb repo]
| {{No}}
| {{Yes}}
| QJoyPad works fine. Map Escape and Enter to help with pausing and selections.
|-
| Flying Snake
| [http://repo.openpandora.org/?page=detail&app=flyingsnake_undexsym repo]
| {{No}}
| {{Yes}}
| QJoyPad works fine. Map Start to help you begin a new round.
|-
| Mini Slug Project
| [http://repo.openpandora.org/?page=detail&app=minislug_ptitseb repo]
| {{Maybe | Works with issues}}
| {{No}}
| Game auto maps the OUYA controller fine, but maps the directional to the left stick. Have not found a way to use the D-Pad. QJoyPad is ignored.
|-
| Mupen64plus v2.1
| [http://repo.openpandora.org/?page=detail&app=mupen64plus repo]
| {{Yes}}
| n/a
| If your controller is not already supported, it can be mapped by editing InputAutoConfig.ini - OUYA controllers and Mayflash GameCube-to-USB can be mapped and auto-detected using the following [https://drive.google.com/file/d/0B7nHCkhKNgw3cXhNVlc0WldGSUk/view?usp=sharing InputAutoCfg.ini]
|-
| Jedi Knight II: Jedi Outcast
| [http://repo.openpandora.org/?page=detail&app=jedioutcast_ptitseb repo]
| {{Maybe | Works With Issues}}
| {{No}}
| Can map buttons easily in-game, but have not found a way to map mouse look to the Right Analog Stick. Using QJoyPad to mimic mouse movement crashes the game. Playable with the OUYA Controller if you use the trackpad instead to control mouse look.
|-
| Jedi Knight II: Jedi Outcast
| [http://repo.openpandora.org/?page=detail&app=jedioutcast_ptitseb repo]
| {{Maybe | Works With Issues}}
| {{No}}
| Can map buttons easily in-game, but have not found a way to map mouse look to the Right Analog Stick. Using QJoyPad to mimic mouse movement crashes the game. Playable with the OUYA Controller if you use the trackpad instead to control mouse look.
|-
| Duck Marines
| [http://repo.openpandora.org/?page=detail&app=duckmarines_ptitseb repo]
| {{Maybe | Automap Is Not Playable}}
| {{No}}
| Game detects external controllers and automaps, but the mapped controls are not usable for some controllers, and I have not yet found a way to correctly remap them.
|-
| PCSX ReARMed
| [http://repo.openpandora.org/?page=detail&app=package.pcsx_rearmed.notaz repo]
| {{Yes}}
| n/a
| Custom control maps work wonderfully.
|}

[[Category:Tutorials]]
[[Category:Bluetooth]]
[[Category:Keyboard]]

Controllers

2015-01-20T19:00:16Z

Edgex004: Update Compatibility List

==Nintendo Wiimote==

This includes instructions on installing software and configuration to pair Nintendo Wii Wiimotes using [[Bluetooth]] to the Pandora, and using them as joystick controllers. This was done under the base install of Angstrom Linux provided on the Pandora, using Hotfix 4. This does not include setting up a sensor bar type setup, but should allow you to use classic controllers that plug into the Wiimote.

=== Installing the Drivers ===

Open a Terminal, and run the command
<source lang="bash">sudo opkg update</source>
It will give you a warning about responsibility, and asks for your user password. This will update the Angstrom packages stored on [[NAND]].

Then install the Wiimote drivers and software, cwiid, using the command
<source lang="bash">sudo opkg install cwiid</source>

=== Pairing the Wiimote ===

Make sure [[Bluetooth]] is enabled. In Hotfix 4, there's a script to "Toggle Bluetooth Status" in the Pandora menu under the "System" category. A light will turn on on the left hand side of the Pandora if [[Bluetooth]] is on, next to the network light.

Open a Terminal, and run the command and follow the directions.
<source lang="bash">wminput</source>
It will tell you to press 1+2 on the Wiimote to connect. On my Wiimotes, the lights flash and the fourth light on the Wiimote lights solid once paired. If you then quit the wminput application (for instance, by hitting CTRL-C), your Wiimote will un-pair and turn off. I usually just hide the Terminal in the background by minimizing the window while I run game emulators.

You can pair multiple Wiimotes, just run wminput a second time and follow the instructions to pair it. I only have two, and both lit the fourth light.

In [[PicoDrive]], the Sega Genesis emulator, in the controller settings, if you push left or right it will display different joysticks configured. You can set up the buttons for different players there. The Wiimotes appeared as joysticks 1 and 2, in the order in which I paired them.

=== Changing the Wiimote Configuration ===

You can edit ''/etc/cwiid/wminput/default'' and ''/etc/cwiid/wminput/buttons'' to map the buttons of the Wiimote. You should quit wminput and restart them for these changes to take effect. They are plain text files. I edited them using vim from the command line, which is not the most user friendly thing to describe. Because they're system files, I needed to use sudo again, so I ran
<source lang="bash">sudo vim /etc/cwiid/wminput/default</source>

By default, the Wiimote is set up to control the mouse with the accelerometer. This means, as you tilt the Wiimote left and right, your mouse will shift around. I found it a bit distracting, and so I commented out two lines in /etc/cwiid/wminput/default so they look like this:

<pre>
#Plugin.acc.X = REL_X
#Plugin.acc.Y = REL_Y
</pre>

Also, I use the Wiimote "sideways", like a traditional Nintendo controller. I changed the direction pad to reflect this. Though you can do that within emulator configurations, it seemed handier to just have that set up by default. To do this, make these changes in /etc/cwiid/wminput/buttons

<pre>
Wiimote.Up = KEY_LEFT
Wiimote.Down = KEY_RIGHT
Wiimote.Left = KEY_DOWN
Wiimote.Right = KEY_UP
</pre>

It is also possible to map the Wiimote or extension buttons to a virtual gamepad. See below for instructions.

== Nintendo Wii Classic Controller ==

There are two ways to use a Wiimote or Classic Controller with the Pandora:
* As a virtual gamepad. This means you can use it in games that support gamepads, and allows multiplayer in games that support it, but won't work in games that don't support gamepads.

* As a clone of the Pandora's gaming controls, by mapping it to the same keys. This theoretically means it would work in games that don't have gamepad support, or allow you to change the controls at all, as long as they are using the Pandora controls. However, currently, not all games will register the input with this method. SuperTux, OpenTyrian, PandoraPanic and Snes9X4D4P will. Giana's Return, Sqrxz and psx4pandora won't. Additionally, Mupen64Plus with the default PPSP Input Plugin won't - but the Blight Input Plugin will.

=== As a virtual gamepad ===

The default profile doesn't have classic controller buttons defined, but cwiid comes with a gamepad profile which does. You can load it in wminput like this using a terminal:
<source lang="bash">wminput -c gamepad</source>
Then connect your Wiimote and Classic Controller. You do not have to connect the Classic Controller before you connect the Wiimote.

However the analog sticks/dpad seemed to be set up wrong in the gamepad profile (''/etc/cwiid/wminput/gamepad''):
<pre>
Classic.Dpad.X = ABS_X
Classic.Dpad.Y = ABS_Y
Classic.LStick.X = ABS_HAT0X
Classic.LStick.Y = ABS_HAT0Y
Classic.RStick.X = ABS_HAT1X
Classic.RStick.Y = ABS_HAT1Y
</pre>

should be replaced with:
<pre>
Classic.Dpad.X = ABS_HAT0X
Classic.Dpad.Y = ABS_HAT0Y
Classic.LStick.X = ABS_X
Classic.LStick.Y = ABS_Y
Classic.RStick.X = ABS_RX
Classic.RStick.Y = ABS_RY
</pre>

Otherwise, you won't get proper analog input from the sticks, since PoV hats aren't analog.

=== As a clone of the Pandora's gaming controls ===

This method works well where it does, you get a clone of the Pandora's gaming controls (minus the nubs), that should theoretically work in all games that support the Pandora's gaming controls. However, because of differences in how the games receive input, not all will detect the "fake" input.

Here is the profile for the Pandora gaming controls:
<pre>
# D-Pad
Classic.Up = KEY_UP
Classic.Down = KEY_DOWN
Classic.Left = KEY_LEFT
Classic.Right = KEY_RIGHT

# Select, Start and Space
Classic.Minus = KEY_LEFTCTRL
Classic.Plus = KEY_LEFTALT
Classic.Home = KEY_SPACE

# BXYA on Pandora
Classic.A = KEY_END
Classic.B = KEY_PAGEDOWN
Classic.X = KEY_PAGEUP
Classic.Y = KEY_HOME
Classic.ZL = KEY_Q
Classic.ZR = KEY_P
Classic.L = KEY_RIGHTSHIFT
Classic.R = KEY_RIGHTCTRL
</pre>

Save that in /etc/cwiid/wminput - you can name it whatever you want, as long as you load it in wminput using "wminput -c filename" - and make sure to save it using UNIX line endings (LF).

Once the profile is loaded and your Wiimote/Classic Controller is connected, it will automatically work in some games, but not in others. This might be possible to change to work in all games by modifying the wminput source code.

=== Extra Information ===

* [http://abstrakraft.org/cwiid/browser/wminput/action_enum.txt List of bindable buttons, axises and keys for wminput]

== MS Xbox360 controller ==
[http://boards.openpandora.org/index.php?/topic/430-xboxdrv-support-for-xbox-and-xbox-360-wired-and-wireless-controllers/ link]

== Sony PS3 controller ==
[http://boards.openpandora.org/index.php?/topic/1136-sony-ps3-wireless-controller-and-pandora/ link]

== OUYA Controller ==

The OUYA controller plays extremely well with the Pandora. As with the Wii controller above, many games that support joystick input will work automatically or by using in game mappers. For most other games, [http://repo.openpandora.org/?page=detail&app=qjoypad-001 QJoyPad] allows the OUYA controller to mimic the Pandora controls. The controller has enough excess buttons to map keys that are helpful in navigation, such as Enter, Escape, Start, Select, and Right Click.

The touch pad on the OUYA controller can control mouse movement and perform Left Click/Drag.

=== How to Connect ===

1. Turn on Bluetooth Hardware.

2. Hold down the OUYA button on the gamepad(s) until two lights are flashing.

3. Enter the following into a terminal:
<source lang ="bash">hcitool scan</source>
Output should look like:
<source lang="bash">AD:DR:ES:SO:UY:A1 Broadcom Keyboard
AD:DR:ES:SO:UY:A2 Broadcom Keyboard1</source>
4. Then, for each of the controllers you would like to pair, use the hidd command with the address output from your terminal. For example, the first controller listed above:
<source lang="bash">sudo hidd --connect AD:DR:ES:SO:UY:A1</source>
If all goes well, there should be no output, and the first light on the controller should be lit.

== Mayflash GameCube to USB Adaptor ==

These adapters must be plugged in through a USB 2.0 hub, but are plug n' play after that. As with other controllers, QJoyPad is necessary for some programs in order to mimic the Pandora Controls.

== Program Specific Compatibility ==

After a controller is paired and found to be working with the Pandora, the following compatibility list can be used as a guide:

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Program
! Link
! Custom Mapping
! [http://repo.openpandora.org/?page=detail&app=qjoypad-001 QJoyPad] Compatible
! Additional comments
|-
| DraStic
| [http://repo.openpandora.org/?page=detail&app=DraStic repo]
| {{No}}
| {{No}}
| No method found yet for using external controllers
|-
| PanMAME
| [http://repo.openpandora.org/?page=detail&app=panmame-advmenu-7927 repo]
| {{Yes}}
| n/a
|
|-
| SNES9x EX+
| [http://repo.openpandora.org/?page=detail&app=com.explusalpha.Snes9xPlus repo]
| {{Yes}}
| n/a
| Custom key maps work great. Make sure to use the linked version of the PND. Other versions in the Repo suffer from crashes when external controllers are set up.
|-
| Not Tetris
| [http://repo.openpandora.org/?page=detail&app=nottetris_ptitseb repo]
| {{No}}
| {{Yes}}
| QJoyPad works fine. Map Escape and Enter to help with pausing and selections.
|-
| Flying Snake
| [http://repo.openpandora.org/?page=detail&app=flyingsnake_undexsym repo]
| {{No}}
| {{Yes}}
| QJoyPad works fine. Map Start to help you begin a new round.
|-
| Mini Slug Project
| [http://repo.openpandora.org/?page=detail&app=minislug_ptitseb repo]
| {{Maybe | Works with issues}}
| {{No}}
| Game auto maps the OUYA controller fine, but maps the directional to the left stick. Have not found a way to use the D-Pad. QJoyPad is ignored.
|-
| Mupen64plus v2.1
| [http://repo.openpandora.org/?page=detail&app=mupen64plus repo]
| {{Yes}}
| n/a
| If your controller is not already supported, it can be mapped by editing InputAutoConfig.ini - OUYA controllers and Mayflash GameCube-to-USB can be mapped and auto-detected using the following [https://drive.google.com/file/d/0B7nHCkhKNgw3cXhNVlc0WldGSUk/view?usp=sharing InputAutoCfg.ini]
|-
| Jedi Knight II: Jedi Outcast
| [http://repo.openpandora.org/?page=detail&app=jedioutcast_ptitseb repo]
| {{Maybe | Works With Issues}}
| {{No}}
| Can map buttons easily in-game, but have not found a way to map mouse look to the Right Analog Stick. Using QJoyPad to mimic mouse movement crashes the game. Playable with the OUYA Controller if you use the trackpad instead to control mouse look.
|-
| Jedi Knight II: Jedi Outcast
| [http://repo.openpandora.org/?page=detail&app=jedioutcast_ptitseb repo]
| {{Maybe | Works With Issues}}
| {{No}}
| Can map buttons easily in-game, but have not found a way to map mouse look to the Right Analog Stick. Using QJoyPad to mimic mouse movement crashes the game. Playable with the OUYA Controller if you use the trackpad instead to control mouse look.
|-
| Duck Marines
| [http://repo.openpandora.org/?page=detail&app=duckmarines_ptitseb repo]
| {{Maybe | Automap Is Not Playable}}
| {{No}}
| Game detects external controllers and automaps, but the mapped controls are not usable for some controllers, and I have not yet found a way to correctly remap them.
|-
| PCSX ReARMed
| [http://repo.openpandora.org/?page=detail&app=package.pcsx_rearmed.notaz repo]
| {{Yes}}
| n/a
| Custom control maps work wonderfully.
|}

[[Category:Tutorials]]
[[Category:Bluetooth]]
[[Category:Keyboard]]

Controllers

2015-01-20T06:14:19Z

Edgex004: Added OUYA controller instructions, Mayflash GC-to-USB, and a program compatibility list

==Nintendo Wiimote==

This includes instructions on installing software and configuration to pair Nintendo Wii Wiimotes using [[Bluetooth]] to the Pandora, and using them as joystick controllers. This was done under the base install of Angstrom Linux provided on the Pandora, using Hotfix 4. This does not include setting up a sensor bar type setup, but should allow you to use classic controllers that plug into the Wiimote.

=== Installing the Drivers ===

Open a Terminal, and run the command
<source lang="bash">sudo opkg update</source>
It will give you a warning about responsibility, and asks for your user password. This will update the Angstrom packages stored on [[NAND]].

Then install the Wiimote drivers and software, cwiid, using the command
<source lang="bash">sudo opkg install cwiid</source>

=== Pairing the Wiimote ===

Make sure [[Bluetooth]] is enabled. In Hotfix 4, there's a script to "Toggle Bluetooth Status" in the Pandora menu under the "System" category. A light will turn on on the left hand side of the Pandora if [[Bluetooth]] is on, next to the network light.

Open a Terminal, and run the command and follow the directions.
<source lang="bash">wminput</source>
It will tell you to press 1+2 on the Wiimote to connect. On my Wiimotes, the lights flash and the fourth light on the Wiimote lights solid once paired. If you then quit the wminput application (for instance, by hitting CTRL-C), your Wiimote will un-pair and turn off. I usually just hide the Terminal in the background by minimizing the window while I run game emulators.

You can pair multiple Wiimotes, just run wminput a second time and follow the instructions to pair it. I only have two, and both lit the fourth light.

In [[PicoDrive]], the Sega Genesis emulator, in the controller settings, if you push left or right it will display different joysticks configured. You can set up the buttons for different players there. The Wiimotes appeared as joysticks 1 and 2, in the order in which I paired them.

=== Changing the Wiimote Configuration ===

You can edit ''/etc/cwiid/wminput/default'' and ''/etc/cwiid/wminput/buttons'' to map the buttons of the Wiimote. You should quit wminput and restart them for these changes to take effect. They are plain text files. I edited them using vim from the command line, which is not the most user friendly thing to describe. Because they're system files, I needed to use sudo again, so I ran
<source lang="bash">sudo vim /etc/cwiid/wminput/default</source>

By default, the Wiimote is set up to control the mouse with the accelerometer. This means, as you tilt the Wiimote left and right, your mouse will shift around. I found it a bit distracting, and so I commented out two lines in /etc/cwiid/wminput/default so they look like this:

<pre>
#Plugin.acc.X = REL_X
#Plugin.acc.Y = REL_Y
</pre>

Also, I use the Wiimote "sideways", like a traditional Nintendo controller. I changed the direction pad to reflect this. Though you can do that within emulator configurations, it seemed handier to just have that set up by default. To do this, make these changes in /etc/cwiid/wminput/buttons

<pre>
Wiimote.Up = KEY_LEFT
Wiimote.Down = KEY_RIGHT
Wiimote.Left = KEY_DOWN
Wiimote.Right = KEY_UP
</pre>

It is also possible to map the Wiimote or extension buttons to a virtual gamepad. See below for instructions.

== Nintendo Wii Classic Controller ==

There are two ways to use a Wiimote or Classic Controller with the Pandora:
* As a virtual gamepad. This means you can use it in games that support gamepads, and allows multiplayer in games that support it, but won't work in games that don't support gamepads.

* As a clone of the Pandora's gaming controls, by mapping it to the same keys. This theoretically means it would work in games that don't have gamepad support, or allow you to change the controls at all, as long as they are using the Pandora controls. However, currently, not all games will register the input with this method. SuperTux, OpenTyrian, PandoraPanic and Snes9X4D4P will. Giana's Return, Sqrxz and psx4pandora won't. Additionally, Mupen64Plus with the default PPSP Input Plugin won't - but the Blight Input Plugin will.

=== As a virtual gamepad ===

The default profile doesn't have classic controller buttons defined, but cwiid comes with a gamepad profile which does. You can load it in wminput like this using a terminal:
<source lang="bash">wminput -c gamepad</source>
Then connect your Wiimote and Classic Controller. You do not have to connect the Classic Controller before you connect the Wiimote.

However the analog sticks/dpad seemed to be set up wrong in the gamepad profile (''/etc/cwiid/wminput/gamepad''):
<pre>
Classic.Dpad.X = ABS_X
Classic.Dpad.Y = ABS_Y
Classic.LStick.X = ABS_HAT0X
Classic.LStick.Y = ABS_HAT0Y
Classic.RStick.X = ABS_HAT1X
Classic.RStick.Y = ABS_HAT1Y
</pre>

should be replaced with:
<pre>
Classic.Dpad.X = ABS_HAT0X
Classic.Dpad.Y = ABS_HAT0Y
Classic.LStick.X = ABS_X
Classic.LStick.Y = ABS_Y
Classic.RStick.X = ABS_RX
Classic.RStick.Y = ABS_RY
</pre>

Otherwise, you won't get proper analog input from the sticks, since PoV hats aren't analog.

=== As a clone of the Pandora's gaming controls ===

This method works well where it does, you get a clone of the Pandora's gaming controls (minus the nubs), that should theoretically work in all games that support the Pandora's gaming controls. However, because of differences in how the games receive input, not all will detect the "fake" input.

Here is the profile for the Pandora gaming controls:
<pre>
# D-Pad
Classic.Up = KEY_UP
Classic.Down = KEY_DOWN
Classic.Left = KEY_LEFT
Classic.Right = KEY_RIGHT

# Select, Start and Space
Classic.Minus = KEY_LEFTCTRL
Classic.Plus = KEY_LEFTALT
Classic.Home = KEY_SPACE

# BXYA on Pandora
Classic.A = KEY_END
Classic.B = KEY_PAGEDOWN
Classic.X = KEY_PAGEUP
Classic.Y = KEY_HOME
Classic.ZL = KEY_Q
Classic.ZR = KEY_P
Classic.L = KEY_RIGHTSHIFT
Classic.R = KEY_RIGHTCTRL
</pre>

Save that in /etc/cwiid/wminput - you can name it whatever you want, as long as you load it in wminput using "wminput -c filename" - and make sure to save it using UNIX line endings (LF).

Once the profile is loaded and your Wiimote/Classic Controller is connected, it will automatically work in some games, but not in others. This might be possible to change to work in all games by modifying the wminput source code.

=== Extra Information ===

* [http://abstrakraft.org/cwiid/browser/wminput/action_enum.txt List of bindable buttons, axises and keys for wminput]

== MS Xbox360 controller ==
[http://boards.openpandora.org/index.php?/topic/430-xboxdrv-support-for-xbox-and-xbox-360-wired-and-wireless-controllers/ link]

== Sony PS3 controller ==
[http://boards.openpandora.org/index.php?/topic/1136-sony-ps3-wireless-controller-and-pandora/ link]

== OUYA Controller ==

The OUYA controller plays extremely well with the Pandora. As with the Wii controller above, many games that support joystick input will work automatically or by using in game mappers. For most other games, [http://repo.openpandora.org/?page=detail&app=qjoypad-001 QJoyPad] allows the OUYA controller to mimic the Pandora controls. The controller has enough excess buttons to map keys that are helpful in navigation, such as Enter, Escape, Start, Select, and Right Click.

The touch pad on the OUYA controller can control mouse movement and perform Left Click/Drag.

=== How to Connect ===

1. Turn on Bluetooth Hardware.

2. Hold down the OUYA button on the gamepad(s) until two lights are flashing.

3. Enter the following into a terminal:
<source lang ="bash">hcitool scan</source>
Output should look like:
<source lang="bash">AD:DR:ES:SO:UY:A1 Broadcom Keyboard
AD:DR:ES:SO:UY:A2 Broadcom Keyboard1</source>
4. Then, for each of the controllers you would like to pair, use the hidd command with the address output from your terminal. For example, the first controller listed above:
<source lang="bash">sudo hidd --connect AD:DR:ES:SO:UY:A1</source>
If all goes well, there should be no output, and the first light on the controller should be lit.

== Mayflash GameCube to USB Adaptor ==

These adapters must be plugged in through a USB 2.0 hub, but are plug n' play.

== Program Specific Compatibility ==

After a controller is paired and found to be working with the Pandora, the following compatibility list can be used as a guide:

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Program
! Link
! Custom Mapping
! [http://repo.openpandora.org/?page=detail&app=qjoypad-001 QJoyPad] Compatible
! Additional comments
|-
| DraStic
| [http://repo.openpandora.org/?page=detail&app=DraStic repo]
| {{No}}
| {{No}}
| No method found yet for using external controllers
|-
| PanMAME
| [http://repo.openpandora.org/?page=detail&app=panmame-advmenu-7927 repo]
| {{Yes}}
| n/a
|
|-
| SNES9x EX+
| [http://repo.openpandora.org/?page=detail&app=com.explusalpha.Snes9xPlus repo]
| {{Yes}}
| n/a
| Custom key maps work great. Make sure to use the linked version of the PND. Other versions in the Repo suffer from crashes when external controllers are set up.
|-
| Not Tetris
| [http://repo.openpandora.org/?page=detail&app=nottetris_ptitseb repo]
| {{No}}
| {{Yes}}
| QJoyPad works fine. Map Escape and Enter to help with pausing and selections.
|-
| Flying Snake
| [http://repo.openpandora.org/?page=detail&app=flyingsnake_undexsym repo]
| {{No}}
| {{Yes}}
| QJoyPad works fine. Map Start to help you begin a new round.
|-
| Mini Slug Project
| [http://repo.openpandora.org/?page=detail&app=minislug_ptitseb repo]
| {{Maybe | Works with issues}}
| {{No}}
| Game auto maps the OUYA controller fine, but maps the directional to the left stick. Have not found a way to use the D-Pad. QJoyPad is ignored.
|-
| Mupen64plus v2.1
| [http://repo.openpandora.org/?page=detail&app=mupen64plus repo]
| {{Yes}}
| n/a
| If your controller is not already supported, it can be mapped by editing InputAutoConfig.ini - OUYA controllers and Mayflash GameCube-to-USB can be mapped and auto-detected using the following [https://drive.google.com/file/d/0B7nHCkhKNgw3cXhNVlc0WldGSUk/view?usp=sharing InputAutoCfg.ini]
|}

[[Category:Tutorials]]
[[Category:Bluetooth]]
[[Category:Keyboard]]

Reicast Compatibility List

2013-12-29T06:18:11Z

Edgex004: /* The Compatibility List */

Reicast is a SEGA Dreamcast Emulator ported on Pandora by PtitSeb. Other versions exist [http://reicast.com/ (Linux|GNU, Android, Windows, Mac..)]

Current version available is VERY alpha. You can download it [http://boards.openpandora.org/index.php?app=core&module=attach&section=attach&attach_id=8058 here]. (will probably be updated often).

==Adding to the Compatibility List==
Choose a playability color that reflects a game's best playability state. Also include the clockspeed at which you ran it, for whichever Pandora version you tested. Please also indicate in the name of the Game whether the version is US/EU/JP, since compatibility may differ depending on regions. You may also add specific conditions you specified in the settings if they differ from the defaults. As for the SGX driver, please write "default" if you did not change your driver vs what was in the firmware.

Don't post a redundant entry unless you are using a different Pandora model and the playability differs from an existing entry. If a game's playability gets worse (new bugs, new crashes) in a new Reicast version, update the entry and add that to notes.

{|class="wikitable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: left;"
|- style="background: #ececec; text-align: center;"
!Playability
!Description
|- style="background: #90FF90"
|Fullspeed
|Games with a '''green''' background run at fullspeed and are fully playable from start to finish. If frameskip is required, add to notes.
|- style="background: #F3F781"
|Playable
|Games with a '''yellow''' background run slower than fullspeed, but are otherwise fully playable. Add problems/slowdowns to notes.
|- style="background: #F7BE81"
|Incomplete
|Games with an '''orange''' background have playability issues and cannot be played from start to finish. This may include missing functionality (wifi) or game crashes. Add problems to notes.
|- style="background: #F78181"
|Unplayable
|Games with a '''red''' background are unplayable. They either don't run at all, or don't get past the intro. Add any other oddities to notes.
|-
|N/A
|Games with a '''white''' background have not been fully tested. If you see one on this list, try it out and report back!
|}
If you are inclined, post your forum username at the end of your notes so you can be contacted by PtitSeb about further debugging your problems.

==The Compatibility List==


You can sort the columns by clicking the table header (javascript required).

{|class="wikitable sortable" border="1" cellpadding="1" cellspacing="0" style="font-size: 90%; border:1px solid gray; border-collapse: collapse; text-align: center; width: 100%;"
|- style="background: #ececec"
! Game Name and Region
! Reicast Version
! Pandora Model<sup>[1]</sup>
! SGX driver
! SZ version

! Frequency
! Notes on Settings
! Status

|- style="background: #90FF90"
|Incoming (US)
|Alpha
|1GHz
|4.10.00.01
|1.60
|1000 Mhz
|Runs full speed most over the time, there are several slowdowns during the campaign while facing the camera into a specific direction, but still doable. (Played for 30 Phases/Sections of the Campaign)
|Green

|- style="background: #90FF90"
|Expendable (US)
|Alpha
|1GHz
|4.10.00.01
|1.60
|1200 Mhz
|Runs at about 95-100% of game speed, the sound starts to stutter a bit sometimes, if there are too many effects and particles shown on the screen.
|Green

|- style="background: #F3F781"
|Soul Calibur (JP)
|Alpha
|1GHz
|4.03.00.02
|1.55
|1000 Mhz
|Slower than fullspeed (probably 60% of actual speed), while completely playable, and devoid of glitches on screen.
|Yellow

|- style="background: #F3F781"
|Sakura Taisen (JP)
|Alpha
|1GHz
|4.03.00.02
|1.55
|1000 Mhz
|Very slow in videos, but in-game the speed is correct and sound stutters only once in while. Playable. Note that the characters' pictures in dialogs in glitchy, somehow.
|Yellow

|- style="background: #F3F781"
|Legacy of Kain: Soul Reaver (US)
|Alpha
|1GHz
|Default
|1.55
|1000 Mhz
|Cutscenes are glitchy and gameplay audio is scratchy at random points but game ranges from slow to very playable depending on your device.
|Yellow

|- style="background: #F3F781"
|Flag To Flag (EU)
|Alpha
|1GHz
|Default
|Default
|1000 Mhz
|Slightly slower than fullspeed but very playable. Sound is very glitchy though and only graphical glitches noted on screen were the cars mirrors [I'd consider this a minor] [FZERO].
|Yellow

|- style="background: #F3F781"
|Trickstyle (US)
|Alpha
|1GHz
|4.10.00.01
|1.60
|1200 Mhz
|Training runs at about 90-100 % of speed, sound stuttering sometimes. Racing runs at about 60%-80% of speed with sound stuttering all the time.
|Yellow

|- style="background: #F3F781"
|Virtua Tennis (US)
|Alpha
|1GHz
|4.10.00.01
|1.60
|1200 Mhz
|Runs at about 60-70% of game speed, the sound is stuttering all the time. But somehow it is still playable.
|Yellow

|- style="background: #F3F781"
|Dead or Alive 2 (US)
|Alpha
|1GHz
|4.10.00.01
|1.60
|1200 Mhz
|Runs at about 60-70% of game speed, the sound is stuttering all the time.
|Yellow

|- style="background: #F3F781"
|Silver (US)
|Alpha
|1Ghz
|4.10.00.01
|1.60
|1200 Mhz
|80-90% of game speed, but very stuttering sound.
|Yellow

|- style="background: #F3F781"
|Unreal Tournament (US)
|Alpha
|1GHz
|4.10.00.01
|1.60
|1200 Mhz
|Runs at about 50-60% of game speed depending on view direction, the sound is stuttering all the time. Sometimes single textures are flickering a bit.
|Yellow

|- style="background: #F3F781"
|Sonic Adventure
|Alpha
|1GHz
|4.10.00.01
|1.60
|1100 Mhz
|Speed fluctuates between 80-100%. Many dropped frames and sound stuttering. Some areas, such as Chao garden, have no stuttering or dropped frames. No crashes yet. Increasing clock to 1200 Mhz seems to help.
|Yellow

|- style="background: #F7BE81"
|Re-Volt (US)
|Alpha
|1GHz
|4.10.00.01
|1.60
|1200 Mhz
|Runs at 90-100% of speed, the sound is stuttering sometimes. BUT menus are missing.
|Orange

|- style="background: #F7BE81"
|MDK 2 (US)
|Alpha
|1GHz
|4.10.00.01
|1.60
|1200 Mhz
|Runs at almost fullspeed, the sound is quite stable. BUT the sniper mode does not function correct. Aiming is impossible due to a texture problem.
|Orange

|- style="background: #F7BE81"
|StarWars - Episode 1 - Racer (US)
|Alpha
|1GHz
|4.10.00.01
|1.60
|1200 Mhz
|Runs at about 70-80% of game speed, the sound is a whole mess. But the racing itself is quite playable. Movie sequences have stuttering sound
|Orange

|- style="background: #F7BE81"
|Marvel VS Capcom 2 (US)
|Alpha
|1GHz
|4.03.00.02
|1.55
|1000 Mhz
|Works well in the menus, and the speed in-game is reasonable, but the characters in 2D are completely glitchy and it makes it unplayable at this stage. Sound stutters too once in a while.
|Orange

|- style="background: #F7BE81"
|Chu Chu Rocket (JP)
|Alpha
|1GHz
|4.03.00.02
|1.55
|1000 Mhz
|Works full speed most of the time with very little stuttering, but in levels when mice are getting out like crazy with tons of them on screen, it becomes unplayable and freezes.
|Orange

|- style="background: #F7BE81"
|Capcom VS SNK 2 (US)
|Alpha
|1GHz
|4.03.00.02
|1.55
|1000 Mhz
|Works well in the menus, and the speed in-game is reasonable, but the characters in 2D are completely glitchy and it makes it unplayable at this stage. Sound stutters too once in a while.
|Orange

|- style="background: #F7BE81"
|Capcom VS SNK 2 (US)
|Alpha
|1GHz
|4.03.00.02
|1.55
|1000 Mhz
|Works well in the menus, and the speed in-game is reasonable, but the characters in 2D are completely glitchy and it makes it unplayable at this stage. Sound stutters too once in a while.
|Orange

|- style="background: #F7BE81"
|Crazy Taxi
|Alpha
|Classic
|Default
|Default
|1000 Mhz
|Menus are full speed with good sound. In game is just playable, but only about 3 frames a second. Other cars have no textures except wheels. (Gruntfuggly)
|Orange

|- style="background: #F7BE81"
|Sonic Adventure (US)
|Alpha
|Classic
|4.04.00.03
|1.55
|900 Mhz
|Menu's mostly black but you can get around and runs at decent speeds. In game though, very few textures load and it's pretty slow. Game crashes after the first fight with Chaos.
|Orange

|- style="background: #F7BE81"
|Ikaruga (JP)
|Alpha
|1GHz
|4.03.00.02
|1.55
|1000 Mhz
|Very slow in certain cinematics (slideshow), faster in actual game, but sometimes the bullets don't even appear and some animations are glitchy. Promising, but not really playable at this stage because of these issues.
|Orange

|- style="background: #F7BE81"
|Soldier of Fortune (US)
|Alpha
|1Ghz
|4.10.00.01
|1.60
|1200 Mhz
|Very slow Gameplay. Sound glitching all the time.
|Orange

|- style="background: #F7BE81"
|Virtua Fighter 3tb (US)
|Alpha
|1Ghz
|4.10.00.01
|1.60
|1200 Mhz
|Runs at about 70 % of speed, but with graphical issues, parts of the bodies arent shown correct. Sound stuttering.
|Orange

|- style="background: #F78181"
|The House of the Dead 2 (US & EU)
|Alpha
|Classic
|Default
|1.55
|1000 Mhz
|Crashes at Start.
|Red

|- style="background: #F78181"
|South Park Rally (US)
|Alpha
|Classic
|Default
|1.55
|1000 Mhz
|Hangs on white screen after BIOs for about 1 minute, then you can hear the music of the game but the screen is still white and frozen.
|Red

|- style="background: #F78181"
|Sega Rally 2 (US)
|Alpha
|1GHz
|4.03.00.02
|1.55
|1000 Mhz
|Crashes at Start.
|Red

|- style="background: #F78181"
|Skies of Arcadia (US)
|Alpha
|Classic
|Default
|1.55
|1000 Mhz
|Crashes at start.
|Red

|- style="background: #F78181"
|Resident Evil 2 (US)
|Alpha
|1GHz
|4.03.00.02
|1.55
|1000 Mhz
|Crashes at Start.
|Red

|- style="background: #F78181"
|Frogger 2: Swampy's Revenge (US)
|Alpha
|Classic
|4.04.00.03
|1.55
|900 Mhz
|Hangs on white screen after BIOs.
|Red