@keith-f-kelly said in Enhancements for Dialog Navigation/Controls:

I don't see why any button needs to be mapped to the TAB key. TAB doesn't appear to be used anywhere in the menus. Am I missing something?

The physical key Tab is by default mapped to traverse the button selection (in the bottom area) in retropie's dialogs. More generally it is mapped to traverse the input fields/controls of the different widgets available in a dialog.

For 0x0a / 0x0d: I do not stick to 0x0a I just took what was there, maybe it is the cleanest to sent the terminfo's cr instead of 0x0a or 0x0d.

@mitu I have attempted that but you dont have to wait to when using the up down left right arrows, i have tested this and it works before the time runs out

@mitu said in runcommand verbose logging:

Since this is a RetroArch option, I guess you can enable it from the RetroArch settings or add it to its configuration file.

Thats what I did. But, as a shot in the dark I added verbose = "1" to the /opt/retropie/configs/all/runcommand.cfg file and that seems to work. Undocumented feature?

@mitu Yeah -- there's no error message readily available when the runcommand dialog isn't shown. I should probably just do a clean install since that is the recommended route, likely something didn't upgrade correctly at you say.

@russellb Would you be so kind to share it? Your approach is probably the most convenient way. TIA!

It was indeed an issue related to the format of the runcommand-onstart.sh file - it was in DOS format. I opened/resaved it in MAC format (using nano). Problem solved. Thank you for your help!

Feh lets you configure its actions for keyboard keys and mouse buttons. See its manpage for further information, and this post in the official Raspberry Pi forum. The action to exit feh is called quit in its configuration files.

So, maybe you could configure a quit key in feh and set a very high delay time in Retropie. Just an idea after a little research, I don't have any practical experience with this.

I've just had the exact same problem this morning and thought I was going mad!

This is actually a great feature as it provides further protection against guests inadvertantly entering it even after applying Kiosk mode.

Many thanks Mitu!

Ah, my apologies, you are absolutely right. I was using the pre-built image on a Pi3 and the manual install on a Pi4. Once I flashed an SD card with the pre-built image for the Pi4 and booted that up I saw the same video options. Thanks for the insight!

@Nicxiv Now I can play Buck Rogers Planet Of Zoom. Thanks!

I found the issue if anyone else has the same problem. I had saved a core config in each of the emulators which caused it to be set in what ever resolution it was in at the time. Configs are stored in opt/retropie/configs/all/retroarch/config/all/retroarch/config/(name of emulator). I deleted them and re set them up in 720p.

So EmulationStation runs Runcommand.sh internally? It doesn't have to be called by an sh file? What about just dosbox? I have no problems executing the sh files with that in emulationstation or cli. Only reason I use lr-dosbox is because I can't seem to control the volume of my monitor's speakers directly.

You might want to change the font to something bigger (xterm -fn <fontname>) if your resolution will make the fonts tiny.

@mitu I apologize. I didnt know. I just ordered it with ready to play out of the box. Then I updated from source to get the newest version of everything. I didnt realize that against license or whatever. My apologies.

Everything works perfect except killer instinct and I'm just trying to change the emulator it uses to see if I can find one that works better. I guess Ill try another forum not directly associated with retropie.

Thanks

@joesnow81 there's plenty of info already here and even more knowledge in the minds of the users here. Stick around and you'll learn things, I certainly have. Welcome to the forum!

@grzzlybr said in ROMs do not launch:

@mitu True, although obviously many people have it running fine from a desktop session (I did before these issues).

Sure, but that's not a configuration that's tested and supported.

I have just tried running RetroPie from boot and it seems to be working fine with local ROMs, but not with ROMs using symlinks (which were working fine before). So I guess that's one issue (sort of) solved and another found!

Can you add more details - and possibly the log file asked earlier, not that Runcommand should be working again ?

If the emulator itself doesn't implement bezels, then there's not much that can be done to externally overlay an image, since most emulators need exclusive/fullscreen access to the video output.

@quicksilver said in Can no longer select video mode after update:

@psyke83 thanks it looks like it's working again. Something I've noticed in general though is that I have multiple listings for the same resolution/refresh rate. On previous pi models there were usually just the different CEA modes listed. Is this difference because of the different drivers/hardware that the pi 4 utilizes?

Yes, we query the available modes via the kernel modesetting API, which doesn't distinguish between CEA or DMT modes. If you look carefully at the duplicates in your list, however, you'll see that there are differences beyond the resolution and refresh rate, such as the aspect ratio encoding, horizontal/vertical sync polarity, etc.

Technically it's still possible to use tvservice for querying and changing modes on RPI4, but if you do change the mode, the underlying KMS framebuffer subsystem will not be aware of the change. This would mean that your monitor would be set to the correct mode, but the applications themselves would detect the framebuffer/refresh to still be set to the original resolution and thus show a cropped image, etc.

@clyde i have a custom solution for this since im running on ODROID with SDL2 and so if im not quitting the process soon enough im getting graphical glitches with on screen borders or other weird problems:

This is my solution by now - its not perfect since it can make problems when a rom cant load (then i have to restart the system) otherwise it works flawlessly on my ODROID with retropie:

Basically i have 2 scripts
runcommand-onstart.sh (mine did not exist since i installed retropie from the distro directly)

pkill fbi pkill tail # the image i want to load loader="/etc/emulationstation/splashes/$1/launching.png" if [-f "$loader"]; then # if image is found - start fbi with the image and no timelimit, also start the check script in same directory fbi -1 -t 0 -noverbose -a "$loader" </dev/tty &>/dev/null & (/opt/retropie/configs/all/check.sh) & fi

and the check.sh script:

# you have to enable retroarch logs - always log everything input=/opt/retropie/configs/all/retroarch/logs/retroarch.log timeout 15 tail -f $input | while read LOGLINE # if any of this lines are seen - kill everything related to launchimages - in this case fbi and tail # "Found display server" is the first command in the log before the emulator kicks in do if [[ $LOGLINE == *"Found display server"* ]]; then pkill tail pkill fbi fi if [[ $LOGLINE == *"Failed to load content"* ]]; then pkill tail pkill fbi fi if [[ $LOGLINE == *"Bus error"* ]]; then pkill tail pkill fbi fi done

So what this is doing:
it starts FBI forever and the check script checks the logs for "exit tokens" - if a exit token is hit every process related to the imageloading gets killed.

If the rom cant load before 15 seconds (timeout 15 - set this to the possible highest value) the process should get automatically killed.

works btw with the newest (current master in repo) mame-plus and mame emulators at my side. If you have "Enter Problems" - do what i said before - just add the clean commands for the tty additional to the pkill commands

maybe that idea/solution gives some ideas to you :)