Displaying button actions

[mitu]

@Texacate The topic has one suggestion for how to automate things - using imagemagickfrom the command line to programatically compose the image. Here's an idea:

• have a master image with the layout
  [ Y ][ X ][ L ]
  [ B ][ A][ R ]

and a separate text inset that would explain the buttons -
Y = Fire
X = Turbo
etc.
But the inset would be empty (in this template image).

• have one (transparent) image with each button selected/lit - i.e. for instance let's say `A' is used, have the same image as above, but just with

  [ A ]

• When generating the final image, combine the layout with the images containing the buttons and populate the text in the inset with the button names/actions.

[BJRetro]

@mitu seems like maybe for a typical 6 button arcade setup this page’s explanation for text positioning with gravity might work on an image because it would always place the text the same relative place on an image of the buttons: https://imagemagick.org/Usage/annotating/ . Very over my head on the coding aspect though.

[hiulit]

I could help with imagemagick.

But @Texacate has a point:

But the downside is: once the game starts, the map/legend is gone... Ideally I like it to be persistent

@mitu do you know if it's possible to alter EmulationStation or RetroArch to map button to show/hide the controller image?

[mitu]

@hiulit Emulationstation is pushed in the background once the game starts, so there's little use to modify it.
RetroArch can use some overlays (bezels) to display the button mappings and I see there's some settings like input_overlay_show_physical_inputs (dunno what it means) or input_overlay_next_btn. Ideally you could have an additional overlay (bezel) to show the button mapping and toggle between the normal (or empty) overlay to the button layout overlay using input_overlay_next_btn. I'm thinking at something similar discussed in this topic which handles shaders.

[mitu]

Aha, I found out what input_overlay_show_physical_inputs does. You can create an overlay (bezel) to show the controller buttons and you can map regions of the overlay to be toggled as you press the buttons on your controller. Here's an example for a NES overlay which can show buttons being pressed while you play.

[hiulit]

@mitu WOW, that's even cooler that showing a plane image! O_O

Now, how could the process of creating those bezels be automated?

[hiulit]

@mitu There's an arcade bezel https://github.com/libretro/common-overlays/blob/master/gamepads/arcade/arcade.cfg that could be used

[mitu]

@hiulit They don't look so hot

[hiulit]

@mitu No. they don't.... :( But then again, we could create a new bezel, right?

[BJRetro]

@hiulit I wonder why the name one is on top of the game whereas NES was outside of the frame.

[Furluge]

These would be amazing if they were being shown outside the screen in all that unused blanks space as opposed to on top of the gameplay.

[hiulit]

@BJRetro I don't understand. I see both bezel on top of the game.

[hiulit]

@Furluge What" unused blank space" are you referring to?

[Furluge]

@hiulit The sides of the screen when using a 16:9 monitor to display games meant for 4:3 aspect ratio. I'm saying I don't understand why the overlays are covering up the screen when they could be filling empty space you would usually see art / bezels fill up for a 16:9 monitor showing a 4:3 game. Displaying controller inputs seems like a pretty nifty usage of that space but all these overlays I'm seeing, even the metroid one, are putting everything over the display area, which seems silly to me. It looks like it was meant cell phone on screen controls to be honest. Actually that's probably exactly what these overlays were made for.

[mitu]

@Furluge The screenshots were done by me, by just loading the bezels/overlays without any parameters (i.e. screen size, viewports size). They can be configured to show outside of the game viewport, I just loaded them to test the button actions reflecting on the bezel changes.

[Furluge]

@mitu Ooohh, ok, I'll have to take a look at them then. Though they still do look suspiciously like on screen phone controls. :D

[mitu]

@Furluge I suppose they look like RA's controls when run on a mobile device - but they're overlays. I posted the link to them in the first screenshot post.