@barrymossel said in Resolution doesn't change:

. Still weird that setting resolution through the configuration editor doesn't work.

The configuration editor is for RetroArch configurations and I think RA doesn't change the resolution of screen itself. What you actually want is the runcommand resolution switch - which works with tvservice. Another option is to use the onstart/onend scripts to switch resolution, instead of manually configuring per-emulator settings in the Runcommand.

@dankcushions These "mini" themes work perfect! I never thought of using 4:3 themes or were aware of them; it fixes the distortion problem and now everything's proportional, thank you :)

I use HDMI to VGA at 640x480 too. Every emulator or even game can have its own resolution. I enabled the RunCommand launch menu and selected for each system (DMT-4 and 5 means 640x480). I don't know if I forgot something, but here it is.

RunCommand launch menu:
Select default video mode for "SYSTEMNAME" (DMT-4)
and
Select RetroArch render res for "SYSTEMNAME" (5)

Then you can disable the RunCommand. I also set the resolution of EmulationStation itself through the file

/boot/config.txt:
hdmi_group=2
hdmi_mode=4
config_hdmi_boost=5

@mhughson said in Stuck at bad resolution:

Thanks for the help!

I didn't do anything, but glad you got it sorted out !

Thanks blackshadow for your reply. I am using the tronkyfran theme, and the raspberry Pi 3b standard. My plan was to make the boxart at a high res, cause I am using the boxart as the screensaver.

I scraped again one full gamelist, at 1200 x 768 and that worked very well in the game list, no lag, and the screensaver boxart now doesn't look stretched or pixilated at full screen.

Hope this might help someone in future, if they planning to use boxart as the screensaver.

Thanks blackshadow all the best

I did give a try a few minutes ago. If I sit far away from my TV the shader looks okay but if I'm up close I can tell a difference. I don't know enough about the inner workings of shaders to say exactly why it looks worse up close, but it does. Hmmm.. I guess it's back to 1080p then as a nice shader is more important to me than marginally smoother menus.

@microb41 According to the Raspberrypi website, there is a pixel clock limit, ie effectively a limit to the number of pixels that can be controlled, of 1920x1200@60 Hz, so as your resolution exceeds that, it shouldn't work

You can set higher resolutions, in config.txt, but they won't work.

https://www.raspberrypi.org/documentation/configuration/config-txt/video.md

Further down on the same page, it shows you how to create a custom screen resolution, so it would be worth you looking at that to get the aspect ratio you want.

@douga said in Screwed up sizing of EVERYTHING playing with MAME:

Looks like I was a bit slow, but anyway, you can force whichever resolution you want by uncommenting the hdmi_mode line again and setting the value. You had it set to VGA resolution, according to that link.

Yeah. Thanks man.

Strange thing is that I never un-commented either of those lines. I know that there is some strange resolution changes that happen when entering and exiting games in MAME and FBL, so I'm thinking that the commenting/un-commenting of those lines must happen while using those emulators and I just happened to freeze the Pi after the un-comment, so it wasn't going to be fixed until I figured out what needed to be done manually.

Thanks for that link. Bookmarked. :)

How do you install blobby volley?
I tried to search "blobby" in install package,
but I can't find it.

Can you help me?

Thanks.

@hsamuels
Same problem after update 1.7.5 - MAME 2003 (0.78) 95bb558

I'll open a new topic.

@briandewiz
git clone https://github.com/Elecrow-keen/Elecrow-LCD5.git

This is what I used to get the screen working if that helps

@drago-supremo The default settings - of the RetroArch included in RetroPie - is to use and preserve the apect ratio of the emulator used, scaled to the resolution of the your output.
If you still want to change it, you can use the Runcommand launch menu (https://retropie.org.uk/docs/Runcommand/#runcommand-launch-menu) to set the resolution per core (emulator) or game.

Here is a list of supported resolutions: https://www.raspberrypi.org/documentation/configuration/config-txt/video.md

Looks like it isn't on there

Here are some handy links found

https://www.raspberrypi.org/forums/viewtopic.php?t=25933 https://raspberrypi.stackexchange.com/questions/46153/detect-hdmi-and-start-gui/46158#46158 (the guide from the Raspberry Pi site) https://www.raspberrypi.org/documentation/configuration/config-txt/video.md

You can start playing with the command and see if you can switch manually between resolutions, on the fly. If this works, then you can incorporate it in a script to be run at boot.

Yap, when i use Retroarch, i always choose "core provided" and any screen or device the resolution of the game is always OK.

@Nossral

I would go with RetroTINK Ultimate and a VGA to Scart cable with two external Audio connections.

To get better audio instead of using the built-in 3.5mm audio jack a would recommend a usb soundcard.

@mitu said in Resolution/Video Mode/Aspect Ratio...:

Set your Pi to 1080p and then don't alter any configurations - you don't need to choose 1080p again in the launch menu.

This worked great, but....

I had to edit /boot/config.txt directly and tell it to ignore the resolution my tv was requesting.

This was the missing magic for your simple solution to work for me.

hdmi_ignore_edid=0xa5000080

https://www.raspberrypi.org/documentation/configuration/config-txt/video.md

You can also set the resolution in the same file.

Otherwise, regardless of how I set the right resolution something was wrong with either the desktop, console, or retropie.

Most systems that display in 256x224 are stretched by the TV.

The NES' pixels are actually 1.2x wider than tall, probably the same for other systems as well.

note that when you used enhanced resolution, the resolution is doubled. so shaders will have to process 4x as many pixels (ie, probably run slowly), and the effect will be less obvious since the pixels are much smaller.