I used a teensy 3.2 with an xbox(ish) setup, the only difference being the r2 and l2 are buttons not analog triggers. This would also apply to the teensy LC which is similar. Here's a couple pics of the handheld I made, I'm just getting the controls working and all the emulators setup and having a blast!

Here'a one-liner that will provide the event device from an joystick input device (here for /dev/input/js0): readlink -f /dev/input/by-path/`udevadm info /dev/input/js0 | grep ID_PATH= | awk -F= ' { print $2 }'`-event-joystick You can also check with cat /proc/bus/input/devices to see which event device is associated with a /dev/input/jsX device.

Could you tell me how to enable vibration in DInput? Or do I need to buy another gamepad? In what mode should it work for vibration to work?

@rogerdodger said in Configuring xboxdrv with Xin-Mo 2 player controller: Perhaps true 4 way controls can only be achieved mechanically, I have limited knowledge of Arcade stuff. i belive this is the only way ... as i suggested earlier, it is possible to physically switch from 4 to 8way by loosen the screw on the bottum, but if you want something that can switch automaticly i would suggest something like the ultimarc servostik perhaps, alltho those are quite a lot more expensive than the zippy joysticks (especially if you want 2).

@mitu Oh my bad, sorry. You can tell I'm a mega-noob because I have a default profile picture 😁

@Andrewpk200 if you use a crossover cable and hook your pi directly to your pc you can have everything transferred in no time.

@MapleStory i have that stick and a different mayflash adapter. I will test them when i get home.

Starting to see a pattern actually that it only works if I run it from the remote ssh connection AFTER the game starts. Can't remember if that was always the case but perhaps I can add some delayed start to a script so that it runs in the bg after the rom loads.

@mitu Thanks. I will give this a try and report back tomorrow as it is getting late here.

@mediamogul said in Using xboxdrv with mame4all/advmame: At this point, the only suggestion I can make to move forward is to reinstall RetroPie using the official image. I would also recommend re-configuring your network to allow a direct connection to your Pi so that you can troubleshoot these types of issues more effectively. I had to rework my entire network configuration about two weeks ago, so I know it's a pain. However, as it stands, you're working at a huge disadvantage by not being able to fully relay the exact contents of these configuration files and error logs. Yeah, redoing my network is something I'd like to do at some point anyway to simplify working with some things, but it's not something I'm prepared to do right away. Nor is re-flashing the SD card, although I recognize that would simplify a few things. (I'd have to save some of the info I've already setup, like my onstart/onend scripts, but that's okay.) I may have to go forward with the system as it is now and look into getting the rest of this working at a later date.

@lummox-jr It should let you edit it now that some time has passed. If not, I'll delete it and you can post your revision below. In any event, thanks for posting your solution. I don't currently have any games in mind that this would apply to, but I'm sure I'll run across some eventually and I'll give this a shot.

@aditkrator said in Changing Xbox driver based off game: Parsec for Raspberry Pi I hadn't heard of Parsec, but it looks like something similar to Moonlight, which I use (or did use, but ever since I updated to RetroPie 4.4 I can't seem to get it to work). I have quite a few individual bash scripts that invoke xboxdrv and then start moonlight and then individual games, so it can be done: sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv > /dev/null 2>&1 \ --silent \ --detach-kernel-driver \ --deadzone=4000 \ --deadzone-trigger 15% \ --force-feedback \ --mimic-xpad \ --trigger-as-button \ --ui-buttonmap lb=void,rb=void,tl=void,tr=void,guide=void,lt=void,rt=void \ --evdev /dev/input/by-path/platform-3f980000.usb-usb-0:1.3.2:1.0-event-joystick \ --device-name "Player_1" \ --evdev-absmap ABS_X=x1,ABS_Y=y1 \ --evdev-keymap BTN_THUMB=a,BTN_TOP=b,BTN_PINKIE=x,BTN_TRIGGER=y,BTN_THUMB2=back,BTN_TOP2=start \ --ui-axismap X1=KEY_DOWN:KEY_UP,Y1=KEY_RIGHT:KEY_LEFT \ --ui-buttonmap a=KEY_Z,b=KEY_E,x=KEY_X,y=KEY_Q,back=KEY_SPACE,start=KEY_ENTER \ --ui-buttonmap back+start=cycle-key:KEY_ESC:KEY_LEFTCTRL+KEY_LEFTSHIFT+KEY_LEFTALT+KEY_Q \ & sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv > /dev/null 2>&1 \ --silent \ --detach-kernel-driver \ --deadzone=4000 \ --deadzone-trigger 15% \ --force-feedback \ --mimic-xpad \ --trigger-as-button \ --ui-buttonmap rb=void,tl=void,tr=void,guide=void,lt=void,rt=void \ --evdev /dev/input/by-path/platform-3f980000.usb-usb-0:1.3.4:1.0-event-joystick \ --device-name "Player_2" \ --evdev-absmap ABS_X=x1,ABS_Y=y1 \ --evdev-keymap BTN_THUMB=a,BTN_TOP=b,BTN_PINKIE=x,BTN_TRIGGER=y,BTN_BASE=lb,BTN_THUMB2=back,BTN_TOP2=start \ --ui-axismap X1=KEY_F:KEY_R,Y1=KEY_G:KEY_D \ --ui-buttonmap a=KEY_S,b=KEY_P,x=KEY_A,y=KEY_W,back=KEY_J,start=KEY_H \ --ui-buttonmap back+start=cycle-key:KEY_ESC:KEY_LEFTCTRL+KEY_LEFTSHIFT+KEY_LEFTALT+KEY_Q \ & sudo /opt/retropie/emulators/moonlight/moonlight stream -bitrate 5000 -audio local -720 -fps 30 192.168.0.5 -app "UnderDefeat" moonlight quit 192.168.0.5 sudo killall > /dev/null 2>&1 xboxdrv The above script invokes xboxdrv, maps out 2 of my joysticks as against keyboard inputs and then starts moonlight and, ultimately, the game Under Defeat via an emulator on my Windows 7 based PC.

@aditkrator Can you check my update in the other topic to see if the workaround I posted there works for you also ?

@chipowski No problem. Glad it's working.

@xadox said in Configure 2 identical controllers differently: I will search on another solution without the use of xboxdrv. If you find anything, please post back. I'm always interested in alternatives to these types of problems.

This absolutely worked no problems to fix the permissions errors as a permanent solution. Thanks very much! The dragonrise controllers work for me now including save/load and exit shortcuts! :) amazing advice thanks guys

@tgilly If you'd like to diagnose the problem, then you'd have to provide the necessary info. No, I don't think 4.4 is unstable, but your problems look like a power supply problem, the system throttling itself down automatically, or more related to the fact that your ROM folder is mounted over the network. Check if your power supply is right up to the specs and then try running the ROMs from the sd card for a test to see if you get the same symptoms.