@buzz Am aware, but i didnt know what the issue was. Thanks.

@SuperPitendo said in rpie-preservatives - Save file remote backup & synchronization tool:

@LiquidDivide I am glad that I could help. Thanks for pointing out the differences, especially the point with the non-retropie devices and that nothing has been done on the other script for 2 years. This should make your script much more interesting. Do you plan to include a save state selector as well?

Yes and no. If something works well, there's not really a need to keep changing and updating it. The other script does still work well and I had minimal issues with getting it working again, though I added a few changes from one of the other forks as well. I'm happy with it for now, but if this script gets more features, more robust, I'll happily switch.

Oops just found it (here: opt/retropie/configs/all/emulators.cfg)

Sorry, topic closed!

@mitu Thanks! :Banghead: Now that was a typical case of "Betriebsblindheit" (1) inmidst my current setup orgy - Sigh. Should have also tried 'em without the bindings 1st. !

[1]: I never came along a real translation for that, but Target fixation or Tunnel vision (metaphor) may come close to it.

@goldug said in Runcommand messes up resolution for some reason:

because I hadn't changed anything, but yes, it seems there is now for some reason.

You added something, there is nothing in stock RetroPie that creates those files automatically.

@CapNinja said in 3 Questions, 1 Noob:

But I want to save the image scaling to all games in that system. Is that not possible?

It is, the same Overrides menu has a Save Content Directory override, which saves the settings for the entire folder.

@BuZz editing /opt/retropie/configs/all/runcommand.cfg did the trick, thankyou! :-)

@BuZz Thanks, BuZz. I am using a 3rd party image, so I am exempt from assistance. I'll try elsewhere...

@WeirdH I fixed that issue by using brackets around the code.

renamed it and it still works
I don't know what the problem was but renaming it seemed to make it work

@keith-f-kelly said in Enhancements for Dialog Navigation/Controls:

I don't see why any button needs to be mapped to the TAB key. TAB doesn't appear to be used anywhere in the menus. Am I missing something?

The physical key Tab is by default mapped to traverse the button selection (in the bottom area) in retropie's dialogs. More generally it is mapped to traverse the input fields/controls of the different widgets available in a dialog.

For 0x0a / 0x0d: I do not stick to 0x0a I just took what was there, maybe it is the cleanest to sent the terminfo's cr instead of 0x0a or 0x0d.

@mitu I have attempted that but you dont have to wait to when using the up down left right arrows, i have tested this and it works before the time runs out

@mitu said in runcommand verbose logging:

Since this is a RetroArch option, I guess you can enable it from the RetroArch settings or add it to its configuration file.

Thats what I did. But, as a shot in the dark I added verbose = "1" to the /opt/retropie/configs/all/runcommand.cfg file and that seems to work. Undocumented feature?

@mitu Yeah -- there's no error message readily available when the runcommand dialog isn't shown. I should probably just do a clean install since that is the recommended route, likely something didn't upgrade correctly at you say.

Yeah it's not. That was another reason why I went the dispmanx route. As it would have required adding X dependencies everywhere and additional logic. When I get around to making it configurable, my plan is to also handle the dependencies aspect. But I also wanted to do more work on this first.

On a code level this would be in a similar fashion to the recently added dependency aliases. This exists already for kernel headers. But it will be expanded. Just simplifies module coding as for example kernel header naming differs between Debian/Ubuntu. A module can now just ask for LINUX-HEADERS and the core code will install the right packages. I wanted this for the X dependencies also - but transparent to the module. The module would specify some flags which would advertise which backends it works on. And the rest would be done automatically.

Rushed explanation, but this is why it's not done yet as it requires some reworking of existing code.

It was indeed an issue related to the format of the runcommand-onstart.sh file - it was in DOS format. I opened/resaved it in MAC format (using nano). Problem solved. Thank you for your help!

Feh lets you configure its actions for keyboard keys and mouse buttons. See its manpage for further information, and this post in the official Raspberry Pi forum. The action to exit feh is called quit in its configuration files.

So, maybe you could configure a quit key in feh and set a very high delay time in Retropie. Just an idea after a little research, I don't have any practical experience with this.

I've just had the exact same problem this morning and thought I was going mad!

This is actually a great feature as it provides further protection against guests inadvertantly entering it even after applying Kiosk mode.

Many thanks Mitu!