@dandelion said in retroarch.cfg scripting help:

I added those lines in the retroarch.cfg file found in /opt/retropie/configs/atari2600. As I mentioned, only the last line worked.
input_exit_emulator_btn = 5

I think it worked just because 5 is already mapped through an auto-configuration file.

I guess that's what I'm looking for -> is there some master list somewhere of the syntax for the retroarch.cfg file vs. the autoconfig files? Or is that a learn linux kind of task?

It's not Linux specific, it's just the RetroArch configuration syntax. For auto-config files, you don't need to set the playerX part, e.g. input_exit_emulator_btn is ok, but when configuring the button in retroarch.cfg file you need to specify the player #, e.g. input_player1_exit_emulator_btn.

I was just thinking that instead of using the EmulationStation menu by pressing Start, scrolling down to Quit, selecting Quit, and then scrolling down to Shutdown System, et al. that I could hot-key/map some of the buttons to do ALL of that. Not necessary - just the cat's pajamas

In EmulationStation this kind of 'hotkey'/shortcut is not available, at most you can exit emulationstation (no questions asked) with F4, but you'd need a keyboard for that.

@icebear81
Nice. I want to get a Sinden lightgun sometime. I guess I'm out of ideas since I haven't used one before. I thought I read on his site that you have to install some custom software or driver to make it work with the border around the screen.

Maybe someone else who has one might have some ideas. To me it sounds like there is some configuration specific to the way the lightgun detects whether it is pointed at the screen or not. On the original NES Zapper it would select game modes if pointed away from the screen and start one if it was pointed at the screen.

@mitu. To clarify, I meant the version I am running - not that the file originally came that way.

Not exactly a problem, just excess from my learning/stumbling through, and wanting to clear out the clutter.

@bollwerk said in How to configure both analog stick and d-pad for retroarch arcade config?:

I assume the Arduino config (or any joypad input config) overrides the retroarch.cfg in some way?

Your configuration in retroarch.cfg - as it is right now - configures a keyboard.

input_player1_r = "w"

When configuring a gamepad, the syntax is different:

input_player1_r_btn = "12"

RetroArch will load - indeed - the configuration from the autoconfig sub-folder if it finds one. The gamepad's auto-configuration file was generated by EmulationStation when you configured the gamepad in the Input Configuration step.

I find it easier to open up the RetroArch's menu (via Hotkey + X) and use the Controls menu to change things, test them and then save it with a Core input configuration remap.

For more details, see https://retropie.org.uk/docs/RetroArch-Configuration/.

Apparently this is an issue with the SN30 Pro itself. I got it working. Here's what I did:

Deleted /etc/udev/rules.d/99-bluetooth.rules Deleted SN30 Pro from registered Bluetooth devices Powered on SN30 Pro with Start+B (Android mode) and held Pair button (top of controller) for 3 secs to immediately go into pairing mode. While in pairing mode selected Register and Connect Bluetooth Devices in RetroPie-Setup Script >> Setup >> Configure Bluetooth Devices Selected 8Bitdo SN 30 Pro from list and finished config Did NOT set up udev rule

Now the controller is working perfectly; I'm able to open Launch Menu or go straight into games ... no sitting at black screen for ~40 secs. Also no waiting required to navigate script menus either.

I did have to reconfigure controller layout ... and the L/R triggers are actually recognized now as well.

@sad_muso I would add, that it's better imho to edit the global file manually or via the RetroPie menu -> configuration editor (which has some of the settings but allows manual editing also)

Reason being that saving out from retroarch saves every possible setting. All config file "comments" will be lost, and it's a lot of config entries. It won't be easy to know what you have changed if you ever need to check.

But of course you can choose the method you prefer.

@roslof
Did that, but nothing changed.
I have no idea where else to look.
Talk about frustrating.

Without seeing a log file - /dev/shm/runcommand.log - or the actual configuration file, it's difficult to say what is wrong. The default configuration file installed by RetroPie should always work (retroarch.cfg.rp-dist).

Also, please add the info requested in https://retropie.org.uk/forum/topic/3/read-this-first.

system_directory should be "~/RetroPie/BIOS". I think it defaults to the current content dir (ROM folder) if not set.

@mitu Never used Reset, at least that I know of. But thanks for that tip. I'll be sure to avoid it.

@sirhenrythe5th said in Amiberry screen position:

Done, works great!
Thanks again for supoort @davidgrohl

Great! I’m glad it helps.

@snock said in retroarch.cfg global and core.:

So if the roms is executed, and automatically the retroarch.cfg of the specific system (turbografx cd) is modified and many configuration lines are added.

That's because you've activated Save on Exit in RetroArch's RGUI for that system or maybe you've reset the configuration file from the RGUI - on exit, the simple retroarch.cfg for that system is overwritten by RetroArch.

@Thorr69 Sure is Ir-Fba Alpha, Ir-Nestopia, Ir- Snes9x 2010

That’s what I get for coding when tired! Thanks for the quick response. All is in fact working as intended...

Thanks again

I have reset EmulationStation input configuration (Retropie Setup -> Configuration / tools -> emulationstation -> Clear / Reset Emulation Station input configuration), after all previous actions and everything now works as after fresh install.

Thanks @mitu .. Found at least one of those as well -- those are dating back quite some time, hence why I wanted to ask if was a possibility. Ill figure some workaround - -

@Clyde Thanks. And for anyone following up this question I was easily able to add audio volume control (via hotkey + D-pad up/down) to the config file mentioned earlier. Like this: input_volume_up_axis = ”” inside the quotation marks I copied the number for the up axis, which was -1 in my config file.