@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.

@mitu said in N64 Controller Setup - Inconsistent Documentation:

@busywait said in N64 Controller Setup - Inconsistent Documentation:

If you don't have a 'retropad A' button defined, of course it's not going to work in the menu . My remark was:

How the button is mapped to the underlying core doesn't matter for the menu (RGUI or otherwise).

I agree, but the reason that I don't have a retropad A button defined is because the core doesn't use it for it's logical function in the mapping. I could have had both [N64 "A" and RGUI "A"] if the core used different bindings.

Obviously this is a minority problem for people trying to use pads without the full set of retroarch inputs, and I can still navigate the RGUI using a keyboard in my case :)

While testing Scummvm 2.5.0 I bumped into this issue too --- seems to be specific as said here to lr-scummvm's interaction with RetroArch as loading titles explicitly with the non-lr version of ScummVm works.

Not sure exactly when this broke, but my RPi3B downstairs works fine on RetroArch 1.8.8 and my 4B on 1.9.7 doesn't work. Tomorrow I'll try to upgrade my 3B to the latest lr-scummvm just to see if it still works, just because I'm curious.

Anyone else hitting this, and have a way to work around without downgrading? Lr-Scummvm is much better for input. It might be tracked here:

https://github.com/libretro/scummvm/issues/183

In 1.9.4 you can selectively disable the notifications shown on screen, so you could remove the messages shown on startup by adding

notification_show_remap_load = "false" notification_show_config_override_load = "false" notification_show_autoconfig = "false" notification_show_set_initial_disk = "false"

to /opt/retropie/configs/all/retroarch.cfg.

@roslof @mitu

Thanks for exploring this one - I assumed that my RetroPie upgrade had overwritten my retroarch.cfg files. The advice here has fixed my missing shaders in my install (a 64-bit Raspberry Pi OS install).

Running and updating the setup script, navigating
P Manage packages
C Core
43 Retroarch
U Re-install (from source)
has fixed the problem for me.

@itsthex said in Controller Issues - Buttons Inop, Controls change:

I picked up a Vilros Pi 4 kit to use with VMAN's 512gb image. Consensus seems to be that one shouldn't use a prebuilt image, but I figured I couldn't go wrong with what was seemingly regarded as one of the best. And, so far so good!

We don't support 3rd party images. Ask the author(s) of the image for support, or use the image from retropie.org.uk/download.

@mitu
i have created an suggest on libretro github

https://github.com/libretro/RetroArch/issues/12434

I don't know if it's the correct ways but i was already registered on github so why not try :)

If you know someone on libretro/retroarch developers team pass the suggest to him :)

@gabbo999 said in Retroarch input setting problem:

I have a Raspberry pi4 with obviously retropie installed, I finished today to build my cabinet and I wanted to set all the right buttons for each emulator.

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

In N64 emulator i went in the Retroarch quick menu and i noticed that in port 1 controls B button and Y button are both button 3, same A and X both button 1... (see photo attached)

Actually, the B/Y buttons are not mapped at all - the right side (which shows the emulated system's mapping) is empty. How did you configure the gamepad ?

@mitu
Just reinstalled them, same thing.

Ah well, it doesn't seem to be RP or upstream in retroarch, seems to be entirely at my end. .

The only thing I can think of is I installed some Ubuntu-studio stuff to get jack/Guitarix working, though I had it before too. I'm guessing whatever is different and is allowing them to work (sort of) this time is some how breaking something else.

@greenhawk84 The line you're looking for is "video_font_enable." What FroyoXSG recommended doing is going to RetroPie -> RetroArch from the main system-select menu. Then, when the RetroArch menu pops up, you can go to

Settings -> On-Screen Display -> On-Screen Notifications

In there, "On-Screen Notifications" are the little text messages you see at the bottom of the screen, while "Graphics Widgets" are those more elaborate boxes telling you about remap and other files being loaded. You can set each to "OFF." I'm not sure what the corresponding line in the config file for the widgets is.