Overlay positioning changed after recent update

Alturis

I apologize for querying like this but I have been away from the retropie community for some time. I recently moved and setup my bartop retropie again that had been dormant for some time and decided to do an automatic update of all installed components via the menus. After that had completed I noticed that the overlay positioning had changed from my past setups. The artwork overlay is now bleeding over onto the playspace more than it had before obstructing my view of the rendering game. Just wanting to know if there were known changes to a recent version upgrade related to overlay artwork positioning,

mitu

That's because of a change in RetroArch's custom resolution index - see https://retropie.org.uk/forum/topic/19598/custom-viewport-problem-retroarch-1-7-5/. You'll need to modify the .cfg files for the overlays and update the index value.

Alturis

@mitu Thanks for the tip. Strange why they would make a change to the config setup like that. I updated all my other emulator cfg files to make that fix.

However, that does not appear to be the issue that I am encountering for most of the games I have as I am not using a custom aspect ratio with my arcade roms nor with the particular example game in question.

frogger.zip.cfg

input_overlay = /opt/retropie/emulators/retroarch/overlays/arcade-bezels/frogger.cfg
input_overlay_enable = true
input_overlay_opacity = 0.900000
input_overlay_scale = 1.000000

/opt/retropie/emulators/retroarch/overlays/arcade-bezels/frogger.cfg

overlays = 1
overlay0_overlay = "frogger_udb-ovl.png"
overlay0_rect = "0.0,0.0,1.0,1.0"
overlay0_full_screen = true
overlay0_descs = 0

/opt/retropie/configs/arcade/retroarch.cfg

input_remapping_directory = "/opt/retropie/configs/arcade/"

input_player1_joypad_index = "1"
input_player2_joypad_index = "0"

#include "/opt/retropie/configs/all/retroarch.cfg"

/opt/retropie/configs/all/retroarch.cfg (left to default - whatever that is)

# Index of the aspect ratio selection in the menu.
# 19 = Config, 20 = 1:1 PAR, 21 = Core Provided, 22 = Custom Aspect Ratio
# aspect_ratio_index = 19

# If this is true and video_aspect_ratio is not set,
# aspect ratio is decided by libretro implementation.
# If this is false, 1:1 PAR will always be assumed if video_aspect_ratio is not set.
video_aspect_ratio_auto = "true"

mitu

@Alturis what's in your bezel config file - frogger.cfg ?

Alturis

@mitu I updated my above post to include that as well.

Edit: But none of my existing cfg setups would have changed. It was only the update to the latest builds of retropie and retroarch where something changed.

mitu

What emulator are you using ?

Alturis

@mitu I use a host of emulators for various games but primarily I use lr-fbalpha (fba). In particular I am running fba for frogger.

mitu

I'll try to give it a test, but that would take a couple of days.

mitu

Just tested this and I don't get the issue you're mentioning. Here's 2 screenshots taken on a 1080p display - https://imgur.com/a/JwkAFkJ - with and without overlay. From what I'm seeing, the overlay matches exactly the remaining screen area, on a 1080p display. The screenshots were taken with Mame2003 and with the latest binary update for RetroArch - I get the same result with FBAlpha.

I used your configs and @UDb23's Frogger overlay, which I assume you're also using.

Alturis

@mitu Well thank you for taking the time to validate and test that on your own. I appreciate it.

If anyone else has any ideas what might have changed in a recent update, that might be causing such a thing, I am all ears.

mitu

@Alturis Do you know what version of RetroArch you had installed before de update ? It might help to diagnose the issue.

One thing I always ask is a verbose log from RetroArch - can you get one and post it on pastebin.com ? You need to start the game with 'Verbose Logging enabled' from the Runcommand launch menu, wait for the game to start then exit. Get the log file from /dev/shm/runcommand.log and upload it to pastebin.com.

Alturis

@mitu No I had not made a point to remember or write down what version I was running prior to upgrading. But it would have had to have been within the last 6 months I would think where I last upgraded. I was about exactly a year ago where I was heavy into retropie and on these forums a lot. But since then I recall doing an occasional update at least a couple times.

Interestingly, the runcommand menu does not seem to have an option for Verbose logging that I can see. Are you positive that was not a feature that was removed recently?

However, this is the contents of the log when I run frogger:

/dev/shm/runcommand.log

emulator: arcade
software: lr-fbalpha
rom_path: /home/pi/RetroPie/roms/arcade/frogger.zip
rom: frogger.zip
Using default player joypads
joycommand:
none
Parameters: 
Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-fbalpha/fbalpha_libretro.so --config /opt/retropie/configs/arcade/retroarch.cfg "/home/pi/RetroPie/roms/arcade/frogger.zip" --appendconfig /dev/shm/retroarch.cfg'|'"/home/pi/RetroPie/roms/arcade/frogger.zip.cfg"
xboxdrv: no process found
Using default player joypads

/dev/shm/runcommand.info

arcade
lr-fbalpha
/home/pi/RetroPie/roms/arcade/frogger.zip
/opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-fbalpha/fbalpha_libretro.so --config /opt/retropie/configs/arcade/retroarch.cfg "/home/pi/RetroPie/roms/arcade/frogger.zip"

/dev/shm/retroarch.cfg

video_refresh_rate = 60

mitu

@Alturis said in Overlay positioning changed after recent update:

Interestingly, the runcommand menu does not seem to have an option for Verbose logging that I can see. Are you positive that was not a feature that was removed recently?

Yes, I'm positive - it should be present for all lr- emulators (see here).

Alturis

@mitu Oh! you mean within the runcommand optional menu when you launch.. ok one sec...

Alturis

@Alturis Ok, verbose log here:

/dev/shm/runcommand.log
https://pastebin.com/2CwTUQvQ

Alturis

@mitu Also, I do recall hand tuning most every single overlay I have ever located. Some of them I created from scratch. It's possible that my current version of frogger_udb-ovl.png is different than the original UDB created. But either way, I would not want to go back through every single game and hand tune the artwork for them again. Looking for what configuration or system change might have altered the outcome of the overlay rendering across the board.

Here is the frogger_udb-ovl.png I am using:
https://drive.google.com/file/d/1o37kClpjM515H5YcTkBGiKs6-6rfCt6-/view?usp=sharing

mitu

I see from the log that the resolution is correct (1080p), but nothing else that pops up. The overlay I used for testing hasn't been updated in 2 years, so it should be the same as yours.

I'll check to see how is my system configured w.r.t. 'Force Aspect Ratio' and 'Integer Scaling', maybe that makes a difference.

Alturis

@mitu Yeah I confirmed by comparing your previous screenshots with my overlay that the one I am using is nearly identical. I had actually gone in and trimmed just a bit more of the overlay pixels away nearest the game display so that the rendered game is framed by a thin edge of black. (just a personal preference and largely why I had hand tuned most every overlay for my games)

So if anything my overlay should be exposing more of the game not covering any of it up.

Alturis

Wait a minute.. hold the phone... I JUST realized that the actual display that is drawing for my overlay is Final_Arcade_Frogger.png... not sure how the hell I didn't notice that before. Something seems to be wrong with my setup such that it is NOT actually listening to the above configuration. Investigating....

mitu

@Alturis You have a game override in the RA's config folder

 [INFO] Config: appending config "/home/pi/.config/retroarch/config/FB Alpha/frogger.cfg"