@oskeeeddie Re-install/Re-enable the RetroPie shares from the RetroPIe-Setup script and see if you get all 3 shares back.

@3rik would be better not to make one perhaps (as this is your only post!). Save the moderators some time. I'll remove you shortly.

@undrwater Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

Please provide more details of set up. No idea which hardware you're running even.

I have just fixed the Fault

runcommand-onstart and runcommand-onend scripts
Runcommand can execute an user script before the game launching (runcommand-onstart.sh) and after exiting the emulator (runcommand-onend.sh). Both scripts must be placed at /opt/retropie/configs/all/.

These were the settings. I changed them to 1024 768
fbset -g 320 240 320 240 8
fbset -g 320 240 320 240 32

Not sure how these are changed, but hey :-)

@mitu

Thanks for all the help. I decided to just give it up and ordered an 8bitdo.

@obsolete maybe should have mentioned that :)

ok so that is surely your issue. you're using hdmi_safe=1, which forces

hdmi_group=2 hdmi_mode=4

which means 640x480. it may be that your TV puts borders on such a low resolution, and there's nothing you can do about that after the fact.

i would change hdmi_safe=0 and manually edit hdmi_group and mode to something sensible for your TV. probably:

hdmi_group=1 hdmi_mode=16

or

hdmi_group=2 hdmi_mode=82

btw config_hdmi_boost=9 does nothing on a pi4.

@mahalingam it was fixed, so if you're getting the issue open a new topic with some info.

Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

I would like to add I dont feel retropie cashes in on this they could make a lot of money if they chose to but they dont you get the moral decent project vote no one could dispute that. You project clearly runs itself for it purpose and not for profit.

Im only talking in licensing terms in general

@ClassicGMR I have the same issue. I suspect it's user error!

Also, thanks :-)

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

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!

Makes sense.

Thanks!

i had something similar happen with my roku / TV .... LG pushed out some sortof update that didnt work well with roku.. i had to connect to another TV memorize the key strokes to set the resolution to a lower resolution. It worked fine after that ... dont know if i ever increased the resolution again.

Possibly adjust resolution lower and see if that resolves the problem.

Can you add more details about your system, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first ?

@KRAKATOA you are a life saver. It worked to perfection. Thank you!!!!

@mitu ok thank you

@mitu - Ok, that sounds good, I appreciate the information.