[Floob]

You need to put roms in the directories to get other emulators to show up.
They may need to have the right extension as well.

Some info at the end of this video.

[Floob]

Have you tried a different usb connection? Is there a chance the controller is faulty – do you have another to try?

[Floob]

You may be able to change the font size etc.. in the theme?

Some info here:

[Floob]

For each system you want specific button mappings for, you would edit the retroarch.cfg file found here
/opt/retropie/configs/{systemname}/

and paste in the button config that can be found in your auto generated file(s) here:
/opt/retropie/emulators/RetroArch/configs

On that basis you could alter the autoload of config files value in the main retroarch.cfg as your system specific retroarch.cfg files would be loading that bit anyway. Although I guess it doesnt matter if you keep autoloading.

This may help

[Floob]

Ok – so a couple of things

– Not sure why *some* of those files are marked as executable.
Green filenames mean they are executable, you can also see this with the last ‘x’ in the permission strings on the left. None of mine are set to be executable.

– Datestamps
Its weird how all of your files have the same datestamp. I dont know how they all can have been written at the same time? I would expect the stock files in there to be 20 July as per the date on the 2.3 retropie image.

For a comparison, check the 6:16 point on the video above.

I would be tempted to re-install and check how they look from the outset, make one change and check the files again etc..

[Floob]

Actually thinking about it, it shouldnt matter as one is keyboard hotkey and one is joypad hotkey.

It would still be interesting if you compare your retroarch.cfg to mine – anything drastically different?

Also, does it make any difference if you take that blank line out of your auto file?

[Floob]

Perhaps when you use the auto file, it is importing it before the
input_enable_hotkey = “tab” line in your main retroarch.cfg file ?

Therefore it gets overwritten by the keyboard tab setting later in that file?

You could check this by putting it back how it was then run it and press tab and then a hotkey button on your joypad.

For reference, this structure works fine for me (uses hotkey in auto file no problem).
https://www.petrockblock.com/wp-content/uploads/2014/12/retroarch.txt

You can compare yours here:

https://www.diffchecker.com/

As a side note, I really need to work out if it cares about the button codes being in quotes or not. “”.

[Floob]

Yes – starting again could clean things up.
But I really cant help until you post the info requested above – the ls -lah command in that dir so we can see the filename and datestamp of your autoconfig file.

[Floob]

[quote=83942]Ok I have searched for a few days, and read every post and I still cannot figure this out. when I run retropie_setup.sh, and select SETUP, instead of finding the joypad (I have a logitec rumblepad 2), it finds nothing and says (and I quote) “The configuration file has been saved as .cfg and will be used by RetroArch from now on whenever that controller is connected”

I can get it to work if I configure it each time for each game, but that is a pain. what am I doing wrong?
[/quote]

That sounds like this error here:

Error with RetroPie Setup scripts

[Floob]

Maybe EmulationStation keeps detecting a new deviceGUID?

<inputConfig type=”joystick” deviceName=”PLAYSTATION(R)3 Controller (00:1B:FB:78:CD:70)” deviceGUID=”060000004c0500006802000000010000″>

Does it work if you use it wired?

If you configure it again, does the datestamp on that file es_input.cfg get updated?

[Floob]

It sounds like you are talking about the EmulationStation GUI saying ‘No Gamepad’
(Retroarch related files wont affect emulationstation)

This is saved here:
/home/pi/.emulationstation/es_input.cfg

If there is a permission issue on that folder/file it may cause it to always ask for new settings.

[Floob]

Yep.
You can write custom button mappings in each system based retroarch.cfg

/opt/retropie/configs/{systemname}/retroarch.cfg

This will overwrite any buttons set in the main (/all) retroarch.cfg

[Floob]

Yes, as laoracc says, try one button for the hotkey, and another for the action.
Here is an example:
https://www.petrockblock.com/wp-content/uploads/2014/12/USB2-axis8-buttongamepad.txt

So:
input_enable_hotkey_btn = “6”

is the hotkey, and everything below that is a hotkey based action.

[Floob]

You can have system specific configs for retroarch based emulators
/opt/retropie/configs/{systemname}/retroarch.cfg

That will overwrite values set in the /all/retroarch.cfg file

Also if you uncomment this, you can get a GUI in retroarch emulation

# Toggles menu.
# input_menu_toggle = f1

[Floob]

Cant say I’ve tried a PS4 controller – are you tempted to try a more retro USB based one?

I’ll see if I can try one out.

[Floob]

I’d be tempted to strip these lines out of your retroarch.cfg as you are using autodetect anyway (input_autodetect_enable = true)

The commands you have below will take priority over the autoconfigs – but best not to have two – plus you may need the “” around the buttons.

‘input_enable_hotkey = nul
input_player1_joypad_index = 0
input_player1_b_btn = 2
input_player1_y_btn = 3
input_player1_select_btn = 8
input_player1_start_btn = 9
input_player1_up_btn = h0up
input_player1_down_btn = h0down
input_player1_left_btn = h0left
input_player1_right_btn = h0right
input_player1_a_btn = 1
input_player1_x_btn = 0
input_player1_l_btn = 4
input_player1_r_btn = 5
input_player1_l2_btn = 6
input_player1_r2_btn = 7
input_player1_l3_btn = 10
input_player1_r3_btn = 11
input_player1_l_x_plus_axis = +0
input_player1_l_x_minus_axis = -0
input_player1_l_y_plus_axis = +1
input_player1_l_y_minus_axis = -1
input_player1_r_x_plus_axis = +2
input_player1_r_x_minus_axis = -2
input_player1_r_y_plus_axis = +3
input_player1_r_y_minus_axis = -3`

This may help

[Floob]

Can you go here:
/opt/retropie/emulators/RetroArch/configs/

and type ls -lah

Can you post the content of the file that has been autoupdated in there, along with its full filename? (It should have a fairly recent timestamp)

i.e. mine is
USB2-axis8-buttongamepad.txt

It starts with these lines which are quite important

input_device = "USB,2-axis 8-button gamepad  "
input_driver = "udev"

[Floob]

For what its worth there are a couple of sound related comments here for MAME
https://code.google.com/p/mame4all-pi/

[Floob]

Mame uses its own config file (for controllers etc..)
SNES/NES etc.. use retroarch.cfg

This may help:

Xarcade2Jstick – Map your Xarcade Tankstick to Game Pads and use it with RetroPie

[Floob]

This should help:

http://elinux.org/RPiconfig#Overclocking

Particularly this bit:
The latest kernel has a cpufreq kernel driver with the "ondemand" governor enabled by default. It has no effect if you have no overclock settings. But when you do, the arm frequency will vary with processor load. Non default values are only used when needed according to the used governor. You can adjust the minimum values with the *_min config options or disable dynamic clocking with force_turbo=1

This is worth a read as well:
http://megakemp.com/2013/02/26/adventures-in-overclocking-a-raspberry-pi/

[Floob]

To set the controller in MAME, just hit tab on the keyboard:

The fba config is here:
https://code.google.com/p/pifba/

Looks like it wants you to use the config.txt

[Floob]

The emulationstation controller file isnt used in games, its a separate one kept here:
/home/pi/.emulationstation/es_input.cfg

Can you post your autogenerated controller file?

Do you have many difference between your retroarch.cfg and mine?
You can see differences quickly here:
https://www.diffchecker.com/

My file is here:
https://www.petrockblock.com/wp-content/uploads/2014/12/retroarch.txt

This is an important section

# Enable input auto-detection. Will attempt to autoconfigure
# joypads, Plug-and-Play style.
input_autodetect_enable = true

# Directory for joypad autoconfigs (PC).
# If a joypad is plugged in, that joypad will be autoconfigured if a config file
# corresponding to that joypad is present in joypad_autoconfig_dir.
# Input binds which are made explicit (input_playerN_*_btn/axis) will take priority over autoconfigs.
# Autoconfigs can be created with retroarch-joyconfig, manually, or with a frontend.
# Requires input_autodetect_enable to be enabled.
joypad_autoconfig_dir = /opt/retropie/emulators/RetroArch/configs/

[Floob]

[Floob]

Check the bottom of this post:

Using overscan in RetroPie to fit video to your display

Its this value in the mame.cfg
display_border (I set mine to 24)

[Floob]

You can change the resolution the emulator kicks into in the es_systems.cfg

Basic guide here:

[Floob]

If you updated the retro-pie script this may be the issue:

Error with RetroPie Setup scripts

If you go in this directory and type ls -lah
/opt/retropie/emulators/RetroArch/configs/

do you see a file that has been updated recently?

Here is a working combination:

Working controller config files attached

Or as you say, pasting a valid button config direct into the retroarcg.cfg file in opt/retropie/configs/all should work

[Floob]

Thanks – I’ve just tweaked retroarchjoyconfig.sh in my version now, but I’ll advise others not to update the script unless they are planning on doing a full source based update.

The new upcoming version sounds great!

[Floob]

The error I get (and a few people commenting on my youtube vids) is
– Install 2.3 image to SD card
– apt-get update / apt-get upgrade
– run retropie script
– choose update script option

Then with the updated script it no longer runs the joypad script when chosen through the setup script (Setup | Configure RetroArch controller)

So the issue is when you update the retropie script to get the latest updates it prevents the configuring of usb controllers. (unless you do a full source based install)

Do you think I should just run the stock 2.3 image instead – would I be losing much /anything by not using the latest script?

[Floob]

You could try pasting your auto config into the main retroarch.cfg file and see if it works there.
Did you try removing that blank line?

[Floob]

You can change the config back here:
/opt/retropie/emulators/mame4all/mame.cfg

I imagine if you rename that file a new one would be created if you dont want to edit it.

[Floob]

Long shot, but try removing that blank line.

Also, how does your retroarch.cfg compare to my working (with auto config file) one here?

Working controller config files attached

Also, in your example you dont have Start set to exit the emulator? You have l2 set too do that?

[Floob]

Yep – I’ve never used composite video out, the instructions show how to update to 640×480 (VGA). This is done in the es_systems.cfg file – which will load the games in that res.

[Floob]

Using overscan in RetroPie to fit video to your display

[Floob]

I’ve put some info here about setting it to VGA in EmulationStation

[Floob]

Dont bother compiling it – just download the ready made rpi version here:
https://github.com/sselph/scraper/releases

[Author]

Posts