@mitu @GoldManSex778

I'm sorry for not getting back to you sooner! The information always seems accurate when you're the one typing it! 🤣🤣

The screensaver displays videos just fine - I don't have an issue with black/blank screens. It is the game information it won't display. On my 3B+ I have set "Show Game Info On Screensaver" - ALWAYS and it displays the game name and system. On Windows it does not.

I should also mention that I'm using the Showcase theme on both my 3B+ and Win10.

Please add the info requested in https://retropie.org.uk/forum/topic/3/read-this-first to your post.
The controller configuration should be done in Emulationstation, it's then automatically translated into RetroArch configuration file(s) so you don't have to re-configure your controller in again in RetroArch.

@E3L1 , try this:
In terminal type:
sudo nano /usr/share/alsa/alsa.conf
Then Change
defaults.pcm.card to 1
To
defaults.pcm.card to 0
Save, exit, and reboot.

I figured it...
Firstly configure the new machine withing AmiBerry and save the config as whatever you like - in my case to set up a compatible Amiga to run a game which the default configs do not run.

Next hop over to RetroPie Configuration Editor from the main menu and choose option 2 - Advanced Configuration.
Then option 4 - Manually edit non RetroArch configurations.
Scroll down to option 26 - amiga/emulators.cfg and copy any of the standard existing default "rp-xxx" lines and replace with your own new filename from AmiBerry which you just saved.

When you next boot press a key to enter runcommand as the info window for runcommand pops up during the booting of the game.
Change the option no 2 - Select default emulator for ROM and select the emulator you saved.
Press x to launch.
That's it. From now on your game will load with the emulator you configured to work with the game and is launch able from ES directly.

Hope this helps to make someone elses' life a bit easier.

Happy xmas.

Cheers.

Rob.

I'm starting to think that the issue is with the mame2010 driver in libretro.
The inputs in other libretto emulators are not problematic (e.g. street fighter in Super Nintendo works fine with all buttons)... but many of the street fighter II sets in mame2010 have issues with second player buttons.

Something for the libretro people to fix I think.

@engrdanny Emulationstation by itself does not read inputs directly, but uses the SDL library to handle the gamepad, which in turn needs the OS to recognize it. Which driver are you using to configure your custom gamepad ? Is the gamepad recognized by jstest ?

ok I went and tried that. same issue. however i decided to start everything over and see if I am missing something. I have had the EasyHack Toolkit script work before so I knew there has to be more to this. well long story short. Looks like this was all due to a bad gamelist.xml file. Sorry to waste your time. (atleast i figured it out). :)

@buzz All good!
With the official script I can compile fine what I
needed!

I had the same issues using my Mausberry switch I had the blue and white cable mixed up.

@mitu said in Videos on system view screen?:

No, it's not possible right now - this feature is not implemented.

such a major bummer! I have a great idea but I guess I'll have to save that until they implement that function. Back to working on my theme. thanks!

@stoney66 said in EmulationStation Scraper saving html file as image:

megaman looks like he is playing ping pong

Yep, it's all I see in the forums :).

@mikee You should update also the RetroPie setup script, the latest version is not 4.3.8. Do the update for the setup script, then update Emulationstation again.

@alturis said in EmulationStation issue with marquee.png:

Or potentially an issue with how the ComicBook theme is setting up the marquee element. Will have to look at that later tonight.

Nah looks pretty simple and straightforward to me.

<image name="md_marquee"> <pos>0.74 0.086</pos> <maxSize>0.26 0.1</maxSize> <origin>0.5 0.5</origin> </image>

Though now I am wondering if is something with the handling of the "maxSize" feature of ES that is at play here.

@kinduff

I gotta say, it's a very intriguing use of ES. I commend your efforts.

Solved. Had to access emulator settings for the one second the game was booting and disable "Fast Memory (Unstable)". Boots fine now.

@carlosricardocm said in Launching chromium from emulationstation:

I get the following message:
Failed to put Xlib into threaded mode.
Gtk: cannot open display

In order to fix that, you need to follow this tutorial.
In the end, I only had to run the two installs below:

sudo apt-get install xinit sudo apt-get install matchbox-window-manager

I have a script called chromium[dot]sh in RetroPie/roms/chromium which contains the following line inside:
chromium-browser

After installing xinit and matchbox-window-manager, I've modified my Chromium launcher script exactly as instructed in the aforementioned tutorial.

Also I added the following to the file es_sytems.cfg located in /opt/retropie/config/all/emulationstation/es_system
<system> <fullname>Chromium</fullname> <name>chromium</name> <path>~/RetroPie/roms/ chromium</path> <extension>.sh .SH</extension> <command>bash %ROM%</command> <platform>chromium</platform> </system>

In my file, I've got:

<system> <name>chromium</name> <fullname>Chromium Web Browser</fullname> <path>/home/pi/RetroPie/roms/chromium</path> <extension>.sh .SH</extension> <command>startx %ROM% > /dev/null 2>&1</command> <platform>chromium</platform> <theme>chromium</theme> </system>

Note the <command> line: I've entered startxfollowed by the %ROM% parameter (which will get the script name) then an extra > /dev/null 2>&1 (this is to omit the output from the script commands, keeping a clean console).

Update:
Initially I had xinit in the command line to invoke the script from a window manager environment. A couple days after, while managing modules and plugins (throwing apt-gets at random, for no reason whatsoever), I ended up somehow breaking xinit as in it would no longer start the X-Server. So I found a workaround by replacing xinit with startx in the <command> line, and all was good again.