miss aligned text in game selection menu

[uberdisko]

im not sure why i cant get this right i have tried to modify about everything in layouts but i keep having my Game Name Text in all my system menus miss aligned please let me know if there is a easy way to fix this im sure its because im trying to run this theme in 4:3 (640x480)

[Rydra]

Same problem here. I just updated my retropie and the text was misaligned. A pity since this is my favourite theme by far.

[uberdisko]

Same problem here. I just updated my retropie and the text was misaligned. A pity since this is my favourite theme by far.

i did kinda fix it by writing a repositioning in the base.xml but then i noticed only 6 of the games listed show up so the bottom entry is blank too

[tonylepsie]

I just finished a fresh install of retropie and snes-mini theme and I had the same issue. Any workaround ?

[makoffee]

I've been able to resolve the issue on my local machine. After reading the Emulation station documentation, it seems to be an issue with how the latest EmulationStation handhelds y co-ordinates for textlist parameters. For the snes-mini theme using the 1080p layout I was able to adjust the settings to get acceptable results. Your mileage may vary, however this file seems to be the issue. It's effecting a number of themes so either the themes need to be updated or ES should put out a fix.

Anyhow - I was able to update /themes/snes-mini/layouts/1920x1080.xml as such (may work in other resolutions):

pos = ${listx} 0.19537037037037
size = ${listWidth} 0.62962962962963
selectorHeight = 0.0814814814814815
selectorOffsetY = -0.0111111111111111

Hope that saves someone else the trouble of sorting it out.

[makoffee]

Added a pull request here (2nd UPDATE):
#26

[uberdisko]

does this fix the missing final game listed?

[Rydra]

@uberdisko I can confirm that @makoffee fix solves all the listing issues. Bear in mind though that he targets specifically at a resolution of 1920x1080.

Thanks @makoffee for the work :D

[makoffee]

@Rydra - No worries. It's true I only targeted the 1080p resolution as that was my target test device (raspberry Pi on HDTV). After a cursory review of the other layout files. It would seem this issue will also negatively impact the other resolutions as well.

I'll do a second pass and update all the effected resolutions and post a more comprehensive pull-request.

[makoffee]

Ok,
I've added a new pull request with a more comprehensive fix, updates the y sizes and offsets of all resolutions:
#26

@uberdisko - Can you test my branch at https://github.com/makoffee/es-theme-snes-mini/tree/makoffee-patch to test and see if my fix works on 640x480?

[uberdisko]

sure thing

[uberdisko]

fixed for 480p, you are a god thank you

[makoffee]

@uberdisko - Your screenshot makes me very happy! Glad to see it working for you.

[ViperAcidZX]

Ok, I've added a new pull request with a more comprehensive fix, updates the y sizes and offsets of all resolutions: #24

@uberdisko - Can you test my branch at https://github.com/makoffee/es-theme-snes-mini/tree/makoffee-patch to test and see if my fix works on 640x480?

Anyone else getting Emulation Station crashes with these fixes? I've tried your fork of this theme and Emulation Station has been crashes with the fixed offsets. I'm using a Raspberry Pi Model 3B+ with the latest RetroPie updates at 1920x1080 (although my display maxes out at 4K).

[makoffee]

@ViperAcidZX - I've been noticing memory issues related to this theme that seem to cause random ES crashes when pre-loading the UI on start. A few things I've tried is deleting the game lists meta data from the scraper. Increasing the GPU memory, and playing with the vram-limit settings.

Try removing my offset-patch and reboot a few times to confirm. Though I'm not sure why different offset values could cause a memory overflow.

[makoffee]

@ViperAcidZX - I think I might be understanding what could be causing the issue.
Looking at the height values for the sizes from the original 1080p layout. if you take Ruckage's original value "0.5481481481481481" and multiply it by the height of 1080px you get a nice whole number of "592". If you take my value of "0.63" and multiply it by 1080 you get a float of "680.4".

I'm going to speculate that if I update the values to calculate as nice whole numbers multiplied by the screen height, at each resolution then it may represent a possible variable type miss-match. I'm just pulling at straws here, but I'm going to give it a shot. And if it works I'll update my branch and post a new pull request.

Stay frosty!