RetroArch: Automatic Frame Delay to reduce input latency

Re:RetroArch: Automatic Frame Delay to reduce input latency by poglet on Wednesday June 08, 2022 @04:35AM (#31664744)

I've spent hours and hours trying to get controls working correctly in RetroArch. There are independent controls for the menu, cores then individual roms.

There have been so many times where I've accidentally locked myself out of the menu controls causing the need to SSH into the device to fix it up.

[ Parent | on HN ]

Re:RetroArch: Automatic Frame Delay to reduce input latency by fb03 on Wednesday June 08, 2022 @05:02AM (#31664879)

RetroArch is very nice but I do agree with has sadly fallen into MAME input configuration territory. All it needs is better defaults.

[ Parent | on HN ]

Re:RetroArch: Automatic Frame Delay to reduce input latency by pezezin on Wednesday June 08, 2022 @06:47PM (#31675402)

Maybe I haven't found the right settings, but I would say that RetroArch is significantly worse than MAME. MAME will show you the relevant inputs for the running machine, whatever they are: sticks, trackballs, button, pedals, you name it. RetroArch will show a generic configuration menu without taking into account each machine's peculiarities.

For example, I have a Megadrive-like 6-button controller and I'm trying to configure a Megadrive core... no luck, you can only configure an SNES-like controller with A, B, X, Y, L and R. Where are C and Z? Apparently you need to hand-edit some text files, and pray to the Machine God that it will work.

[ Parent | on HN ]

Re:RetroArch: Automatic Frame Delay to reduce input latency by j-james on Wednesday June 08, 2022 @05:46AM (#31665139)

I think the move to Ozone as the default UI was a big step forward in this regard.

[ Parent | on HN ]

Re:RetroArch: Automatic Frame Delay to reduce input latency by willis936 on Wednesday June 08, 2022 @06:42AM (#31665470)

Boy howdy do I know this pain.

Even worse is initial setup can't bootstrap without M+KB.

[ Parent | on HN ]