Copy controller settings
-
Pi Model or other hardware: (B, B+, 2 B, 3, X86 PC etc..)
Power Supply used: (If using a Pi)
RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest):
Built From: (Pre made SD Image on RetroPie website, Berryboot, or on top of existing OS etc.. - please provide the filename of any image used)
USB Devices connected:
Controller used:
Error messages received:
Log found in /dev/shm/runcommand.log (if relevant):
Guide used: (Mention if you followed a guide)
File: (File with issue - with FULL path)
Emulator: (Name of emulator - if applicable)
Attachment of config files: (PLEASE USE PASTEBIN.COM FOR LARGE LOGS)
How to replicate the problem:This is what we'd like you to fill out.
-
@CodeDrawer said in Copy controller settings:
Pi Model or other hardware: (B, B+, 2 B, 3, X86 PC etc..) Pi3 Model B (Quad core CPU 1.2GHz, 1GB RAM...)
Power Supply used: (If using a Pi) Official 2.5a PSU
RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest): 4.2
Built From: (Pre made SD Image on RetroPie website, Berryboot, or on top of existing OS etc.. - please provide the filename of any image used) - Premade SD image on 4.1 then upgraded via update menu on pi
USB Devices connected: USB mouse and keyboard
Controller used: Bluetooth s600
Error messages received: None, the controller will just not work. What will happen is the ROM will start and the keyboard sometimes seems to take over, although I will only be able to use a small selection of keys. I can't exit out or anything having pressed all buttons on keyboard.
Log found in /dev/shm/runcommand.log (if relevant): Can't get to this just now
Guide used: (Mention if you followed a guide) There were various guides about trying to reprogram the controller via retroarch but i couldnt follow them
File: (File with issue - with FULL path) All roms experience this issue
Emulator: (Name of emulator - if applicable) All emulators experience this issue
Attachment of config files: (PLEASE USE PASTEBIN.COM FOR LARGE LOGS). Can get this later, is there a specific path ?
How to replicate the problem: Start any game.This is what we'd like you to fill out.
So basically what happens is as above. Originally when I got retropie installed and turned on, emulationstation asked me to map the controller - which works fine. I can navigate between all emulation station menus no problem, but whenever I start any of the ROMS the controller seems to just become dead, if i plug my USB keyboard in I can use that, but with very very limited functionality - tab wont work, esc wont work. The arrow keys do but nothing else really.
-
@Rudy I can't help you there... maaaayyyybe going to the controller config file?
-
@CodeDrawer so how do i do that ? total retropie newbie
-
https://github.com/retropie/retropie-setup/wiki/RetroArch-Configuration
There is a place to go. Let me dig some more.
-
/opt/retropie/configs/all/retroarch-joypads Is the file. Do you know how to use linux terminal?
-
tell me the commands and i'll have at it !
-
Ok so once you boot up you get the front end of emulation station. You press f4 to drop out to terminal.
So the first command is
cd /That will bring you to the root folder, or directory.
The/es in the path name, indicate a folder. So after thecd /you typesudo nano /opt/retropie/configs/all/retroarch-joypadssudo part gives you god-like privileges. The nano part, is the program to edit the file, it is very old and uses archaic commands, but it is a good text editor. The other part, shows the computer where to look. I can bring you that far by my self. I'll come on later! :-) -
I had this exact same issue with a generic bt controller I had purchased. I mapped the controls in emulationstation but no roms would recognize the controller. I had to go into RGUI with a keyboard in each emulator and then change the input and map each key specific for that emulator. It was handy as it fixed my problem but also allowed me to set keys specific for separate consoles. The only one I haven't mastered is mupen64plus ( better n64 emulator). Even with a keyboard I couldn't access the RGUI.
Hope this helps!
-
@CodeDrawer said in Copy controller settings:
Ok so once you boot up you get the front end of emulation station. You press f4 to drop out to terminal.
So the first command is
cd /That will bring you to the root folder, or directory.
The/es in the path name, indicate a folder. So after thecd /you typesudo nano /opt/retropie/configs/all/retroarch-joypadssudo part gives you god-like privileges. The nano part, is the program to edit the file, it is very old and uses archaic commands, but it is a good text editor. The other part, shows the computer where to look. I can bring you that far by my self. I'll come on later! :-)ok, so should I download these files and upload them as .zip ?
@incrediblekyle said in Copy controller settings:
I had this exact same issue with a generic bt controller I had purchased. I mapped the controls in emulationstation but no roms would recognize the controller. I had to go into RGUI with a keyboard in each emulator and then change the input and map each key specific for that emulator. It was handy as it fixed my problem but also allowed me to set keys specific for separate consoles. The only one I haven't mastered is mupen64plus ( better n64 emulator). Even with a keyboard I couldn't access the RGUI.
Hope this helps!
How do I get into RGUI ?
-
@Rudy you use a keyboard and act like you're going to play a game. One the rom has started I believe that it is whatever you have mapped as Select and X pressed at the same time. I'm trying to find the github article I used to help but coming up with nothing
-
i just had a problem with a non official image of ES and RP. the controller wouldnt work in any of the emulators, I now have it working by copying a working config file into the retroarch config folder.
i did the following in order to copy a working config from one image to another :
1)enable SSH
2)SHH into the pi using the username :pi and password: raspberry.
3) enter the following:
cd /opt/retropie/configs/all/retroarch-joypads and hit enter
4) type ls (lowercase L and lower case S) and hit enter
5) you should see a list of the config files for all gamepads on that system. in my case I saw only one config file without the correct name.
6) put a working image on an SD and insert into the pi.
7)SSH into the pi and type the following : sudo nano /opt/retropie/configs/all/retroarch-joypads
hit enter
8) choose the config file that you want to copy to the harp64 image, in my case the sony dual shock 4 and type :
sudo nano /opt/retropie/configs/all/retroarch-joypads/SonyInteractiveEntertainmentDUALSHOCK®4USBWirelessAdaptor.cfg
hit enter, replace the sony config file with the name of the one you want. this will open the file. select the text you need (all of it) and copy it CNTRL + INS. save it in a text file for later,
9)put the harp64 image back into the pi, ssh into it, type sudo nano /opt/retropie/configs/all/retroarch-joypads/SonyInteractiveEntertainmentDUALSHOCK®4USBWirelessAdaptor.cfg
Because the file doesnt exist you will see the text "new file" paste all of the text you have in the clipboard with a right click from the mouse,
10) save and exit with CNTRL + X and then reboot the pi by entering sudo reboot into the ssh terminal -
@incrediblekyle said in Copy controller settings:
@Rudy you use a keyboard and act like you're going to play a game. One the rom has started I believe that it is whatever you have mapped as Select and X pressed at the same time. I'm trying to find the github article I used to help but coming up with nothing
That's the problem - no idea what has been mapped seeing as the controller and only a few buttons on the keyboard work. Someone said backspace and x would do something or tab and x but neither of those worked.
@spruce_m00se said in Copy controller settings:
i just had a problem with a non official image of ES and RP. the controller wouldnt work in any of the emulators, I now have it working by copying a working config file into the retroarch config folder.
i did the following in order to copy a working config from one image to another :
1)enable SSH
2)SHH into the pi using the username :pi and password: raspberry.
3) enter the following:
cd /opt/retropie/configs/all/retroarch-joypads and hit enter
4) type ls (lowercase L and lower case S) and hit enter
5) you should see a list of the config files for all gamepads on that system. in my case I saw only one config file without the correct name.
6) put a working image on an SD and insert into the pi.
7)SSH into the pi and type the following : sudo nano /opt/retropie/configs/all/retroarch-joypads
hit enter
8) choose the config file that you want to copy to the harp64 image, in my case the sony dual shock 4 and type :
sudo nano /opt/retropie/configs/all/retroarch-joypads/SonyInteractiveEntertainmentDUALSHOCK®4USBWirelessAdaptor.cfg
hit enter, replace the sony config file with the name of the one you want. this will open the file. select the text you need (all of it) and copy it CNTRL + INS. save it in a text file for later,
9)put the harp64 image back into the pi, ssh into it, type sudo nano /opt/retropie/configs/all/retroarch-joypads/SonyInteractiveEntertainmentDUALSHOCK®4USBWirelessAdaptor.cfg
Because the file doesnt exist you will see the text "new file" paste all of the text you have in the clipboard with a right click from the mouse,
10) save and exit with CNTRL + X and then reboot the pi by entering sudo reboot into the ssh terminalCan this be done via ftp ?
-
If it helps I get 0/0 not configured down the bottom of the screen when I load the rom
-
Got it sorted guys, had to mess around quite a bit and then eventually had to bind the keys via the retroarch menu.
all good now and thanks for your help !!
-
@Rudy Great! Glad to help the little I could! ;)
-
@Rudy did you get it working for all systems? I struggling with n64
-
@incrediblekyle second that, I cant get n64 to work yet, I need a working config file for the ds4 on the n64
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.