@rock0520 no. It's hardcoded currently.

Hello all,

@meleu

I am on retropie 4.8 and a pi 4.

Can I get some guidance on getting the subject working?

The package is talked about here on the retropie docs:

https://retropie.org.uk/docs/Runcommand/

"Manage packages" >> "Manage experimental packages" >> "launchingimages" >> "Install from binary"

For whatever reason, the images created from this package are not filling up the whole screen even though the retropie menus and all game emulators do. It's like the package is not creating the proper size images and I really don't have a good idea how to fix it. Below is an example of what my run command screen looks like. Thank you all for any guidance you can give on fixing this.

IMG_3188.jpg

@Concat said in Runcommand Images Preventing Runcommand Menu:

I'm better off just mashing :)

I hear you. I've made the same comment about a few fighting games in the past. 'Primal Rage' comes to mind.

@rbaker I've never been sure. As I said I just mash. It seems to work.

Oi Meleu, show d+ seus scripts... muito obrigado [],ao Carlos

@waltisfrozen This was already changed - if you update to the latest retropie-setup it no longer uses md5 hashes by default, but just includes system and rom name minus extension /path (excluding all characters except a-z A-Z 0-9 _ - in the format system_romname

for per emulator settings, the format is emulator_romname

@columboscoat said in Any way to disable or hide the yellow controller message when launching a ROM?:

In what way is your solution better than using the RetroArch GUI?

Now I'm at my laptop and I'm able (have patience) to type better than on my Android phone...

My solution pleases my own taste because when using RGUI RetroArch dumps the current status of every single option of the running instance in the retroarch.cfg, overwriting the previous content. All those useful comments explaining what the options do will disappear.

We all know that RetroArch documentation is very scarce and scattered. I think that the retroarch.cfg skeleton is a good resource of information about the RetroArch options.

Ah of course! Talk about not seeing the wood for the trees! Thanks everyone.

@BuZz
Thanks Buzz <3
https://github.com/RetroPie/RetroPie-Setup/commit/cc2d23c7fa40f2238f9175c5f0b250a9f5c272c8

never mind.

it seems with the launching screens that i got from here.

https://retropie.org.uk/forum/topic/4611/runcommand-system-splashscreens

i just need to spam the a button to get it the timing correct.

sorry all

@hansolo77 Thanks. :) There isn't a like but you can vote up posts etc which is the same sort of thing.

I have been using mupen64plus-rice-hi_res legend of zelda oot. But this has been happening with other emulators in the past. I remembered the way I was able to make changes was by launching a freshly loaded rom (this instance was NBA showtime n64) , never been played on this system before, and access runcommand. Once in there I can change the default emulator. Then I exit the runcommand, and can now change the runcommand settings on the problem rom. I know that seems really confusing. Sorry about that.

@edmaul69 How about using Dropbox?

@Rookervik Hi maybe you can do for psp and GameCube please?

You can mark this SOLVED! I remembered I was following another site's suggestion on creating ".SH" files to automatically launch games in DOSBox without having to manually type the commands. Along the way, I had modified the es_systems.cfg file to give it an entry so it would show as an emulator because it wasn't coming up after installing DOSBox.

It turns out, there's more than one es_systems.cfg file. The one I posted above was in the ETC path. I found another one under /opt/retropie/configs/all/emulationstation/

When I opened it up, I guess I had somehow split the line:

<command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ pc %ROM%</command>

into this:

<command>/opt/retropie/supplementary/ runcommand/runcommand.sh 0 _SYS_ pc %ROM% </command>

Once I backspaced each separation so it was on one line, it worked! Well, the "+Start DOSBox" entry works, but the ".SH" scripts I made do not launch the games properly, so that will be my next mission. Thanks for your help BuZz.

@Drakaen391 Yes, I am aware that scripts can launch scripts and do quite often. The idea of a single line bash script just to execute a python script is pretty silly though.

The matter is closed though. The devs aren't interested in the idea which is their right.

@sc0tt88 said in runcommand blinking cursor (no launch menu):

It didn't.

Well it should - but without any details from you I cannot advise (eg versions, and also if you are using a splashscreen)

I think I found the reason: The hex values that are getting sent are terminal-specific and don't work for my terminal. I fixed it (hopefully) by using curses which uses terminfo to translate to the actual terminal values.
PR soon... :)