@rhino said in RetroArch version:

So after using one of prebuilt images you end up with proper distro and can stay up-to-date by re-running the script and there's no need to reinstall even after major Retropie releases?

Pretty much yes. At some point though the current OS (RasPI OS) becomes unsupported (both upstream and by RetroPie) and you'll have to upgrade your OS by installing a new image.

@lamaman1971
I'm no expert, but I think RetroArch can only have one mouse index per player. So I don't think you can assign two of these devices at the same time through the menu. If it were possible to somehow make the operating system see two input devices on the same device index that would be one way. I have no idea how to do it though.

I think as painful as it may be, the only thing to do is assign whichever device the most games use as the default and then create game specific overrides for those that use the other device type.

I have found the holy grail in this repo line:
https://github.com/meleu/RetroPie-joystick-selection/blob/master/jsfuncs.sh#L345

Basically in order to change the index, we should just edit /opt/retropie/configs/all/retroarch.cfg at this line:
input_player1_joypad_index = "some_index_number"

or whatever input player you want. NOTE: i didn't tested it yet, but this might work.

@kelvinator3300 I found this but the links are broken. This is exactly what we want. We should definitely look into this amazing tool!

https://opium2k.tumblr.com/retroarch-readers

@dankcushions

Thank you very kindly on the response to this. :)

@roslof Thanks Roslof. I didn't know your spreadsheet already reflected an overclocked Pi.

RetroArch's version is pinned in the install script, installing from source will still get you the pinned version. If you update your RetroPie-Setup script, the latest version available will be 1.9.7.

If you wish to build the latest master or and another version, you need to modify the retroarch package script and change the branch used here. Note that RetroPie applies some patches to the source (here), if they don't apply correctly to the version you want to build, you'll need to comment the patches before installing from source.

@mitu I did indeed configure my controller when I first booted up. Had to re-do it a few times because I was having issues with the blue tooth. I guess I must have mucked something up when I re-configured my controller, because I went back to re-configure my input from the emulationstation ui just to make sure, and now the problem is fixed, I feel like such a dope for not trying this, thanks.

@bdpyle sorry, i don’t understand the question. configuration editor IS for retroarch (ie, libretro cores)

@gaz I am out of ideas here, and having never used the Lightgun outside of the Raspberry Pi, I would definitely suggest bringing this back to the Sinden Lightgun discord, as Andy will likely be able to best help troubleshoot the scenario.

Specifically, if the gun works in other software such as the test apps, it might be something simple that I am not knowledgeable enough nor experienced enough to detect. The Linux-specific channel there might be the best to get to the bottom of this, but do share whatever you find here, as if there's something that we can change on our end I suspect we'll be happy to accommodate.

Sorry about that.

@skykid said in Despair over controller ports constantly swapping:

I hear setting up Samba on OSX is a ballache, which is why I was looking for an easier option.

It's not, you can access the RetroPie shares from macOS without any issues:

open Finder, select "Go" menu and "Connect to Server". Type smb://retropie and hit "Connect".

@mitu That did the trick! Appreciate all the help!

@bdpyle duplicate of https://retropie.org.uk/forum/topic/31061/psx-and-psp-games-won-t-start-after-adjusting-retroarch-settings ?

@bdpyle Word of advice - don't use 'Reset Configuration' in RetroArch, the defaults it creates are not best suited for a Pi/RetroPie installation.

Thank you everyone for your feedback and suggestions! I think I figured out what is causing the conflicts I am experiencing, for which I'll reference the following screenshot of the mame input configuration for sf2.zip:

sf2-210802-174734.png

My rebindings are attempting to "relocate" buttons, assigning buttons 1->2, 2->3, 3->6, etc... (as noted before). The end result is that only the RetroPad bindings changed, not the keyboard key bindings. The OR clause in the mame mappings thus maps one key/button to two events and that ends up breaking things!

@dankcushions said in Unable to configure per-ROM input override for MAME:

point of order, but they do, but it relies on you using the correct physical location or your buttons:

B A R
Y X L

I had not considered this, but this seems very sensible given mame's default inputs (key or retropad event). I had have wired things using the IPAC switch numbers, which won't be hard to change.

1 2 3
4 5 6

EDIT
Here is a post descripting this same problem, which is due to the "simultaneous" core input setting in retroarch:

https://retropie.org.uk/forum/topic/29976/mame-button-mapping-conflicting-with-retroarch-button-mapping

@denyou I just got this working with @sleve_mcdichael's help on reddit. See if there's anything in that thread that helps or drop back in and I'll try to walk you through it here. It works like a charm and is a really great feature.

@nevsan please fill out ALL of https://retropie.org.uk/forum/topic/3/read-this-first including image file name and verbose log.

@fadangalini to be honest manually changing the files is not recommended. you should bind your default during https://retropie.org.uk/docs/First-Installation/#configure-controllers, then any overrides for specific consoles via https://retropie.org.uk/docs/RetroArch-Configuration/#core-input-remapping

/dev/shm/retroarch.cfg is here:
https://pastebin.com/embed_iframe/YyUgG611

this isn't a verbose log.

@mitu said in Warning, Parsing error for "controller"::

@mth75 the parsing error thrown by joy2key should be fixed by https://github.com/RetroPie/RetroPie-Setup/pull/3370

The underlying problem seems to be the RetroArch's auto-config file being incorrectly generated by EmulationStation. Is you left analog joystick working in games ?

@mitu Thx mate, problem solved

@dankcushions said in Need lr-MAME2003 core options for config file:

input_overlay_enable_autopreferred = "false"

Tried this, doesn't work from the local overlay/scaling file that is associated with the rom in the rom folder.

Seems MAME2003 is not reading this file for the overlay size specs anymore. Previously, you had to make a config file that pointed to the overlay, then the scaling and and opacity was set there as well. Did something change because it's not reading this file for those settings anymore, even with the auto-scaling "off" in the On-Screen Overlay menu. The overlay shows, but it's scaling is all screwed up because it only reads the settings in the core retroarch.cfg.

I does read everything else in this file though.

005.zip.cfg

video_shader = "/opt/retropie/emulators/retroarch/shader/arcade-bezel-shader/crt-pi-vertical.glslp"
video_shader_enable = "true"

input_overlay = /opt/retropie/emulators/retroarch/overlays/arcade-bezel-overlays/005.cfg
input_overlay_enable = true
input_overlay_opacity = 0.900000
input_overlay_scale = 1.000000

custom_viewport_width = "741"
custom_viewport_height = "933"
custom_viewport_x = "589"
custom_viewport_y = "70"

video_scale_integer = false
input_overlay_enable_autopreferred = true

**** nevermind... I see what's changed... it's PORTRAIT now. It's reading that setting just fine.

I deleted the old retroarch.cfg and allowed it to rebuild a new one, and there it was.