@setiawan for that issue (if it is the same), just disable widgets is the easiest solution for now - https://retropie.org.uk/forum/topic/26322/pi-4-display-issue-with-lr-genesis-plus-gx

regarding the crash, not really sure what it could mean at this point. i guess the issue is around here but it seems pretty generic https://github.com/libretro/RetroArch/blob/c377516db24f999251bec18da414381ff8aab640/gfx/drivers/gl.c#L4174

building retroarch in debug mode might make things easier to debug, but you'd have to mess with the install script for that.

@guy-0 said in Run a command after logging off pixel:

Should I have done it through CLI instead?

No, installing from RetroPie-Setup is fine. I wonder why the onstart script doesn't work though, the desktop is launched via runcommand.

@dclegend By default, there are no onstart, onend scripts - it's an extension that can be used by users to add their own customizations.

This should be handled automatically - via the renameModulefunction in the scriptmodule. See for instance here.

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