OLD Gamepad Autoconfig Thread

RetroArch Android devices
#81

Just added a new item into my collection: NEOGEOX Arcade Stick (for the shameless rip-off that is the NeoGeo X). It is a standard USB HID device, works on Windows, Linux, Android menus etc…

HID : “TOMMO NEOGEOX Arcade Stick” A 96 B 97 C 99 D 98

Start: 105 Select: 105

Stick: x=0.00 y=0.00 on all directions. Manual input detector sees it as DPAD UP/DOWN/LEFT/RIGHT but Windows says it’s a POV Hat.

Probably best to have it match the original NeoGeo layout button for button so: RetroPad A is NeoGeo B RetroPad B is NeoGeo A RetroPad X is NeoGeo D RetroPad Y is NeoGeo C

#82

Start and Select are the same. Are you sure about this?

For the stick I’ll try implementing it as DPAD_UP/DPAD_DOWN/DPAD_LEFT/DPAD_RIGHT.

Can you compile from source? This could help in testing it before release (probably later this week).

#83

[quote=“bluemonkey”]

Ok, got my phone now. But I’m a bit stuck right now.

What are the correct steps to test the controller? I turn on bluetooth on android (ICS), turn on the icontrolpad in Joystick mode, pair it. Then launch retroarch, select input method but I cannot see the icontrolpad at all.

Don’t really know what to do next. Can somebody help, please?

UPDATE:

Ok, I have paired successfully the ICP to android, and it detects it as an input device. I can even navigate through the menus using the controller. Launched a game with retroarch and I can see the button mappings in a yellow font whenever I press a button. But they wont work for gameplay.

The mappings are detected as follows:

UP 188 LEFT 190 DOWN 191 RIGHT 189 Y 198 A 199 X 200 B 201 SEL 196 START 197 L 192 R 202 LEFT ANALOG x

The right analog is not detected.

I think I should be able to select the icontrol pad from the input method screen, but that doesn’t happen.[/quote]

I had one previous guy tell me that the iControlPad works now - so I dunno. i don’t have an iControlPad myself so I can’t test.

Also,you should report the ‘HID name’ to me - perhaps your iControlpad reports something different. I explain in the OP of this thread how you can report the HID name of the device to me

#84

Ok, done it.

The iControlPad can be started in different modes: HID Keyboard, HID Joystick, HID Gamepad, etc. I have tryied the mentioned modes and the following data is reported by the emulators:

HID xx iControlPad-38DC

where xx was 10, 11, 12, 13, etc.

But I cannot get any mode to work with RetroArch, I can control the UI thouh.

#85

Start and Select are the same. Are you sure about this?

For the stick I’ll try implementing it as DPAD_UP/DPAD_DOWN/DPAD_LEFT/DPAD_RIGHT.

Can you compile from source? This could help in testing it before release (probably later this week).

Sorry about the Start/Select mix up. The correct strings are:


keycode_lut[AKEYCODE_BUTTON_R2] |= ((RETRO_DEVICE_ID_JOYPAD_START+1) << shift);
keycode_lut[AKEYCODE_BUTTON_L2] |= ((RETRO_DEVICE_ID_JOYPAD_SELECT+1) << shift);

Compiled and tested. All buttons are fine but stick isn’t recognized for now.

#86

Stick: x=0.00 y=0.00 on all directions. Manual input detector sees it as DPAD UP/DOWN/LEFT/RIGHT but Windows says it’s a POV Hat.

Are you sure it reports x 0, y 0 regardless of which direction you push the stick in? Mind testing it again?

#87

Hi Squarepusher, I just found this today: http://boards.openpandora.org/index.php/topic/12089-retroarch-now-supporting-icontrolpad-on-android/ That link talks about the iControlPad support in RetroArch, but you have to use bluez-ime to make it work ;(.

Maybe that’s the guy you mentioned earlier, the one who tested the icp? I don’t want to rely on Bluez-ime to use my pad, please could you add native support for the icp ;)?

#88

Unfortunately yes.

In doubt, I checked with the 360 D-Pad (also a POV for Windows). Same problem. Can browse Android menus, binds as D-Pad alright in the manual settings but can’t use in-game. Debug says x=0.00 y=0.00 on all directions.

Android doesn’t like hats?

#89

Hi,

I copy/paste email I sent:

My device is a iDroid x360 (chinese touch tablet with a gamepad)

step 3a: HID: “Sun4i-keypad”

step 4: ac always =0 and I can’t see src (always “src=” and end of the screen) Values for Pad 0:

Pad Up: 19 Pad down: 20 Pad right: 22 Pad left: 21 A: 69 B: 124 X: 76 Y: 123 Left trigger: 71 Right trigger: 112 Left Analog Up: 152 Left Analog Down: 146 Left Analog Right: 150 Left Analog Left: 148 Right Analog Up: 92 Right Analog Down: 93 Right Analog Right: 113 Right Analog Left: 72 START: 126 SELECT: 70 MENU: 82

I hope it will be good Thanks a lot for your work.

#90

Tip: added it to the autodetection list - will be in r13.

#91

Thanks Squarepusher.

#92

Hi squarepusher, any chances of IcontrolPad support without bluez-ime? Did the values I posted where of any help?

Can’t wait to try r13, I hope some day each core can be customized individually. The pcsx-rearmed core has a double resolution option wich locks impressive ;).

#93

Hi Squarepusher,

Is support for the JXD 7300B built into .r13? I know the mappings were previously posted up onto XDA, but if you need them again, just let me know.

Thanks!

#94

I still need the HID name - I had asked for this on xda-developers but I never got a response.

Follow the steps in the OP of this thread - and let me know the ‘HID name’ that it shows.

  1. go to ‘RetroArch Settings’ and go to ‘Input Settings’.
  1. Make sure that "Debug Input Reporting Enable’ is set to ‘OFF’.
  1. After that, start up a game with any emu (doesn’t matter which). The first thing I need to know exactly is the message that appears when you press a button on the pad - it should say something like

“HID {%some name here%]”

I need to know exactly that name that appears there.

#95

I still need the HID name - I had asked for this on xda-developers but I never got a response.

Follow the steps in the OP of this thread - and let me know the ‘HID name’ that it shows.

  1. go to ‘RetroArch Settings’ and go to ‘Input Settings’.
  1. Make sure that "Debug Input Reporting Enable’ is set to ‘OFF’.
  1. After that, start up a game with any emu (doesn’t matter which). The first thing I need to know exactly is the message that appears when you press a button on the pad - it should say something like

“HID {%some name here%]”

I need to know exactly that name that appears there.

[/quote]

Thanks! Just tried that and I see:

hid 6: adc joystick, p: 0

Does that sound right?

Thanks for all your amazing work on this.

#96

OK, I guess I could hook it up then.

#97

Great, let me know if you need me to test a pre-release build.

#98

Thank you for all your hard work. I just recently discovered RetroArch, and I’m really impressed. I escpecially love that it plays cave story. The only problem I’ve run into is the no diagonal problem with my wired xbox 360 controller. I was just wondering if you ever got a chance to check out that idea you said you had that could be causing it? I would be happy to help test it for you.

#99

I’m using the iPEGA controller in joystick mode as well and have some more info regarding the dpad. When setting up the custom binds for the controller, hitting either up on the dpad and up on the left stick during detect mode get bound as “DPAD UP”. Both the left stick and the dpad work to navigate the RetroArch setting menu. The problem is that in games only inputs on the left stick actually seem to be registered by the game , rather than the dpad.

It seems like hitting up on the dpad up should register DPAD UP, and hitting up on the stick should register something like STICK UP. Right now they both register to the same command, but only the less useful stick works when in-game. I should add that the right stick never seems to be detected in the custom binds menu.

Using the debug feature shows the same results as Matroc. EDIT: screwing around some more I can confirm that the dpad works in the android menu and works properly in several apps, including SuperGNES, NYTimes and Talk.

#100

Don’t know if this is a bug but while I was using the snes core with a dualshock 3 controller, I accidentally touched the screen of my phone while holding down on the controller. The input got stuck holding down and the controller stopped responding. Few seconds later, retroarch stopped responding then my phone all of a sudden showed the android boot animation and was just stuck there until I rebooted the phone. Music from the game I was playing just kept running in the background when the phone hanged on the boot screen.