I’m in the process of doing the exact same thing, don’t suppose you have any links for the lcd controller board? I can’t find any with USB ports on them, and like the idea of running the whole thing off one power import.

Ok, now try

“sudo lsusb -D /dev/bus/usb/001/005″

and look for the iProduct value.

And can you screenshot the jstest output as well?

To test the principle lets just try the buttons first.

whats your output when you type lsusb ?

Here is an example file that should be placed here:
/opt/retropie/configs/all/retroarch-joypads

http://pastebin.com/raw.php?i=vYP9xSeF

You can get the input_device value by looking at the “iproduct” value.
use “lsusb -v”
Or for a specific device, like this
“sudo lsusb -D /dev/bus/usb/001/004”

because mine is the 4th device on the usb bus

Anyway… not sure if it will work but you can try.

Does the jstest output tell you the button mappings?

Is it like this?
http://www.instructables.com/id/SNES-Teensy-USBPS3-Gamepad/

I’m going to look at mine soon (although mine are MadCatz Arcade SE and TE).
I have to get the internals swapped out (although its fine in my PC if I use a VIA USB chipset).
I’m not sure if the Qanba has the same issue. Does it work fine in your PC?

I’m having almost this exact problem. I’m on Retropie 3 – Beta 2. The Auto Remapping feature is fantastic, yet it is not perfect. I’d like some more control.

I’m using a PS3 Bluetooth controller as my main controller for the system. For the NES console, Button A (NES) is “Circle” on the PS3 Controller and Button B (NES) is “X” on the PS3 Controller. To me this feels awkward, and I’d rather have the buttons shifted one button over to this: Button A (NES) is “X” (PS3), and Button B (NES) is “Square” (PS3).

To simplify… This is what I currently have:
NES A = PS3 Circle
NES B = PS3 X

And this is what I want to have:
NES A = PS3 X
NES B = PS3 Square

I know that I can do this fairly simply by adding a few lines into the NES config file (iaaberg, this may help you), found at “\opt\retropie\configs\nes\retroarch.cfg”. I can just add the following:

input_player1_a_btn = "14"
input_player1_b_btn = "15"
input_player2_a_btn = "14"
input_player2_b_btn = "15"

However, this breaks the remapping feature, because now any different controllers I connect to the RetroPie will take those button mappings, overriding the Auto Config. This makes the fix above kind of useless.

I wish instead I could modify how the NES emulator takes the inputs. I wish I could do something like:

NES_input_a_btn = input_b_btn
NES_input_b_btn = input_y_btn

That might get a little complicated, but the principle is simple. There’s a variable for the specific controller input, there’s a variable for the input of the emulator, so there should be a bridge of some sort in between where you can dynamically mix and match the variables to your liking. This way, the dynamic remapping feature stays intact, but the user still has freedom to make changes like I just stated.

For a little more info, here’s the full story. I have a PS3 Bluetooth controller, and a PS2 controller connected via PSX-to-USB adapter. If my Bluetooth controller runs out of battery, I use the PS2 controller. But if I want to play a NES game, I can’t, because the two controllers have different internal button mappings, like so:

PS3 Face Button ID’s:
Triangle = 12
Circle = 13
X = 14
Square = 15

PS2 (via Adapter) Face Button ID’s:
Triangle = 0
Circle = 1
X = 2
Square = 3

If I hardcode a change to the NES configs, it won’t be usable for both controllers. Does anyone know of a way to get the correct result as I described?

[quote=100876]I also am using a Dualshock 4 (PS4) controller, and had the same issue, but I finally found out a solution!

After looking through some of the setup options, one of the options was Install Retroarch autoconfigs (or something like that, it was very similar). I decided to just give it a whirl and install this, and it ended up working! I rebooted my Pi, went into Super Mario World for SNES and it worked perfectly.

Also tested on The Legend of Zelda Minish Cap for GBA. Works fine! I hope this helps!

I did not have to go back in and configure the controller manually after this. I just rebooted my Pi and it was already configured correctly.

[/quote]

Thanks for the help, Falcon! :D
For anyone that couldn’t find the option, it’s located at:

Retropie menu, retropie-setup
"setup/config (to be used post install)"
[Option 318] "Install Retroarch joypad config"

Now the joypad almost works!

What I find peculiar is that now I have 3 dragonrise cfgs:

DragonRise_Inc.___Generic___USB__Joystick__.cfg
DragonRise_Inc.___Generic___USB__Joystick__.bak

(these ones where created “manually” while trying to setup before)

DragonRise_Inc._Gamepad.cfg
and
DragonRiseInc.GenericUSBJoystick.cfg
(these where download automatically, and are almost empty. The GenericUSB one only have “input_driver = “udev”)

And Retroarch is reading… That one the I created before! Very weird.
I’m sure of that, because I placed the code to go back to the ES menu pressing select+start, reset emulator, etc, inside this one, and he can understand that.

But I still can’t make my analogs work. Here is the analog part of the code (auto-generated by the retroarch joy config before):

[...]
input_l3_btn = "10"
input_r3_btn = "11"
input_l_x_plus_axis = "+0"
input_l_x_minus_axis = "-0"
input_l_y_plus_axis = "+1"
input_l_y_minus_axis = "-1"
input_r_x_plus_axis = "+3"
input_r_x_minus_axis = "-3"
input_r_y_plus_axis = "+4"
input_r_y_minus_axis = "-4"

Again, I tried to place it inside each of dragon’s cfgs, placing it inside “\\RETROPIE\configs\all\retroarch.cfg”, “\\RETROPIE\configs\psx\retroarch.cfg”, etc

I’m starting to think that this code have something wrong, but I can’t really understand what :o Maybe the axis notation?

I’ll keep trying to figure out what is the problem, but any help is appreciated :)

[EDIT]
I discovered how! :D Thanks to this video from TechTipsta:

His video is more indepth, configuring the .cfgs using a usb keyboard, directly on the Raspy. But you can do all using a wifi dongle, and sharing your config files via samba (already comes preconfigurated, at least in this version of retropie [v.3.0, beta 4])

First, you need o configure 2 Retroarch specific buttons: one to toggle the hotkeys, another one to bring the retroarch config menu.
On the video, he used select + f1 (the f1 is already on the “\\RETROPIE\configs\all\retroarch.cfg”, but it’s commented by default; you just need to open it, and uncomment the line, deleting the “#” in front of it), but you can use any button from your controller. can use any button you wish.

In my case, I used the select + the equivalent of the triangle button on my generic controller. This code goes inside your gamepad cfg, located in

\\RETROPIE\configs\all\retroarch-joypads\[yourjoypadname].cfg

I’m my case, the code is:

input_enable_hotkey_btn = "8"
input_menu_toggle_btn = "0"

After that, you just start the psx emulator, push your enable_hotkey button, the input_menu button, and voilá, you should bring up the retroarch menu.

Now, you should be able to use your keyboard or your joypad to navigate thru the menus. But when I tried to use the joypad, the menus goes ballistic, and I can’t select anything. So, keep your keyboard with you, just in case! You are looking to go to:

options> core options> pad1 type

Change the pads type from STANDARD to ANALOG

Now just go back 1 menu, select “resume content”, and you are done! :D
I still have to test if this config “sticks” after shutting down the PI, and this menu have many more options to mess. I’ll edit this post in the case that I find something important! :D

Ops, it doesn’t stick. That’s what I get for skipping the video :/

After changing from standard to analog inside the core options, go back to settings > Input settings, and change “User1 Devicetype” from Retropad to Retropad w/ analog

Go back to the “root” menu, and choose “Save New Config”
It will change the “configuration files” above from retroarch.cfg to libretro.cfg. Everytime you save it again, it creates a new file (libretro-1.cfg, 2, 3, etc).

After that, exit the emulator, press f4 on your keyboar to reset the Retropie. On the command line, we will append the libretro config file to the retroarch one, so it (theoretically) load the settings everytime.

(Via samba, you can just open the 2 files, and ctrl+c, ctrl+v the settings from inside the libretro file to the retroarch one, but let’s do it the “clean” way)

Type in the command line

cd /opt/retropie/configs/psx
(in the video, the path is …/configs/all; i think it changed since them, because retroarch saved everything inside the psx folder)

Now type ls; You’ll see all the files on this directory, including the newly created libretro.cfg. To append it to the retroarch.cfg, just type

cat libretro.cfg >> /opt/retropie/configs/psx/retroarch.cfg

Theoretically, Retroarch should read this, and autoset the analog everytime. But isn’t working yet, I still need to manually change to analog everytime I restart the emulator :/

I’ll keep messing with it, but as I said before, any help or hint is appreciated :D

[quote=100854]Just got my raspberry pi today and I am having this issue as well, but it seems to be with all emulators (I have only tested NES/SNES so far though). Dpad is not working in any of the games I have tried, but the other buttons seem to be ok. When setting the controller up in the settings, all of the buttons seem to be recognized, except when I press the L2 button it adds it as L2 and R2 in the config settings as soon as I press it. But the main issue is that the dpad isn’t working; it’s unplayable without that.

I am using the Dual Shock 4 / PS4 controller with a USB cable if that matters.

[/quote]

I’m not using a ps4 controller, but I’m having the same problem here. Changed from Lakka to Retropie and EmulationStation today, and I can’t figure out what the problem is, for the life of me :o

My usb keyboard works fine, but the dpad and analogs just doesn’t work.
I used jtest to see the inputs, used the new autoconfig via the ES menu, tried to setup the retroarch cfg manually, placing copies inside the “\config\[emulator]”, placing the controller config inside “\config\[emulator]\retroarch.cfg”… Still nothing. Tested Super Mario All-stars, A Link to The Past (snes), SuperMarioland (gb), castlevania (nes) and CTR (psone)
(btw, I can control the games using the keyboard and the joypad at the same time.)

I’m using the Version 3.0 BETA 4 (retropie-v3.0beta4-rpi2.img.gz), and this is my joypad config inside “\\RETROPIE\configs\all\retroarch.cfg”:

input_device = "DragonRise Inc.   Generic   USB  Joystick  "
input_driver = "udev"
input_b_btn = "2"
input_y_btn = "3"
input_select_btn = "8"
input_start_btn = "9"

input_up_btn = "h0up"
input_down_btn = "h0down"
input_left_btn = "h0left"
input_right_btn = "h0right"

input_a_btn = "1"
input_x_btn = "0"
input_l_btn = "4"
input_r_btn = "5"
input_l2_btn = "6"
input_r2_btn = "7"
input_l3_btn = "10"
input_r3_btn = "11"
input_l_x_plus_axis = "+0"
input_l_x_minus_axis = "-0"
input_l_y_plus_axis = "+1"
input_l_y_minus_axis = "-1"
input_r_x_plus_axis = "+2"
input_r_x_minus_axis = "-2"
input_r_y_plus_axis = "+3"
input_r_y_minus_axis = "-3"
input_enable_hotkey_btn = "8"
input_exit_emulator_btn = "9"
input_menu_toggle_btn = "0"
input_load_state_btn = "4"
input_save_state_btn = "5"
input_reset_btn = "2"
input_state_slot_increase_btn = "h0right"
input_state_slot_decrease_btn = "h0left"

Any help?

Strange things, i dont even know where to start, but i will drop RetroPie until it will be 3.0 Stable.

It looks like via usb cable – pad works, if i want to pair it via BT – it gets paired ok but it wont work in emustation or in games.

ok, edit:

just found ./retroarch-joyconfig did whole config via BT and pad works it was paired but somekind emustation cant see those configs

So basically you want the sound outputted to a bluetooth speaker, rather than through a TV or PC/USB speakers?

Just got my raspberry pi today and I am having this issue as well, but it seems to be with all emulators (I have only tested NES/SNES so far though). Dpad is not working in any of the games I have tried, but the other buttons seem to be ok. When setting the controller up in the settings, all of the buttons seem to be recognized, except when I press the L2 button it adds it as L2 and R2 in the config settings as soon as I press it. But the main issue is that the dpad isn’t working; it’s unplayable without that.

I am using the Dual Shock 4 / PS4 controller with a USB cable if that matters.

Just installed the Pi2 image to an SD card and played around with it. Couple of strange new issues since beta 2 (haven’t tried beta 3) with controller setup for Xbox 360 Wired USB Controllers.

Not only is setting it up problematic (strange sticking issues on Left bottom buttons, when pressed it begins trying to skip it and it cannot be stopped. Tested on two usb Xbox controllers) but worst of all.. even with the d-pad set up, games no longer recognise it. Tested in a NES game, it’s no longer possible to move. A, B, Start etc all work fine, but neither the d-pad or configured analogue sticks will move.

While I love the idea of sharing the configure imput of the gui with the retroarch configs, it seems to have broken USB Xbox controller imput.

After much testing with the emulator over the past few days, I have yet to figure out the dpad issues with the wireless xbox 360 controller. I know I can add the line d pad as button in xbxdrv but doing so would require me to remap all of the other emulators controls which isn’t going to happen. it appears that reicast isn’t set up to read the dpad as an axis, but whats crazy is, as noted above I have the dpad mapped to the axis that it is listing in jstest, and the Dpad_Right is working in-game, so that being considered, I might just need to play around with some of the other axis numbers and might stumble across the other directional mappings. Here’s hoping….

Bugreport

As far as bugs, I believe I have also found a bug in regards to the Wireless Xbox 360 controller. This only happens in Reicast and not in any other emu nor emulation station. After restarting the system, and loading a game with the emulator, the emu appears to load the wrong controller config sometimes. What I mean by that is, I have 2 wireless xbox 360 controllers registered with retropie. And at first I thought Reicast wasn’t picking up any controllers, despite my 360 controller working fine in ES and other emus after reboot. But I noticed when I loaded a 2 player game, that it was indeed picking up the controller, but it was picking up as player 2, not player 1, despite the xbox light showing it as the first player controller. After exiting the emu and switching usb ports (sometimes having to try a few different ports) the emulator will then pick up the xbox 360 controller correctly as player one and work fine from that point on, until another reboot of the pi. Not sure what’s going on with Reicast, but this bug only happens with this emulator and no others. Something definitely needs to be looked at here.

I have also tested quite a few games thus far, and wanted to give updates on performance on these on the latest version of Reicast. Overall, most games I have tested work near perfect or near full speed with only minor graphic gltiches… Sound on the other hand in most games is really choppy. But considering the games them selfs are running almost perfectly, this really appears to me that the pi has plenty of power to run DC games at full speed and just needs some audio fixes to get these titles nearly perfect! Here is the list of games I have tested so far, hope this helps some, and I will be updating these in the future as I test more titles.

Games Tested

Sonic Adventure

After playing the first few levels, both the sound and graphics are nearly perfect with only a few very minor graphic glitches here and there. The game runs at pretty much full speed and it’s one of the few games that I have tested so far where the audio is also nearly perfect!

Soul Calibur

Game is now running at pretty much full speed on the latest version of Reicast. There is some slight slow down when doing some of the “charging” effects but other than that the game runs at close to full speed if not full speed most of the time. There are a few minor graphic glitches here and there, but nothing major at this point and the game is now fully playable. Audio on the other hand is very choppy and quite bad.

Legacy of Kain – Soul Reaver

Another game where so far it runs at pretty much full speed with only minor graphic glitches and is fully playable. Slight slow down during some of the “soul sucking” particle effects but nothing major. Audio is choppy but not as bad as other titles like Soul Calibur.

Draconus – Cult of the Wyrm Disc 1

Boots and loads into game, but heavy slow down making it basicly unplayable. Sky box is also pink, but this is a known bug in the PC dreamcast emulators as well.

Power Stone 2

Boots fine and sound is perfect in the menus and stage intros… Once game loads sound gets super choppy and is very bad. Also game is currently not running at full speed and gets a fair amount of slow down, at least with 4 players on the screen (me and 3 AI). Game would be considered playable, but not much fun in it’s current state.

Street Fighter 3 3rd Strike

Game boots fine but has some graphic glitches in the menus but still mostly navigable. Character sprites and some parts of the back ground have major graphical glitches, though mostly on the players, and currently making the game unplayable due to this. The game does however appear to run at full speed.

Dead or Alive 2

Boots to DC logo and then locks up the pi.

Metropolis Street Racer

Fully playable, runs at full speed, very minor graphical glitches on some of the tracks, pretty much looks perfect! Audio is also perfect! Plays great!

Hope this helps some, just need to figure out the dpad issues with the 360 controller and solve the I/O bug and hopefully audio fixes will come soon enough. So far I am blown away by how playable these games are, most work at near full speed and just need audio fixes and they will be perfect! I will update the games tested list as I make more progress with the system.

usb keyboards are very cheap though – handy to have a wireless one available rather than having to do everything remotely.