@greenhawk84 Download the latest image and open it with 7zip to look in the boot partition and read it. This is what it looks like, extracted from the PI4 image:
# For more options and information see
# Some settings may impact device functionality. See link above for details
# uncomment if you get no picture on HDMI for a default "safe" mode
# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
# uncomment to force a console size. By default it will be display's size minus
# uncomment if hdmi display is not detected and composite is being output
# uncomment to force a specific HDMI mode (this will force VGA)
# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
# uncomment for composite PAL
#uncomment to overclock the arm. 700 MHz is the default.
# Uncomment some or all of these to enable the optional hardware interfaces
# Uncomment this to enable infrared communication.
# Additional overlays and parameters are documented /boot/overlays/README
# Enable audio (loads snd_bcm2835)
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
For the PI2/3 models, I think there's a memory setting added that's extra, the rest should be identical.
sure! didn't want to imply that, it just was a major roadblock for me yesterday and today and a lot of searching around just showed that a bunch of people had the same problem. the solutions with manually editing the config file sure help but it would have been just so much easier if I could have set it in the menue. not because editing the file is difficult, more like you don't think of it because everything else just works like it should (well, beside the playstation classic controller not working despite being a simple USB device) and the config tool just blanking out is confusing. honestly if the whole system wouldn't crawl around at around 10 - 15fps at 4k you wouldn't even notice the problem is there to begin with. I'll search if the problem is known at Raspbian.
I don't think it would be 81, but you are correct that it's wrong. Shouldn't be 16 because my TV only displays up to 720p, not 1080p. Although it is a 16:9 TV (not 64:27 like it shows under #81). Also, my TV frequency isn't 30Hz, unless I'm missing something.
you've fixed it now so i guess this is irrelevant but yes, you'd need to use hdmi_group=2 for 81 - it doesn't seem to be supported under 1. but yes, @mitu 's suggestion would get show you the complete list of supported modes. given that it's less than 4k, i would always want to be running in the native panel resolution so you don't get scaling artefacts.
i assume now you've taken out hdmi_safe you can safely take out any hard coded modes and it should hopefully choose 1366x768 by default.
Using raspi-config to change the audio output will not write to /boot/config.txt, but will change the ALSA (sound system) settings.
Changing the settings from the raspi-config will invoke
amixer cset numid=3 2
underneath. Try running this command from the command line (exit EmulationStation via the menu or by pressing F4) and see if the settings are kept after a reboot.
If that doesn't work, then add more info about your system, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.