@Trillien

I expanded your technique to include any Bluetooth controller and added it to the xboxdrv guide as succinctly as possible. Thanks again for this.

@ward614

Unfortunately, setting xboxdrv up in this way is a good bit more involved than just copying a few files. The documentation page is written to cover each and every little step, but it does require that you begin with a certain understanding of how to access and edit files remotely, as well as remotely execute commands. Even afterwards, you'll likely stumble around a fair amount before you have a working understanding of the whole thing.

If this hasn't scared you away yet, then my advice to you would be to not worry about the process as a whole and only concern yourself with the first few steps. If that works out for you, keep moving forward until you need help. Whenever you do need help, just come back here and I'll be happy to answer any questions that you might have.

To add to this I was able to get it connected again. It worked and I tested a couple games. I restarted the Pi and it would not work. If I shut down the pi and turn it back on, then turn the controller back on it connects. If I go to config to setup Joypad order it only shows '4' xbox controllers even though only 1 is connected. I shut down a couple more times like normal and booted up and controller connected. Now I shut down and boot the system back up and controller does not connect. Just blinks. When it does connect it will show player 1.

@Dan problem with renaming the page is it breaks the original link. GitHub doesn't handle redirects

Yes there seems to be differences with these cheap china dongles. Well, I got refunded all money for the dongle and did not have to return it. Will order Micro$oft genuine one next. But, if somebody has tips how can i get that cheap dongle working, i am open for suggestions. Thanks backstander for the help earlier :)

So, that cheap dongle has something wrong with it, win10 does not make the usb connection sound and is not recoqnized with device manager. But, light is lit and blinking when button is pressed. Also, RPi does not show it in lsusb list.

I would also be quite interested to hear people's opinions and experience with this. The advanced controller mapping guide is excellent and very comprehensive for xboxdrv however the retropie wiki does seem to suggest xpad is the preferred and is even the default.

I would especially be interested if anyone has any suggestions for xpad tweaks to improve ScummVM analog control.

Thanks very much.

@markg said in xboxdrv works in FE / shell but not emulator:

Is there a different place I should put this to make it more permanent?

This setting can be hardcoded in /opt/retropie/configs/all/retroarch.cfg. The entry you're looking for is:

input_player1_joypad_index = "x"

Something else that comes to mind and is completely untested by myself is that this setting could be altered alongside xboxdrv launching, so as to accommodate individual mappings and controllers on-the-fly. Try at your own risk, but something like this might work well:

sed -i 's/input_player1_joypad_index = "*"/input_player1_joypad_index = "1"/g' /opt/retropie/configs/all/retroarch.cfg

@i8allUrPi

I really appreciate your time and effort.

Not a problem. I'm glad it all worked out.

@herb_fargus I tried it but doesn't work: Pi3 stuck on rainbow screen after a kernel downgrade.

@dudleydes said in Mapping Numeric Keypad to Analog Stick:

Bioforge uses the Ctrl and Alt keys with the numpad for hand and feet combat so using modifiers is going to result in some serious finger contortion!

On all the keypad-based systems I've mapped this way, most just use keypad input for menu options such as player and difficulty selection, which can be casually selected. However, I can definitely see why mapping a game like 'Bioforge' this way wouldn't be any fun. Intellivision games often make the keypad an integral part of the core control scheme as well and I sometimes find myself doing mental and finger gymnastics in order to simply move a character from left to right. I end up having to tailor map a custom control scheme if I want to play the game any further.

Anyway, I'm glad you found an option that works for you. It does seem to be the best solution.

@mediamogul I agree. I'll continue to update in a new thread.

I found a solution in case anyone else has this problem in the future:

I did cat /proc/bus/input/devices to list input devices, which does not give the full ID. But I saw a "Wireless Controller" listed there, so I knew that was my bluetooth controller. I saw it had an H: Handlers set as event0 and I recalled being ale to substitute this for the full ID. So, instead of doing --evdev /dev/input/by-id/*** where the ID is still unknown at this time, I was able to do --evdev /dev/input/event0 instead.

Now whether or not the button mappings I did are accurate is a whole different problem. Time to go test it out.

@BuZz thanks for the help, I'll try a fresh install and give kodi17 a go. Not sure why I had neither xpad or xboxdrv installed on 4.1 and the controller worked fine after only editing rc.local

First post updated

I also noticed, When running evtest, event0 and event2 outputs data. event0 which are the gamepad buttons, no output at all.

(event2 is the clear, turbo and home button on the controller)

@BuZz

Ah, that's too bad.

I renamed the file.

I also went to RetroArch congifuration and put the digital->Left analog to P2 and P3 (silly me!!)

It worked like a dream.

Thanx @meleu

@Pyjamarama said in UAE4Arm XBOXDRV - Mouse in Pad - F12:

I have put them in the opt/retropie/configs/amiga/emulators.cfg

uae4all = "/home/pi/RetroPie/roms/amiga/+Start\ UAE4All.sh" default="uae4arm" uae4arm="/home/pi/RetroPie/roms/amiga/+Start\ UAE4Arm.sh %ROM%" --ui-axismap x1=REL_X:10,y1=REL_Y:10 \ --ui-buttonmap y=BTN_LEFT,x=BTN_RIGHT,back=KEY_F12 \

but it does not do anything. I must be doing something wrong...

It requires a bit more effort unfortunately.

Take a look at my solution that by the way enables per-game joypad mapping config.

The +Start UAE4Arm.sh script has been modified to look for a file with the same name as the .uae config, but having .script extension. The .script file can contain things you might want to get executed before launching the game and after it is closed.

/opt/retropie/configs/amiga/emulators.cfg uae4arm line:

uae4arm="/home/pi/RetroPie/roms/amiga/+Start\ UAE4Arm.sh %ROM%"

/home/pi/RetroPie/roms/amiga/+Start UAE4Arm.sh

#!/bin/bash pushd "/opt/retropie/emulators/uae4arm" config=$1 script=$(echo $config | awk -F\. '{print $1}').script if [ -f "$script" ]; then /bin/bash "$script" "before" fi if [ -n "$config" ]; then ./uae4arm -f "$config" else ./uae4arm fi if [ -f "$script" ]; then /bin/bash "$script" "after" fi popd

Now the fun part - an example specific for Slam Tilt (and my pad) - Slam Tilt.script:
(note: my config name is Slam Tilt.uae)

#!/usr/bin/env bash case $1 in "before") sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv \ --evdev /dev/input/event0 \ --silent \ --detach-kernel-driver \ --force-feedback \ --deadzone-trigger 15% \ --deadzone 4000 \ --device-name "Media-Tech Wireless Pad" \ --evdev-absmap ABS_X=x1,ABS_Y=y1 \ --evdev-keymap BTN_SOUTH=a,BTN_EAST=b,BTN_NORTH=x,BTN_C=y,BTN_WEST=lb,BTN_Z=rb,BTN_TL=tl,BTN_TR=tr,BTN_TL2=guide,BTN_SELECT=back,BTN_TR2=start \ --ui-buttonmap tl=KEY_SPACE,tr=KEY_SPACE,lb=KEY_A,rb=KEY_L,a=KEY_ENTER,b=KEY_S,x=KEY_Y,start=KEY_F1,guide=KEY_ESC,back=BTN_LEFT,y=KEY_UP \ --ui-axismap y1=KEY_DOWN,x1=KEY_LEFT \ & ;; "after") sudo pkill -9 xboxdrv ;; *) echo "Need a paramter: 'before' or 'after'" esac

Obviously, you should tune the absmap, keymap, buttonmap and axismap lines to suit your needs (/opt/retropie/supplementary/xboxdrv/bin/xboxdrv --help-all and evtest /dev/input/event0 are your friends).

I would not recommend using xboxdrv anymore. It used to be the go-to for 360 controllers but Xpad is now better. Here's some documentation on it:

https://github.com/retropie/retropie-setup/wiki/Setting-up-the-XBox360-controller

As for the version that you are currently running, there is no easy command to run to get this. Here is a Reddit post that mentions (in the comments) how to find out what version you have from Github which you'd then need to compare to what is on your screen.
As I understand it, the reason there is not an easy, one-line command is because Retropie is not one big program. Instead it is a ton of smaller programs all bound together. If you think about the many emulators that you can run on Retropie, each emulation program has its own version. This might be an oversimplification but it is how I understand it from the research I've done.

You can always follow this wiki update guide (same website as the top) to make sure you are on the latest but there is always the chance of messing up the current settings/controls you have set.

Best case scenario for you, you will see xpad on the list of drivers, install it, and things work well. But my experience is that if you change one thing, others will be modified accidentally.