Show Control Panel Layout before game starts in RetroPie, just like Arcade1UP does.

[TheRealSmilebit]

@cyperghost That is good idea.

[TheRealSmilebit]

@BJRetro said in Show Control Panel Layout before game starts in RetroPie, just like Arcade1UP does.:

I guess the coding option is good because depending on the emulator used the buttons might be different for different people

Yes...I was going to try to figure this out, as if button layout changed would have to change each graphic...but with this would only have to change the text file.

[cyperghost]

@TheRealSmilebit I think if the community will start to collect the files for navigation someone will start to write a good script. My contribution is likely just a text message display ... simple but will not look well ;) Maybe a more talented user can do the graphic stuff. A tool package like imagemagick is the way to go ;)

Support for different emulators needs to be added, too.

[UDb23]

@cyperghost Nice idea.
To be useful to players the txt file and the graphics should consider also the different types of gamepads actually used.
Buttons assignment / layout for an arcade game would be different depending on the controller you use. That makes the whole thing quite complicated.

[cyperghost]

@UDb23 Na it is not so complicated if we assign to a Standard layout like the XBox or PS controller. And then map the inputs to a specific layout. It is doable but needs care what we are doing here. But in fact I would appreciate such a feature

[Texacate]

I found a database that will associate a rom name, with a list of button actions, like "Fire", "Jump", "Hard Punch", etc. Check out https://github.com/yo1dog/controls-dat-json. Not a full solution, but a necessary building block, for sure.

[robertvb83]

@TheRealSmilebit what a great idea. This would really add some value to my arcade cabinet
@GreenGriffon wow this is an awesome looking example. I like the idea of using a flyer in addition to the button layout.
of course an automated script based solution would be great. @cyperghost could you imagine a solution to deal with different joypad layouts that people use for their arcade? I mean GreenGriffon uses a 6-Button layout with
123
456
I think of some way to easily change that via a personal input e.g. my pad would also be 6-button but
456
123
other pads would be
1234
4568
you get my idea.

btw. I am pretty sure there already is a source file inside of mame with button names and how many buttons are used for each game @markwkidd am I right? this is what you used to come up with the automated button names to display in retroarch for mame2003-plus

[markwkidd]

@robertvb83 said in Show Control Panel Layout before game starts in RetroPie, just like Arcade1UP does.:

btw. I am pretty sure there already is a source file inside of mame with button names and how many buttons are used for each game @markwkidd am I right? this is what you used to come up with the automated button names to display in retroarch for mame2003-plus

controls.c has the button names. I am determining the number of players in the code when the game is loaded, but I am pretty sure that information is available in the DAT.

[chicuelo]

@GreenGriffon Thats my arcade cpo icon ;)

[cyperghost]

@robertvb83 said in Show Control Panel Layout before game starts in RetroPie, just like Arcade1UP does.:

. @cyperghost could you imagine a solution to deal with different joypad layouts that people use for their arcade? I mean GreenGriffon uses a 6-Button layout with

There is need for a standarized button layout. I suggested the XBOX or PS controllers and then the user can assign like you mentioned in your layout

Button A = 1
Button B = 2
...
or
Button A = 4
Button B = 5

as you like

@Texacate said in Show Control Panel Layout before game starts in RetroPie, just like Arcade1UP does.:

I found a database that will associate a rom name, with a list of button actions, like "Fire", "Jump", "Hard Punch", etc. Check out https://github.com/yo1dog/controls-dat-json. Not a full solution if you have hundres of games, but a necessary building block, for sure.

This is a nice finding!
The data can be extracted out from the 1.3MB database ;)

[Texacate]

@cyperghost AFAIK, the yo1gog's data appears to be just a reformatting of the data from the Controls.dat project started by Kevin Jonas (SirPoonga) with the help of Howard Casto. The original data is currently archived here: http://controls.arcadecontrols.com I've noticed only parent roms are in the database. So if you run a clone (like PacMan), you will need to account for that limitation. Also, I believe the data has not been updated in several years, (2011? if memory serves...) Newer rom are likely to be missing, but I probably couldn't run those games on a RPi anyway.

[Texacate]

I'm pretty motivated to get something like this working. I thought about using a separate "slave" RPi, with its own 5" to 7" LCD display to display the button map. That way it could be placed anywhere on my cabinet, and would never interfere with the main gaming display. I sure someone has already created a simple script that just listens on a port, and displays the desired (local or remote) image file. Kinda like a kiosk, or remote-control screen saver, but I have yet to find a simple utility like that. I'm fairly linux and retropie literate, but if I have to build it from scratch, this sort of master-slave network communication is beyond my linux skills.

[markwkidd]

@Texacate the MAME 2003-Plus controls.c is based on the last 2011controls.dat version plus of fixes and new games. We've also started matching parents and clones.

Link: https://github.com/libretro/mame2003-plus-libretro/blob/master/src/controls.c

If there is any way to share our controls metadata with your project and have both improve then I would be glad to talk about whether, for example, we could implemented a scripted conversion between our controls.c and whatever format is needed here.

[markwkidd]

Upon further thought, it should be straightforward for MAME 2003-Plus to export our updated controls.dat metadata as XML and continue to provide XML in an automated way if we were coordinating updates.

When I say updates, I should mention that there are games from even back as far as MAME 0.78 that were never added to controls.dat. There are also some games for which their control names are incorrect, so we have a policy of double-checking that information before making it active in the core.

[Texacate]

I have been going down the path of using a separate raspberry pi to display the button map.

I have solved the problem pi to pi communication thanks to a set of YouTube videos. Effectively the second raspberry pi will listen to the main raspberry pi, and display the image was instructed to display.

The client side which runs on the main raspberry pie is done. It uses runcommand-onstart .sh hooks provided by emulation station . I’m still tweaking the server which runs on the second raspberry pi to display the desired image .

I will post the instructions and the python scripts on my github account .

Once I have the server working, all I need is a library of images !

[Arnulf]

I like this idea.
I've done this a few day ago to light my buttons depending on the rom/game.
I wrote a python script which will do this for me.

My next plan would be to illustrate this within the load screen. So this thread is now one of my favorite :)

@cyperghost : I like your method to trace the keylayout.txt.

[Texacate]

I have a prototype of this working, and have set up my first "real" github project!

All the files are at:
https://github.com/Texacate/Visual-RetroPie-Control-Maps

The (starting framework of) the documentation is at:
https://github.com/Texacate/Visual-RetroPie-Control-Maps/wiki

This is definitely a work-in-progress and is my first foray into Python programming! Please be kind. I'm sure I've made numerous coding blunders. Also, I have no artwork files built yet, (I'm using a set of marquee files for my testing). But the thing actually works and does not seem to crash my RPis !

I would love to have feedback on this.

Thanks!

[cyperghost]

@Arnulf Yes I think the way to do is clear but I think I've not the time to take on that challenge. Working on some other projects currently

@Arnulf Why do you want to establish a communication socket between a node? I think the Pie alone is powerfull enough to create/show/manage every image. Keep us imformed about your progress ;)

[Texacate]

@cyperghost Was the question on socket communication meant for me?

My project uses a small LCD screen dedicated to displaying the button map, where as GreenGriffon and others prefer to use the splash screen, upon launching the game. I agree there is enough compute power to handle everything on one RPi. But out of the box, an RPi cannot drive the HDMI port and the LCD port at the same time. This limitation led me to choose a 2nd RPI for the button map display, but also created a need for the two RPIs to communicate. TCP sockets seemed a logical way to accomplish that.

[CargoRunner]

@GreenGriffon I think your loading screen looks great. And you are certainly correct when you say how time consuming producing them is. I wanted to do the same thing for console games. I have a small curated list of games too. I find the more artwork the more interesting and/or nostalgic the experience of playing the game is. And reminding the player what the controls are can make playing the game enjoyable instead of frustrating when nothing seems to work. I gave up on my theme and console loading screens as I am not artistic enough to make the finished product look good enough.

And as people have stated, the value of sharing the finished product is limited as people use different controllers. Mine is based on the xbox 360 controller.

I put the TV retropie project on hold as I want to build an arcade cab more. I would love to use your loading screens but my menu/exit/coin/start buttons are in totally different places.

I think that the ideal solution would be if the loading screen was an XML defined page just like the game select screens. So the loading screen was just part of the emulation station theme. The XML defined page could then pick up the artwork and button text. This is obviously a significant change to ES so is not possible at all. But it is nice dreaming !