Ok, pngview was already installed on my system and used by the PiBoy OSD. I found a png loading used in the installscript of the firmware and I can reproduce this when I want with a single line added in my scripts. It's exactly what I was looking for !

@sleve_mcdichael Thanks for your help

@Folly Thanks, I got everything running now!

@mitu It doesn't let me verify it

@duglor set this (and all other retroarch settings) via the configuration editor: https://retropie.org.uk/docs/Configuration-Editor/

it's in the basic settings menu - you can see it in the screenshots

@icer363 said in Skyscraper not showing videos?:

I have it enabled in the settings.

Do you enabled it in the Skyscraper settings or EmulationStation (or maybe both) ?
Note that after you scrape (with videos enabled), you need to run the gamelist generation step again in order for the videos to show up in EmulationStation.

Ok, so the stutter goes away if I set baud rate of Bluetooth to 460800:
Run sudo nano /boot/config.txt and then append the following

# Enable autoprobing of Bluetooth driver dtparam=krnbt=on # Increase Bluetooth baud rate dtparam=krnbt_baudrate=460800

The idea was taken from here: https://github.com/Arkq/bluez-alsa/issues/205

Now only the playback delay left.

Correct, @mitu , I created a separate system that lists the conf files:

<system> <name>p2000t</name> <fullname>Philips P2000</fullname> <path>/home/pi/RetroPie/roms/p2000t</path> <extension>.conf .CONF</extension> <command>/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ p2000t %ROM%</command> <platform>p2000t</platform> <theme>p2000t</theme> </system>

Runcommand looked good:

Parameters: Executing: /opt/retropie/emulators/dosbox-sdl2/bin/dosbox -conf "/home/pi/RetroPie/roms/p2000t/Monkey.conf" fluidsynth: warning: Requested a period size of 64, got 480 instead fluidsynth: warning: Failed to set thread to high priority fluidsynth: warning: Failed to pin the sample data to RAM; swapping is possible. DOSBox version SVN Copyright 2002-2019 DOSBox Team, published under GNU GPL. --- CONFIG: Loading primary settings from config file /home/pi/RetroPie/roms/p2000t/Monkey.conf SDL: Current window pixel format: SDL_PIXELFORMAT_ARGB8888 MIDI:fluidsynth: loaded soundfont: /usr/share/sounds/sf2/FluidR3_GM.sf2 MIDI: Opened device:fluidsynth One joystick reported, initializing with 4axis Using joystick Xbox 360 Wireless Receiver with 6 axes, 15 buttons and 1 hat(s) Using driver "opengl" for renderer

I am happy to investigate more if it helps the community. If we collectively believe this is a problem with a 20-year old emulator, I am also content to call this one good enough and run without a joystick. :)

I don't think stty would help here, but try adding quiet to the cmdline.txt line, this should suppress the boot messages. See more options at https://retropie.org.uk/docs/FAQ/#how-do-i-hide-the-boot-text.

🙂

In general, if the command line does strange things, it's a good idea to check if the command was entered correctly. As in this case, one missing or wrong character can be the culprit.

I like that suggestion even more than mine :-)

https://github.com/RetroPie/RetroPie-Setup/wiki/FAQ#why-emulationstation-doesnt-start-automatically-after-an-update-

Okay, for some reason, the screen command needs an sh after the -L on a Raspbian-based Retropie. sh starts a new shell with the script in it. On my Desktop PC running Kubuntu Linux 18.04, the command works without the sh, but on my Raspberry Pi running Retropie, it needs the sh to work as intended.

Whatever, please try this with an sh behind -L:

screen -S bezelproject -L sh /home/pi/RetroPie/retropiemenu/bezelproject.sh

@mitu Right, so you're saying it's unable to catch a signal while it's "paused". Makes more sense now. I had assumed it would have forked the emulator and thus be ready for interrupt signals to act on in the background.

Anyway, this is way more than I really have any business knowing. Graphics and GUIs have never been my thing and I know enough about inter-process communication to get me into trouble, but that's about it. Thanks for the help. Really useful.

@mitu Indeed - nothing seemed to happen. However I did already have a bunch of funky characters in the command line prompt, so perhaps those prevented the "reset" command from working.

This is the second time it's happened to me in the last two days, so I will try to type in "reset" on a clean command line prompt the next time it occurs (although it didn't seem to work for the previous poster and his issue is a carbon copy of mine).

@jasonh1314 The ascii art welcome is produced by running retropie_welcome, a shell function added by the install script to your shell start-up file.
If you open the $HOME/.bashrc file, the last lines should be

retropie_welcome # RETROPIE PROFILE END

If you accidentally overwritten your .bashrc, then the welcome ascii art function is not run when your login session starts.

@dankcushions Thanks for letting me know, is much appreciated :-)

@nunyabizniss Meant to add, I'm using a 3b+

hey mitu, thank you!

could you explain me how to or give me a link to read how to do re-compiling?