D'oh seems they have added extra move from other versions of this game.

Thanks for help.

@reginaldsharma said in Unable to use hotkeys with xbox360 controller on retro4.3:

but next time around i made it the xbox button. still was having issues.

See what @BobHarris also said. If you mapped the now 'xbox' button as Hotkey, then it will replace what you previously used (Select) in the button combinations you're trying now. If you left the Hotky button unmapped, then the input dialog will ask you if you want to use Select and then it should work as in ver. 4.1.

@woody440 https://retropie.org.uk/forum/topic/3/read-this-first

Thanks got it working

@caver01 Of course :) I will definetly post. I took a few photos during the build, and its still not finished yet. Should be done in a week :)

Here are some tests i have done :

$ jstest /dev/input/js0 Driver version is 2.1.0. Joystick (PowerA Xbox One wired controller) has 6 axes (X, Y, Rx, Ry, Hat0X, Hat0Y) and 13 buttons (BtnX, BtnY, BtnTL, BtnTR, BtnTR2, BtnSelect, BtnStart, BtnMode, BtnThumbL, BtnThumbR, ?, ?, ?). Testing ... (interrupt to exit) Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off 10:off 11:off 12:off $ lsmod | grep xpad xpad 18566 0 ff_memless 5315 1 xpad $ evtest /dev/input/event[0] Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x24c6 product 0x543a version 0x101 Input device name: "PowerA Xbox One wired controller" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 304 (BTN_SOUTH) Event code 305 (BTN_EAST) Event code 307 (BTN_NORTH) Event code 308 (BTN_WEST) Event code 310 (BTN_TL) Event code 311 (BTN_TR) Event code 312 (BTN_TL2) Event code 313 (BTN_TR2) Event code 314 (BTN_SELECT) Event code 315 (BTN_START) Event code 316 (BTN_MODE) Event code 317 (BTN_THUMBL) Event code 318 (BTN_THUMBR) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 1 (ABS_Y) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 3 (ABS_RX) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 4 (ABS_RY) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 16 (ABS_HAT0X) Value 0 Min -1 Max 1 Event code 17 (ABS_HAT0Y) Value 0 Min -1 Max 1 Event type 21 (EV_FF) Event code 80 (FF_RUMBLE) Event code 81 (FF_PERIODIC) Event code 88 (FF_SQUARE) Event code 89 (FF_TRIANGLE) Event code 90 (FF_SINE) Event code 96 (FF_GAIN)

I use just lr-tyrquake and copy files of "Abyss of Pandemonium" to folder I've created maybe/home/pi/RetroPie/roms/ports/quake/aopfm_v2

and then I create a bash script inside nano /home/pi/RetroPie/roms/ports/quake/Abyss.sh that contains:

#!/bin/bash path="/home/pi/RetroPie/roms/ports/quake/aopfm_v2" #------------ "/opt/retropie/supplementary/runcommand/runcommand.sh" 0 _PORT_ "quake" "${path}/pak0.pak"

That's all

@halfdaymatt

hello i have the same problem or should i go to see if it has the duplicate configuration i am lost:

Seems OK on Safari on iOS 11.2
Seems OK on Chromium 63.0.3239.84 on GalliumOS 2.1

Weird.

@steve-bamford Not a problem. xroar is a "niche" emulator at best. We gotta stick together. Enjoy. Get yourself a full game ROM set and go crazy!

@mitu @chipsnblip Hahaha, wow. How embarrassing. Thanks, I will try this and report back.

...I think it was my fault...
I was thinking, that retropie shows me the usb files, when i plug in the stick...
But it look like, it shows alltime the files on the sd card ;-)
...so I have created a folder "retropie-mount" on the usb stick, let retropie copy all roms to it, and after that I deleted any files in "\retropie\roms"
Look like this solve my issue.

I think now I understand the differents between the directory "retropie" and "retropie-mount"
...if I want to import roms to the sd card, i put the files on the usb stick to "retropie" and if I like to use a external usb stick as storage for the roms, I use the "retropie-mount" directory on the usb stick...
Is this right?

@retroprogrammer No problem. The switch issue on Raspberry Pi is a need for everyone, not just RetroPie users. So, you can google the idea and find all kinds of examples of people using a simple momentary switch to short a GPIO pin to ground with examples of their custom scripts to monitor for that event. In most cases, examples in include a shutdown command, and that would be enough to do a soft shutdown or reboot. However, it is this command that you could replace with something more retropie-specific found in the threads here.

Close this thread. I threw that piece of crap away and just bought a new one. =/ Now I have to go through all the setup again.

Ok have resolved this issue by performing a fresh install after backing up roms via network

Installed using retropie v4 video

installing controller from fresh install all works fine, 2nd player works fine too

also start & select now exits games

@mitu Okay, just did that, didn't work.

I decided to see if there were some config settings or something under xboxdrv so I ran it from the terminal, but it throws an error saying there are no Xbox controllers connected...
Even though I was just using it in ES.

I then ran jstest which looked actually does detect controller inputs... so I don't know where the issue really is... unless my controller is incompatible with xboxdrv?

I've used 2 different controllers for testing though and they don't work.

@mitu , thanks for your reply.

I have not used Pastebin before, so I hope I am doing this right.

I have one controller plugged in; the GameCube controller through the Mayflash adaptor. I have remapped the controller to use the xboxdrv using these instructions and I only configured the xboxdrv controller through the EmulationStation Configure Input tool, which explains why the runcommand.log says the controller on Pad #0 does not have a profile but the xboxdrv controller on Pad #1 does have a profile.

[INFO] [udev]: Plugged pad: Wii U GameCube Adapter Port 1 (0:0) on port #0. [INFO] [udev]: Pad #0 (/dev/input/event0) supports force feedback. [INFO] [udev]: Pad #0 (/dev/input/event0) supports 4 force feedback effects. [INFO] [Autoconf]: 4 profiles found. [INFO] [Autoconf]: no profiles found for Wii U GameCube Adapter Port 1 (0/0). [INFO] [udev]: Plugged pad: Wii_GameCube_Port_1_(xboxdrv) (0:0) on port #1. [INFO] [udev]: Pad #1 (/dev/input/event1) supports force feedback. [INFO] [udev]: Pad #1 (/dev/input/event1) supports 16 force feedback effects. [INFO] [Autoconf]: 4 profiles found. [INFO] [Autoconf]: selected configuration: /home/pi/.config/retroarch/autoconfig/Wii_GameCube_Port_1_(xboxdrv).cfg [INFO] [Joypad]: Found joypad driver: "udev".

In the RetroPad section (see the full runcommand.log in the pastebin link below) it looks like the Start Button is mapped correctly. If the Start Button worked for me, I can see how to edit the config file to fix the button mapping.

For what it is worth, I first configured the Gamecube Controller without the xboxdrv and I had the same results; the Start, DPAD, A and B buttons worked fine in EmulationStation and seemed dead in the RetroArch emulator. Here is the complete runcommand.log

http://paste.ubuntu.com/26183051/

Thanks for your time.