Ok apparently there is a compatibility issue with the display driver, because if I uncomment that the display doesn't work. They have drivers that are compatible with Retropie on the Rpi3 but not the Rpi4 yet. I guess I'll reach out to them and see if they have a solution

@notthesame can you post the link where they said the error was fixed?

Yes, I figured so much. I was asking if it will ever be available for environsments that are not running X, but I guess as soon as it is ready, people will make the effort to implement it to Retroarch.

@gizmo90 said in Retroarch Integer Scale setting not saving: Any idea why the cfg file is being ignored? If you're running a custom image, then we don't know how it was modified or configured from a stock RetroPie image.

@etheling excellent work. Looks really slick on the side-bars there.

@MrShanksio the 2 best SBCs in 2020 (well, they already were in 2019, before the pi4 was even out) are those 2 : Odroid N2 => best all rounder (better cpu & gpu than pi4) Jetson Nano => best gpu, decent cpu (cpu between pi3 & pi4) NB : idk if retropie can be installed on those SBCs, but that criteria wasn't included in your question, and there are other retrogaming distros with support for those boards. NB2 : you won't play PS2 on a SBC in 2020, but systems like Dreamcast/Naomi/Atomiswave and Saturn will run fine on the 2 SBCs i mentioned (full speed + upscaling).

Great news! (I hope.) As nice as it is to have it at all, RetroPie's launching artwork always nagged me by pausing the loading process without any way to end it prematurely by pressing a button. My own attempts to decouple them from runcommand weren't crowned with success, and @johnodon's solution is elegant, but rather complicated. It would be nice to have a simple native RA function for that.

@mitu After remapping the controller as you stated and reviewing the config file, I tried holding Select then pressing Start, and it took me out of the game. Similarly, holding Select and pressing left bumper loaded state. In short, it seems to be working. It appears my understanding of the hotkey was incorrect. I thought you simply pressed the hotkey only to bring up the GUI. Thank you for your help and work on this forum.

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/

To me is looks like the gamepad is not correctly detected and configured by the OS - so no amount of configuration will make this work if the kernel doesn't properly detect it. Hence the suggestion to try and see if you have the same issues with an older build.