OLD Gamepad Autoconfig Thread

RetroArch Android devices
#101

I checked over at XDA developers to see if anyone else was having issues with the iPega d-pad in retroarch. A couple of others are, and one person suggests that it was previously working before they upgraded to Android 4.2.2. I also tried the iPega in a few more modes. The dpad works once and only once in iCade or keyboard mode - retroarch responds to a single dpad input, then no longer responds at all.

If both up on the joystick and up on the dpad are mapped as DPAD_UP, is there any way to configure retroarch to listen for inputs from both? Currently only inputs from the joystick actually get executed in a game (although both work in the retroarch settings menu).

#102

im sorry but your implementation for the steelseries free doesn’t work. bluez ime was able to get everything working with these, would be wonderful if you could do the same for retroarch:

DPAD Up: D/DataDumpReader(25976): Read data: 08 a1 1c 04 fe fe fe fe fe DPAD Down: D/DataDumpReader(25976): Read data: 08 a1 1c 05 fe fe fe fe fe DPAD Left: D/DataDumpReader(25976): Read data: 08 a1 1c 06 fe fe fe fe fe DPAD Right: D/DataDumpReader(25976): Read data: 08 a1 1c 07 fe fe fe fe fe Button 1: D/DataDumpReader(25976): Read data: 08 a1 07 02 fe fe fe fe fe Button 2: D/DataDumpReader(25976): Read data: 08 a1 07 03 fe fe fe fe fe Button 3: D/DataDumpReader(25976): Read data: 08 a1 07 01 fe fe fe fe fe Button 4: D/DataDumpReader(25976): Read data: 08 a1 07 00 fe fe fe fe fe L Trigger: D/DataDumpReader(25976): Read data: 08 a1 1c 08 fe fe fe fe fe R Trigger: D/DataDumpReader(25976): Read data: 08 a1 1c 09 fe fe fe fe fe A Button: D/DataDumpReader(25976): Read data: 08 a1 1c 0b fe fe fe fe fe B Button: D/DataDumpReader(25976): Read data: 08 a1 1c 0a fe fe fe fe fe

Each release of a button ended up with: 4th hex number going to fe

Still figuring out the sticks, this is what I think so far. Sample output: Left Stick: D/DataDumpReader(25976): Read data: 05 a1 08 00 00 fd Right Stick: D/DataDumpReader(25976): Read data: 05 a1 08 01 00 c0

https://code.google.com/p/android-bluez-ime/issues/detail?id=192#c12

thanks <3

#103

does it support HID 12: Microntek USB Joys?

the weird is Pad 0:190,ac=0src=1281 Pad 0: x=-0.00,y= -0.00 src 16777

Plz help me ><

Why it doesn’t have respond?

#104

You need to provide me with the HID name that it reports. See the steps in the OP.

#105

You need to report all the keycodes. Those are not all the buttons - not by far.

#106

sorry the only thing it write is this i didnt see other word except than this

#107

You need to press every button on the pad, see what ‘keycode’ it shows onscreen and then report those to me (per button).

#108

You need to press every button on the pad, see what ‘keycode’ it shows onscreen and then report those to me (per button).[/quote]

sorry as i say it didn’t show anything (press all the button)except the one i show you

#109

hi ,I use retroarch on my tablet DEA myplay but only 4 buttons do not work above it knobs are square, cross, L and R for square: pad 0 : 53, ac= 0, src = 257 for cross : pad 0 : 30, ac = 0, src = 257 for L1 : pad 0 : 30 , ac = 0 , src = 257 for R1: pad 0: 46,ac = 0 , src = 257 for select: pad 0 :47, ac = 0 , src = 257 very thanks for your job

#110

You need to press every button on the pad, see what ‘keycode’ it shows onscreen and then report those to me (per button).[/quote]

sorry as i say it didn’t show anything (press all the button)except the one i show you[/quote]

does it support HID 12: Microntek USB Joys?

the weird is Pad 0:190,ac=0src=1281 Pad 0: x=-0.00,y= -0.00 src 16777

I can’ t do anything with this - sorry. You don’t even mention which button 190 belongs to for example.

Come back to me when you have something more complete - look at how the others in the previous pages reported keycodes.

#111

I also need you to report the name to me that it reports -

it should read something like -

HID 12: Microntek USB

The number and the name there will be different for your tablet. You need to tell me exactly what it says there - case-sensitive.

#112

the hid is : hid 2 sun4i-ir,p:0 and is ok , I managed to set up all the key all button run with retroarch

#113

I’ve got two of the stick pictured above- both give different codes- I believe one is sold as PC USB version, and one as Xbox 360 version.

Here goes:

HID 13: Datel Arcade Stick, p: 0. Button / Data Displayed 1 / Nothing displayed 2 / 104 ac=0 src=1281 3 / 110 ac=0 src=1281 4 / 105 ac=0 src=1281 a / 100 ac=0 src=1281 b / 96 ac=0 src=1281 c / 99 ac=0 src=1281 d / 101 ac=0 src=1281 e / 102 ac=0 src=1281 f / 97 ac=0 src=1281 g / 98 ac=0 src=1281 h / 103 ac=0 src=1281 up x=0, y=0 right up x=0, y=0 down up x=0, y=0 left up x=0, y=0

HID 12 Microsoft X-Box 360 pad, p:0 Button / Data Displayed 1 / No Data Displayed 2 / 109 ac=0 src=1281 3 / 110 ac=0 src=1281 4 / 108 ac=0 src=1281 a / 102 ac=0 src=1281 b / 99 ac=0 src=1281 c / 100 ac=0 src=1281 d / 103 ac=0 src=1281 e / x=0, y=0 f / 96 ac=0 src=1281 g / 97 ac=0 src=1281 h / x=0, y=0 up / x=0, y=0 right / x=0, y=0 down / x=0, y=0 left / x=0, y=0

Much like post 101 the directions map ok as DPAD UP, DPAD RIGHT etc when binding by hand, but fail to react ingame, I guess they are reacting as the wrong xbox stick as far as Retroarch is concerned. Both pads work fine in android afaik - have mapped all buttons correctly in ‘Onlive’ games for example…

#114

OK - so the details for Madcatz Street Fighter IV Fight Pad HID 12: Generic X-Box Pad, p:0 Button Name / Data Displayed x / 99 y / 100 rb / 103 a / 96 b / 97 rt / x=0, y=0 lb / 102 lt / x=0, y=0 turbo / No Data Displayed back / 109 x-box button / 110 start / 108

Pad (with selector on LS setting) Up / x 0 Y-1 right / x 1 y 0 Down / x 0 y 1 left / x -1 y 0

Pad (with selector on DP setting) Up / x 0 Y 0 right / x 0 y 0 Down / x 0 y 0 left / x 0 y 0

Pad (with selector on RS setting) Up / x 0 Y 0 right / x 0 y 0 Down / x 0 y 0 left / x 0 y 0

#115

Sorry if the question is already out there in this forum, but I’ve not found answer to may questions…

I’ve got an iPega bluetooth controller and I tried to use it with RetroArch on my TF300 tablet (android 4.1.2, not the new 4.2.1 coming soon).

I don’t understand how to setup the controller to work with RetroArch. The manual is not so easy for me to understand: RetraArch support ipega natively or an IME is necessary? The only one i SixAxis? Nothing free? In wich mode the ipega must be start to work? iCade, mouse, keyboard or joystick mode?

Many thanks for answers!

#116

Could you please add the JXD S7300B (http://www.jxd.hk/products.asp?id=627&selectclassid=009006) ?

HID 6: adc joystick, p: 0.

left joystick up: Pad 0 : 19, ac = 0, src = 1281 left joystick down: Pad 0 : 20, ac = 0, src = 1281 left joystick left: Pad 0 : 21, ac = 0, src = 1281 left joystick right: Pad 0 : 22, ac = 0, src = 1281

right joystick up: Pad 0 : 37, ac = 0, src = 1281 right joystick down: Pad 0 : 39, ac = 0, src = 1281 right joystick left: Pad 0 : 38, ac = 0, src = 1281 right joystick right: Pad 0 : 40, ac = 0, src = 1281

X: Pad 0 : 99, ac = 0, src = 1281 y: Pad 0 : 100, ac = 0, src = 1281 a: Pad 0 : 96, ac = 0, src = 1281 b: Pad 0 : 97, ac = 0, src = 1281

start: Pad 0 : 66, ac = 0, src = 1281 select: Pad 0 : 62, ac = 0, src = 1281

R1: Pad 0 : 103, ac = 0, src = 1281 R2: Pad 0 : 105, ac = 0, src = 1281

L1: Pad 0 : 102, ac = 0, src = 1281 L2: Pad 0 : 104, ac = 0, src = 1281

Many Thanks!

#117

Please add support for “Twin USB Joystick”. The codes are the same of thrust predator.

Thanks

#118

Just wondering if there has been any progress on the xbox 360 controllers diagonal problem? Thanks in advance for any response.

#119

I can’t debug the issue because I only have two wireless 360 gamepads and no wireless receiver - ie. it only works on 360.

#120

I don’t know if there is, but if there is anything I could do to help I will. I have a wired 360 controller.