Guide: Advanced Controller Mappings

spud11

mediamogul

@spud11 said in Guide: Advanced Controller Mappings:

Does this correspond to the "$" inputs 1, 2, 3, 4?

It does and I was hoping to see something wrong here that would explain your issues, but everything seems to be in order. I won't lie, I'm starting to run out of ideas here myself. One thing you can try is to add:

#!/bin/bash

sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv \
    --evdev /dev/input/by-path/platform-3f980000.usb-usb-0:1.2.3:1.0-event-joystick \
	--silent \
	--detach-kernel-driver \
	--force-feedback \
	--deadzone-trigger 15% \
	--deadzone 4000 \
	--trigger-as-button \
	--mimic-xpad \
	--device-name "Amiga Joystick Player 1 (xboxdrv)" \
	--evdev-absmap ABS_X=y1,ABS_Y=x1 \
	--evdev-keymap BTN_TRIGGER=x,BTN_THUMB=y,BTN_THUMB2=a,BTN_PINKIE=b,BTN_BASE3=back,BTN_BASE6=start \
	--ui-buttonmap lb=void,rb=void,tl=void,tr=void,guide=void,lt=void,rt=void \
&

to it's own separate script and in turn launch it from runcommand-onstart.sh with:

if [ "$1" = "amiga" ]
then
sh /path/to/new/script.sh
fi

EctoOne

Sorry to interrupt, I didn't read all of the lasts post. It is about setting up xboxdrv to work with uae4arm and the possibility that launching uae files might cause some trouble right? If so, I have no problems with the same setup. Although I replaced uae4arm with amiberry. So if needed I could copy the controller setup part from the guide I used.

The only thing that I can't figure out, is how to get custom controls within uae4arm/amiberry to work. Which would be great if I could map the X, Y Buttons to whatever the game needs. But from what I've found that seems to be a bug with amiberry (never tried it with uae4arm), so I have to wait for an update to that.

mediamogul

@EctoOne said in Guide: Advanced Controller Mappings:

If so, I have no problems with the same setup.

On paper, there should be nothing preventing this from working on any setup. There has to be some other factor at play that is not being accounted for, but I'll be hornschwaggled if I can see it.

Which would be great if I could map the X, Y Buttons to whatever the game needs.

Almost any computer game responds to keyboard input. You could always map the keys to the controller.

EctoOne

@mediamogul said in Guide: Advanced Controller Mappings:

Almost any computer game responds to keyboard input. You could always map the keys to the controller.

Yes I know that. It works for something like ScummVM where you can map the start button to F5. Because that's the key most ScummVM games use to access the menu. But for Amiga games it's more different what keys are needed. Example I want to use X as Spacebar for Turrican but on The Clue! I want X to be F1 to be able to open the menu.
Uae4arm has a menu to map buttons on its own but I can't get it to work. And I don't know if that's an uae4arm/amiberry problem or if there is a conflict with my setup.

mediamogul

@EctoOne

Ah, I gotchya. I have a similar need for some individual system games. If you use if [ "$3" = "/path/to/rom" ] in your if/else statement, you can launch your mappings based on individual ROMs rather than have them applied to whole systems.

spud11

@mediamogul I've now given that one a go too:

#!/bin/sh

if [ "$1" = "amiga" ]
then
sh /opt/retropie/configs/amiga/joystick.sh
fi

joystick.sh is:

#!/bin/sh

sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv \
    --evdev /dev/input/by-path/platform-3f980000.usb-usb-0:1.2.3:1.0-event-joystick \
	--silent \
	--detach-kernel-driver \
	--force-feedback \
	--deadzone-trigger 15% \
	--deadzone 4000 \
	--trigger-as-button \
	--mimic-xpad \
	--device-name "Amiga Joystick Player 1 (xboxdrv)" \
	--evdev-absmap ABS_X=y1,ABS_Y=x1 \
	--evdev-keymap BTN_TRIGGER=x,BTN_THUMB=y,BTN_THUMB2=a,BTN_PINKIE=b,BTN_BASE3=back,BTN_BASE6=start \
	--ui-buttonmap lb=void,rb=void,tl=void,tr=void,guide=void,lt=void,rt=void \
&

Unfortunately, there is no output .log file .info file.

It seems that the runcommand-onstart.sh will work, but only if there is no if/then statement.

I'll have a quick go at replacing "amiga" with another system and see what eventuates.

spud11

@spud11 Tried with "c64" instead of "amiga" and same results as for amiga - separate script no output in dev/shm and a similar output if the sudo statement appears directly in the runcommand statement.

Perhaps I could somehow include reference to the script in the .uae files instead? I don't know.

spud11

@EctoOne You seem to have a similar problem to me. I'm using amiberry too. Although the author thought he had got custom controls to work from the f12 menu, I haven't been able to get that working either. Apparently, he is thinking of "going" libretro, but it hasn't happened yet.

What I do know is that if I use runcommand-onstart.sh to install xboxdrv (but without the if/then statement), my "amiga joystick" does appear in the uae4arm menu (ie press f12) and I can select that joystick and all works well in game after "resuming" the game.

Also, it is possible to manually bulk change all the individual game .uae scripts to default to the "amiga joystick" for player 1. I use a Windows program called "Find and Replace " to achieve that: http://findandreplace.sourceforge.net

That will work, but obviously because there is no if/then statement in runcommand-onstart.sh, my controls are all screwed up for every other emulator/core which is self-defeating.

EctoOne

@mediamogul said in Guide: Advanced Controller Mappings:

@EctoOne

Ah, I gotchya. I have a similar need for some individual system games. If you use if [ "$3" = "/path/to/rom" ] in your if/else statement, you can launch your mappings based on individual ROMs rather than have them applied to whole systems.

Oh really, that sounds like a solution but it also sounds like a lot more work. If the custom controls within uae4arm where working, i could map the buttons on the fly and to see what's best and then simply save the config file. But thanks for the hint, i might give it a shot.

@spud11
This is a copy of the guide i used (Can't provide a link, because it also contains games)

And this is my runcommand-onstart.sh (scummvm settings removed to avoid confusion):

#!/bin/sh
## Uncomment one or all of the following if you need to find some information about the emulator or roms
## Name of the emulator
#echo $1 >> /dev/shm/runcommand.log

## Name of the software used for running the emulation
#echo $2 >> /dev/shm/runcommand.log

## Name of the rom
#echo $3 >> /dev/shm/runcommand.log

##Executed command line
#echo $4 >> /dev/shm/runcommand.log


### The FUN begins
#Get ROM name striping full path
rom="${3##*/}"

### Set variables for your joypad and emulator
### Basic Configuraions - Standard controller mappings 
LogiF710="/opt/retropie/supplementary/xboxdrv/bin/xboxdrv > /dev/null \
	--evdev /dev/input/event3 \
	--silent \
	--detach-kernel-driver \
	--deadzone=4000 \
	--deadzone-trigger 15% \
	--force-feedback \
	--mimic-xpad \
	--trigger-as-button \
	--evdev-absmap ABS_X=x1,ABS_Y=y1,ABS_RX=x2,ABS_RY=y2,ABS_HAT0X=dpad_x,ABS_HAT0Y=dpad_y \
	--evdev-keymap BTN_SOUTH=a,BTN_EAST=b,BTN_NORTH=x,BTN_WEST=y,BTN_TL=lb,BTN_TR=rb,BTN_TL2=lt,BTN_TR2=rt,BTN_THUMBL=tl,BTN_THUMBR=tr,BTN_SELECT=back,BTN_START=start,BTN_MODE=guide \
	--calibration x1=-32767:0:32767,y1=-32767:0:32767,x2=-32767:0:32767,y2=-32767:0:32767"


### Extended Configurations
### Specific emulator configuration or any other parameters you will need only for some emulators
amiga="--axismap -Y1=Y1,-Y2=Y2 \
	--buttonmap tl^toggle=tl \	
        --buttonmap rt^toggle=rt \
	--ui-axismap tl+x1=REL_X:5,tl+y1=REL_Y:5 \
	--ui-buttonmap tl+a=BTN_LEFT,tl+b=BTN_RIGHT \
	--ui-buttonmap start=KEY_P,back=void \
	--ui-buttonmap rt+a=KEY_ENTER,rt+b=KEY_ESC,rt+x=KEY_SPACE,rt+y=KEY_F1,rt+du=KEY_UP,rt+dd=KEY_DOWN,rt+dl=KEY_LEFT,rt+dr=KEY_RIGHT \
	--ui-buttonmap guide=KEY_F12,guide+start=KEY_Q \
	--ui-axismap x2=void"

fourway="--four-way-restrictor"

invert="--ui-buttonmap du=KEY_DOWN,dd=KEY_UP"

### Kill Command
xboxkill="sudo killall >/dev/null xboxdrv"

### Execute the driver with the configuration you need
# $1 is the name of the emulation, not the name of the software used
# it is intellivision not jzintv
case $1 in

    amiga)
        $xboxkill
        joycommand="$LogiF710 $amiga &"
        eval $joycommand
    ;;
esac

Beware that i'm using a Logitech F710 controller, so you can't probably just copy paste that. This mapping toggles mouse/joystick function when pressing the left analog stick and also toggles cursor keys on the digipad when pressing RT/R2 (instead of holding RT/R2)

mediamogul

@spud11

I'm curious as to whether or not any if/then statements will run on your setup. Try adding the test below to your runcommand-onstart.sh and then look to see if the two test sentences were written in runcommand.log after running a game.

test=yes
if [ "$test" = "yes" ]
then
echo "This is only a test." >> /dev/shm/runcommand.log
fi
if [ "$1" = "amiga" ]
then
echo "This is also only a test." >> /dev/shm/runcommand.log
fi

spud11

@mediamogul The runcommand-onstart.sh looks like this:

#!/bin/sh

if [ "$1" = "amiga" ]
then
sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv \
    --evdev /dev/input/by-path/platform-3f980000.usb-usb-0:1.2.3:1.0-event-joystick \
	--silent \
	--detach-kernel-driver \
	--force-feedback \
	--deadzone-trigger 15% \
	--deadzone 4000 \
	--trigger-as-button \
	--mimic-xpad \
	--device-name "Amiga Joystick Player 1 (xboxdrv)" \
	--evdev-absmap ABS_X=y1,ABS_Y=x1 \
	--evdev-keymap BTN_TRIGGER=x,BTN_THUMB=y,BTN_THUMB2=a,BTN_PINKIE=b,BTN_BASE3=back,BTN_BASE6=start \
	--ui-buttonmap lb=void,rb=void,tl=void,tr=void,guide=void,lt=void,rt=void \
&
fi
test=yes
if [ "$test" = "yes" ]
then
echo "This is only a test." >> /dev/shm/runcommand.log
fi
if [ "$1" = "amiga" ]
then
echo "This is also only a test." >> /dev/shm/runcommand.log
fi

And the runcommand.log is this:

/opt/retropie/configs/all/runcommand-onstart.sh: line 2: $'\r': command not found
/opt/retropie/configs/all/runcommand-onstart.sh: line 18: syntax error near unexpected token `&'
/opt/retropie/configs/all/runcommand-onstart.sh: line 18: `&
'
Parameters: 
Executing: pushd /opt/retropie/emulators/uae4arm/; ./uae4arm -config="/home/pi/RetroPie/roms/amiga/Alien Breed Special Edition '92.uae"
/opt/retropie/emulators/uae4arm /opt/retropie/supplementary/runcommand
Amiberry build 2017-01-08, by Dimitris (MiDWaN) Panokostas and Olly Aigner
Based on previous work by Chips and TomB (Pandora)
Joystick 0 : DragonRise Inc.   Generic   USB  Joystick  
    Buttons: 12 Axis: 4 Hats: 1
Joystick 1 : DragonRise Inc.   Generic   USB  Joystick  
    Buttons: 12 Axis: 4 Hats: 1
Joystick 2 : DragonRise Inc.   Generic   USB  Joystick  
    Buttons: 12 Axis: 4 Hats: 1
Joystick 3 : DragonRise Inc.   Generic   USB  Joystick  
    Buttons: 12 Axis: 4 Hats: 1
starting sound thread..
stopping sound thread..
xboxdrv: no process found

spud11

@EctoOne Hi EctoOne. I've seen a guide similar to the one you've provided. Thanks for that. I think most of the characteristics in the guide I've got, but will look at more closely.

Also, I'm familiar with your runcommand-onstart.sh. I recall the script it's based on had a "per rom" setting (as mediamogul has pointed out) as a possible way of getting xboxdrv working. (It was for mame games, and I think you've got a residual "per rom" setting from the original script in your script - rom="${3##*/}" too).

I agree "per rom" would be a lot of work unless it could be automated in some way, but that does assume we're able to get xboxdrv with "if/then" working at all with the amiga. At this stage, it doesn't appear that the if/then statement works at all, for whatever reason, as mine at least "hangs" straight away on the first line being the "if" statement $'\r'.

mediamogul

@spud11

I'm somewhat stumped. I'll continue to give it thought, but I really can't see a reason why this isn't working. The fact that you're getting script errors regarding information that is not even in your script is really odd. You might try looking around for other instances online where similar statements are read incorrectly and what might cause such a thing.

EctoOne

@spud11
I'm not sure what the rom thing is about in my script. I just copied it, entered the F710 buttons and made some changes to the mapping.

But I noticed that in my script are no if/fi parts compared to yours. Maybe you should go and try mine.

spud11

@mediamogul Will do. Thanks.

spud11

@spud11 Thanks, EctoOne. I will have a go with your script too and I'll let you know. Thanks.

spud11

@EctoOne Hi. I adapted your script as below which I think should work:

#!/bin/sh
## Uncomment one or all of the following if you need to find some information about the emulator or roms
## Name of the emulator
#echo $1 >> /dev/shm/runcommand.log

## Name of the software used for running the emulation
#echo $2 >> /dev/shm/runcommand.log

## Name of the rom
#echo $3 >> /dev/shm/runcommand.log

##Executed command line
#echo $4 >> /dev/shm/runcommand.log


### The FUN begins
#Get ROM name striping full path
rom="${3##*/}"

### Set variables for your joypad and emulator
### Basic Configuraions - Standard controller mappings 
DragonRise="/opt/retropie/supplementary/xboxdrv/bin/xboxdrv
	--evdev /dev/input/by-path/platform-3f980000.usb-usb-0:1.2.3:1.0-event-joystick \
	--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 \


### Extended Configurations
### Specific emulator configuration or any other parameters you will need only for some emulators
amiga="--device-name "Amiga Joystick Player 1 (xboxdrv)" \
	--evdev-absmap ABS_X=y1,ABS_Y=x1 \
	--evdev-keymap BTN_TRIGGER=x,BTN_THUMB=y,BTN_THUMB2=a,BTN_PINKIE=b,BTN_BASE3=back,BTN_BASE6=start \"

fourway="--four-way-restrictor"


### Kill Command
xboxkill="sudo killall xboxdrv"

### Execute the driver with the configuration you need
# $1 is the name of the emulation, not the name of the software used
# it is intellivision not jzintv
case $1 in

    amiga)
        $xboxkill
        joycommand="$DragonRise $amiga &"
        eval $joycommand
    ;;
esac

I ended up with the following output:

/opt/retropie/configs/all/runcommand-onstart.sh: line 5: $'\r': command not found
/opt/retropie/configs/all/runcommand-onstart.sh: line 8: $'\r': command not found
/opt/retropie/configs/all/runcommand-onstart.sh: line 11: $'\r': command not found
/opt/retropie/configs/all/runcommand-onstart.sh: line 14: $'\r': command not found
/opt/retropie/configs/all/runcommand-onstart.sh: line 15: $'\r': command not found
/opt/retropie/configs/all/runcommand-onstart.sh: line 19: $'\r': command not found
/opt/retropie/configs/all/runcommand-onstart.sh: line 36: Amiga Joystick Player 1 (xboxdrv): command not found
/opt/retropie/configs/all/runcommand-onstart.sh: line 37: --evdev-absmap: command not found
/opt/retropie/configs/all/runcommand-onstart.sh: line 38: --evdev-keymap: command not found
/opt/retropie/configs/all/runcommand-onstart.sh: line 39: $'\r': command not found
/opt/retropie/configs/all/runcommand-onstart.sh: line 41: $'\r': command not found
/opt/retropie/configs/all/runcommand-onstart.sh: line 42: $'\r': command not found
/opt/retropie/configs/all/runcommand-onstart.sh: line 45: $'\r': command not found
/opt/retropie/configs/all/runcommand-onstart.sh: line 49: syntax error near unexpected token `$'in\r''
/opt/retropie/configs/all/runcommand-onstart.sh: line 49: `case $1 in
'
Parameters: 
Executing: pushd /opt/retropie/emulators/uae4arm/; ./uae4arm -config="/home/pi/RetroPie/roms/amiga/Alien Breed Tower Assault.uae"
/opt/retropie/emulators/uae4arm /opt/retropie/supplementary/runcommand
Amiberry build 2017-01-08, by Dimitris (MiDWaN) Panokostas and Olly Aigner
Based on previous work by Chips and TomB (Pandora)
Joystick 0 : DragonRise Inc.   Generic   USB  Joystick  
    Buttons: 12 Axis: 4 Hats: 1
Joystick 1 : DragonRise Inc.   Generic   USB  Joystick  
    Buttons: 12 Axis: 4 Hats: 1
Joystick 2 : DragonRise Inc.   Generic   USB  Joystick  
    Buttons: 12 Axis: 4 Hats: 1
Joystick 3 : DragonRise Inc.   Generic   USB  Joystick  
    Buttons: 12 Axis: 4 Hats: 1
starting sound thread..
stopping sound thread..
xboxdrv: no process found

I'll trawl the forums and see if I can find any information about the error $'\r'. Thanks.

I'll probably need to think of options other than using runcommand-onstart. Possibly even recompiling the emulator itself.

EctoOne

@spud11
I'm no tech expert but seeing you getting even more errors with my script let's me think that either your xboxdrv version is different or something went wrong during the installation.

Edit: From what I've found is that \r seems to be caused by Windows newline characters. You said that you're using Notepad++ so that would make sense if you copy/pasted my script. So you should try to ssh into your Pi with putty. Use nano to edit the file (mentioned above by @mediamogul), delete everything, and copy it back in using middle mouse button. Or delete the file and make a new one with nano.

spud11

@EctoOne Thanks for that tip. I'll try that later.

That might explain why earlier on, I was finding that the xboxdrv script was working 100% in rc.local only when the whole script was on one line, but didn't seem to work when I had used \ and enter at the end of each line.

I'll try the copy/paste way with nano first and then, if that doesn't work, I'll manually type it all back in with nano. A bit laborious but best way to ensure the script works.

Just checked the WinSCP documentation too:

"Text/ASCII Transfer Mode
For this reason, file transfer clients and servers support a text/ASCII transfer mode.
When transferring a file in this mode, the file gets (ideally) converted from a format native to a source system, to a format native to a target system.
For example, when uploading a text file using text mode from Windows to Unix system, the file line endings get converted from CR+LF to LF.
Opposite to the text/ASCII transfer mode is a binary transfer mode that transfer the file as is (binary identical).
WinSCP by default uses the binary transfer mode for all regular file transfers. "

I've also at various times copied the runcommand-onstart.sh from Windows to the Pi and made the file executable, so based on the above, the transfer is likely to have been in binary transfer mode by default, meaning that /r new line errors are very possible.