One final note...

I had been doing all of my testing on an x86 platform. Since moving the scripts/overlays to my RPI4, I had to increase the sleep outside the loop to 2 otherwise it wouldn't pause.

#! /bin/bash while ! pgrep retroarch >/dev/null; do : sleep 1 done sleep 2 echo -n "PAUSE_TOGGLE" | nc -u -w1 127.0.0.1 55355

@Kaydron said in Issues with NetPlay: Client cannot connect when going through RetroPie:

I found this post that has very similar symptoms https://github.com/RetroPie/RetroPie-Setup/issues/3161.

If you're encountering the same problem as the the one described in the issue, then there's no solutio yet, just the workaround posted in the same issue. The only method that seems to work is to directly connect by specifying the hostname.

@mitu Yeah, I meant just for the cases that I can't control. I'll be shutting it down properly from now on. Thanks for the help!

I did a similar project not too long a go. E.g. built RetroPie into Atari 2600 case. Anyways - yes, key presses that ControlBlock sends when using MAME layout are hardcoded into it's driver:

URL: https://github.com/petrockblog/ControlBlockService2/blob/master/src/controlblock/gamepads/MAMEGamepad.cpp#L41-L141

To change e.g. switch 'z' to send something else than z, say a, you would modify lines below and replace KEY_Z with KEY_A. And recompile and re-install the driver (instructions here https://github.com/petrockblog/ControlBlockService2).

URL: https://github.com/petrockblog/ControlBlockService2/blob/master/src/controlblock/gamepads/MAMEGamepad.cpp#L68-L70 to

Available KEY_* events (that you could replace KEY_Z above) are found from here: https://github.com/petrockblog/ControlBlockService2/blob/master/src/controlblock/uinput/UInputEventCodes.h

I hope this helps you forward. I did a slight re-write for the driver myself as I wanted all the Atari 2600 switches to provide their original functionality. Which isn't straightforward since official ControlBlock driver doesn't support switch where both on and off indicate certain state (e.g. on -> colorTV, off B&W). I suppose I could clean up my code a bit and put it up to github sometime.

Thank you so much!

@mitu I've enabled both the options u showed in your post. It successfully. I was quite baffled because I saw the the Dt overlay option twice in the end of my boot config.

Thank you for your help

@sonicman2020 with respect, your understanding of the runahead settings, and the audio latency settings are very wrong. if you want to get this working properly, please start again from the retropie image, and don't change such settings: https://retropie.org.uk/docs/First-Installation/

@nicshoe18

I had to add usbhid.quirks=0xf000:0x0008:0x100000 to /boot/cmdline.txt and then reboot to get jstest detect the missing buttons.

@skrilmps said in can't access MAME 2003+ (libretro) in-game menu:

cy

no problems at all always use then menu to set options code can change any time.

You nailed it; once I deleted the shaders folder from retroarch, the update went through without issues.
Thanks!

@mitu nvm, I shall just reflash the retropie pre-built image.

Thanks!!! That solved the problem!

@pinacolada Ok so I think I've resolved this.

Firstly, I took advice from a YouTube video which described how to update RetroPie itself - this took me to the following screens:

Update Remote Setup Script Basic Install Perform Reboot

It took a while, and looked like some errors occurred during the install, however...it did come back up, and now the hotkey + right trigger DOES load from the save slot.

So I guess the root cause here was an older version of Retropie.