ScummVM Controlller Issues
-
good that we got rid of it now .... we shall start fresh and clean
(i think i meddled with this xboxdrv months ago ... how would i know or delete any controllers from the past )
-
thanks for pointing your's out and then mine
i know i may have a more simple controls ... but i still dont really understand & confused what im missing ... but hope you can clear that up
-
--evdev
is the code the controller sends out
--ui
is what we want the controller to do.so exampler from mine
i had the a key mapped as the left mouse button--evdev-keymap KEY_#304=a --ui-buttonmap a=BTN_LEFT
-
@escc1986 said in ScummVM Controlller Issues:
thanks for pointing your's out and then mine
i know i may have a more simple controls ... but i still dont really understand & confused what im missing ... but hope you can clear that up
im going to do my best
-
that makes sense to me , thank you
-
the buttons are the easy part. the dpad is tricky for me.
so i think work on getting the other buttons mapped. as i do some playing on my end -
sorry to be a headach ...
i guess the thing that confuses me the most is the steps
like there is alot of steps unless it can be simplfyed somehow
yes the d pad is what confuese me alot too
-
im going to try to start over ...
im going to discconect my keyboard and mouse and see if anything changes
-
ok after typing (With Disconnected keyboard and mouse )
cat /proc/bus/input/devices
my event changed to 0
event0
-
@escc1986 yes thats right.
the event will change as things are plugged in and outso is you dont play to have a keyboard in there full time best to set if for event 0
-
thank you for informing me , i had no idea ....
ok can you clear this up with me
which setting do i use out of these 3 settings :
sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv
--evdev /dev/input/by-id/[•]
--silent
--detach-kernel-driver
--force-feedback
--deadzone-trigger 15%
--deadzone 4000
--mimic-xpad
--evdev-absmap ABS_[•]=x1,ABS_[•]=y1,ABS_[•]=x2,ABS_[•]=y2,ABS_[•]=lt,ABS_[•]=rt,ABS_[•]=dpad_x,ABS_[•]=dpad_y
--evdev-keymap BTN_[•]=a,BTN_[•]=b,BTN_[•]=x,BTN_[•]=y,BTN_[•]=lb,BTN_[•]=rb,BTN_[•]=tl,BTN_[•]=tr,BTN_[•]=guide,BTN_[•]=back,BTN_[•]=start
&sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv
--evdev /dev/input/by-id/[•]
--silent
--detach-kernel-driver
--force-feedback
--deadzone-trigger 15%
--deadzone 4000
--mimic-xpad
--dpad-as-button
--evdev-absmap ABS_[•]=x1,ABS_[•]=y1,ABS_[•]=x2,ABS_[•]=y2,ABS_[•]=lt,ABS_[•]=rt
--evdev-keymap BTN_[•]=a,BTN_[•]=b,BTN_[•]=x,BTN_[•]=y,BTN_[•]=lb,BTN_[•]=rb,BTN_[•]=tl,BTN_[•]=tr,BTN_[•]=guide,BTN_[•]=back,BTN_[•]=start,BTN_[•]=du,BTN_[•]=dd,BTN_[•]=dl,BTN_[•]=dr
&sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv
--evdev /dev/input/by-id/[•]
--silent
--detach-kernel-driver
--force-feedback
--deadzone-trigger 15%
--deadzone 4000
--mimic-xpad
--evdev-absmap ABS_[•]=dpad_x,ABS_[•]=dpad_y
--evdev-keymap BTN_[•]=a,BTN_[•]=b,BTN_[•]=x,BTN_[•]=y,BTN_[•]=lb,BTN_[•]=rb,BTN_[•]=back,BTN_[•]=start
--dpad-only
--ui-axismap lt=void,rt=void
--ui-buttonmap tl=void,tr=void,guide=void
& -
just dont know which template to follow that is correct for my nes controller
that i will need to make a nano for
nano /etc/rc.local
-
@escc1986
i say go for the last one
you can always cut stuff outand stay out of rc.local
-
you will be doing your work in the runcommand.onstart
-
kind of confused .... so i
sudo nano /opt/retropie/configs/all/runcommand-onstart.sh
(This template)
sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv
--evdev /dev/input/by-id/[•]
--silent
--detach-kernel-driver
--force-feedback
--deadzone-trigger 15%
--deadzone 4000
--mimic-xpad
--evdev-absmap ABS_[•]=dpad_x,ABS_[•]=dpad_y
--evdev-keymap BTN_[•]=a,BTN_[•]=b,BTN_[•]=x,BTN_[•]=y,BTN_[•]=lb,BTN_[•]=rb,BTN_[•]=back,BTN_[•]=start
--dpad-only
--ui-axismap lt=void,rt=void
--ui-buttonmap tl=void,tr=void,guide=void
& -
close
you need this on the top or it will not know when to start the mappingif [ "$1" = "scummvm" ] then sudo killall >> /dev/shm/runcommand.log 2>&1 xboxdrv sudo /opt/retropie/supplementary/xboxdrv/bin/xboxdrv >> /dev/shm/runcommand.log 2>&1 \ --evdev /dev/input/by-id/[•] \
-
https://retropie.org.uk/docs/Universal-Controller-Calibration-&-Mapping-Using-xboxdrv/
go to the
Key-Mapping For Individual Emulators part to get a start on how the runcommand needs to look like
but for now i think you should just put your mapping in a txt on your computer.
there are ways to test it before you setup the run command
-
not sure what to put here
--evdev /dev/input/by-id/[•] \
(the dot)
-
@escc1986
just use the event and the number so for you it will be event0
i could never get the id-to workthink you could send me a link or something for your controller.
when you posted the event codes there are alot more buttons then i would of thought for a NES -
--evdev /dev/input/by-id/event0 \
like so ?
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.