@Darksavior thanks for the advice. I think I'll return the 1440p monitor and get a 1080p one.
I can always upgrade down the line.

@3250847 said in RetroPie doesn't recognize my 7 inch display:

I already edited my /boot/config.txt and added this line

The line is not enough and it's incorrect. The configuration you should add to the file is:

hdmi_cvt=1024 600 60 6 0 0 0 hdmi_group=2 hdmi_mode=87 hdmi_drive=2

Thanks, I will try this, but I doubt this will help. Raspberry PI OS and Emulation Station recognise the display correctly as they feed it with 1280x800 automaticaly. RetroArch seems to miss this information or ignores it.

Edit: With hdmi_ignore_edid=0xa5000080, resolution in raspi-config = 1280x800 and no resolution set in RetroArch everything works fine. I still do not realy get why, but thanks a lot @mitu!

@mitu I did a small test. well I’m all confused. I swear you couldn’t change resolution in the raspi config anymore. Guess from the time I used the Kms driver from my last build. Well I went there and it allowed me to set a resolution and set the config.txt. Rebooted, but here’s the kicker. The hdmi port I was on, that booted to 1080p, now booted to a black screen acting as a second screen. And when I switched hdmi ports, to the one that ran at 4K 30hz, it was now displaying at 1080p. Still wondering why I was getting 1080p on the other port before. Guess at this point it doesn’t matter.

https://retropie.org.uk/docs/Runcommand/#runcommand-launch-menu

Success! Ok i figured it out. This is going to be a long one so sit back, but anyone with a similar problem, i hope this will work for you. Again I am running RetroPie on a raspberry Pi 3 with a Pi2Jamma adaptor and i ran the retropiergb mod to output to a 15khz monitor. so i figured that this was an issue with the run command, so i found a file in the /opt.retropie/configs/all, named runcommand-onend.sh . In it there is a line for HDMI timings that was different then the one in the global config.txt in the boot folder. so i added the correct timings and # out the originals and it worked! but then for some reason mame was outputting a very stretched image at 1920x240, so i went into the configuration options in the run command menu and changed the settings in the edit custom retroarch config option. In it you will see that the custom viewport is set to 1920x240, so i just added a pond symbol before the commands. Since the layout seems to be UK it is a £ instead of # for us Americans but it works just the same. and now mame defaults to the listed game resolution. I have no Idea why these options did this but I wasn't going to let this beat me. I hope this helps.

fix_0.jpg fix_2.jpg
fix_3.jpg
fix_1.jpg
fix_5.jpg
fix_6.jpg
fix_7.jpg
fix_4.jpg

Please add some more details about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

Pressing A when the game is loading and changing the resolution for the emulator. Can't seem to find the right one.

Just remove any custom resolution and leave the game/emulator running with the default resolution. Check if you haven't got a 'render resolution' configuration and remove it also.

I saw an answer somewhere to run the command sudo raspi-config. Is that the command, nothing else?

raspi-config sets the global resolution, used when starting the Pi, but it doesn't affect the individual game/emulator resolution if you're changing it from the runcommand menu.

I also saw an answer to go to Settings and choose "Adjust Resolution" but can't seem to find that.

Maybe in the Configuration Editor ?

@stonewind please supply a verbose log as per https://retropie.org.uk/forum/topic/3/read-this-first

FYI/UPDATE : For future browsers who may purchase and use this, or a similar, screen on their Pi.

https://www.amazon.com/dp/B07S82CN57 - Longruner Raspberry Pi Touch Screen

It turns out the driver for the LCD set the GPU RAM to 64MB upon installation. I tried it on 2 other 3B+ units I had running RetroPie because it was bugging me, and it did the same on both of them.

Just to confirm, I set it back to 128, reinstalled the driver, and it went back to 64 each time.

So if you use this screen, or maybe one similar to it, check your GPU RAM allocation after you install the drivers, it may have changed. Especially if you move the Pi back to a higher resolution display.

Edit: To be more specific, running "sudo ./LCD-hdmi" will set it to 64 every time. In my case, and probably others, if you move back to a "standard" HDMI display and do not run this, you will not have audio at all, no matter what you set in the Raspberry Pi/RetroPie. So if you use this or any similar LCD, and you notice you lost audio when moving to something else, don't forget to run this. Then check your GPU RAM allocation.

:)

@dankcushions
OK I was a bit silly I had the HDMI plugged into the one away from the USB C power port. I have edited the line in config.txt to hdmi_group=1
hdmi_mode=16

All working fine now 👌

@benmclean said in Resolution menu not working?:

I reported it here

Shoot, I did not find that despite searching. I'll close mine! Thanks!

I made a mistake. While i am using KMS, I guess somehow in my config.txt file, the changes I made to force 1080P got commented. Maybe the raspiconfig did it when I selected to have my monitor set resolution. Anyway, I uncommented the forced resolution and now the pi is working in in 1080P. Not sure if that's how its supposed to work?

It's working okay now all things considered. I'm surprised at how well the scaling works as on the raspbian + retropie the text is harder to see and the borders are a bit off even in the terminal. I should try to copy retropie's font to my other sd cards with raspbian + retropie on them to make the console more visible

Glad you got it sorted out, actually RetroPie is using Raspbian (RPI OS) Lite underneath, so there's no specific font that's included in RetroPie.

Maybe the borders' position have something to do with the Overscan settings for the display ? Or you may try to increase the font size from the Setup script, as explained here ?

@4retropietft alr thank you so much for your help

@stuckinthe90s If Mitu's suggestion to check "in emulator" or "in game" for overriding video mode settings doesnt work, I had a similar problem the other night on a Pi Zero..... i had a message floating across the screen saying something to the effect of the input signal is not compatible. I ran raspi-config and found "Display Options" then "Resolution". When i opened it was set to something in the middle of the list.... I arrowed up to the top of the list and found "Default Monitor preferred resolution". I selected that and rebooted. IDK if the Pi4 has the same config( i only have a ZERO and a 3B+... and am also quite green in the ways of Pi). That change fixed my issue. Not sure if that is the best way, and i haven't done much testing to see if there are other issues caused by that fix. Best of luck. -D