Announcing Pegasus Frontend
@dudleydes the Flixnet theme didn't show the RetroPie icons because it was set to only show the "grid icon" picture. I've just added support for the box art image, which should now show up instead if there's no grid icon. The result isn't as nice, but I guess it's better than having no image at all.
lilbud last edited by
@fluffypillow What do you use to scrape the images for Pegasus? I'll have games with scraped art that show up as nothing.
@lilbud I've used Universal XML Scraper to get the box art images, then added the
-boxFrontsuffix to the files (with the linux tool
rename) and moved them all into
<romdir>/media. Similarly did the same for the logo, screenshot and video files. The "grid icons" (wide images used by eg. Steam/Ice) are from consolegrid.com, for which I've manually wrote a simple scraper. I'm also using the files from https://github.com/mattrixk/es-toolkit for testing as well.
If you have troubles loading some images, make sure they have the right suffix. If ES can show the box art of a game, it should also work in Pegasus; if not, that's likely a bug.
HurricaneFan last edited by
@fluffypillow One thing with ES though is it doesn't need a suffix to show an image. My gamelist has box art and videos in ES and they are the exact name as my rom. Just with a .png or .mp4 extension.
lilbud last edited by
fluffypillow last edited by fluffypillow
@HurricaneFan yup, that's also supported; suffix-less
jpgmaps to the box front image, and video files to -- oh, looks like I've actually forgot that, thanks. ES loads whatever it sees in the image/video tag; Pegasus too can read the same XML files, which is why if an asset works in ES, it should work in Pegasus as well.
@lilbud indeed it is, but its interface was easier to work with and I was lazy.
@fluffypillow Thanks for the info. I have updated the mapper file so that I can switch between themes and navigate them with my controller.
I have also updated the flixnet theme and the RetroPie menu icons now appear. I used ImageMagick to resize the icons to a 16:9 aspect ratio. @HurricaneFan I can confirm that gamelists and boxart from ES2 work fine without any further work.
On exiting Pegasus, there is a segmentation fault and the error
evdevkeyboard: Failed to query led statesin the lastrun.log. I don't know if this is an issue.
I would like to play around with themes as I would prefer to have box art in the flixnet theme rather than grid icons. Do you have any links that may be useful to get to grips with QML?
Finally what does Live Theme Reload refer to? And how do I get the clock in the corner?
@dudleydes "On exiting Pegasus, there is a segmentation fault": yeah it's quite annoying, but luckily not critical. Some underlying component seems to crash at exit sometimes; I'd suspect one of the GStreamer plugins. I'll see if I can find out what fails exactly.
Personally I've found most QML guides somewhat lacking/incomplete (at least if you wish to build a full program from the ground up), but the language isn't hard and you can get the hang of it after a while. There's a short tutorial here and a longer one here (mainly chapters 4-6), and the QML documentation is useful as well when you have to look up a component. In practice you won't need to know that much to create a simple theme, but you can also make it very fancy if you wish.
Live Theme Reload
Well I've planned to add a function to reload the current theme on a key press (eg. F5), but I haven't implemented it yet.
And how do I get the clock in the corner?
Heh yeah that's still missing, I'll start experimenting with it the weekend.
@dudleydes sure, I'm using Qt Creator too, it works really well for Qt/QML projects.
- added support for calling scripts before and after launching a game
- added support for suffix-less video file assets
- the Flixnet theme can now use box art images
Other than that, I was tidying up the source code; this should make it easier to read, extend and test it in the future.
@fluffypillow After spending the past week looking at using the Linux Joystick Mapper program (
loadmap) with the Pegasus Frontend, I don't believe it will work seamlessly as I would've hoped. After running a rom and exiting back to Pegasus, if I then try to exit Pegasus, then Pegasus reloads and I cannot use my PS3 controller. I can usually exit Pegasus with a keyboard and in the console, there will be the following messages relating to the earlier attempt to exit Pegasus:
evdevmouse: Could not read from input device (No such device) Gamepad: Could not read from input device (No such device) evdevkeyboard: Could not read from input device (No such device) evdevkeyboard: Failed to query led states
This is an issue for users who share their PS3 controller between their Pi and their console or other device(s). With the Linux Joystick Mapper program, it's not possible to unplug the controller from the Pi and then replug it and expect it to work. The
loadmapprocess must be killed and restarted for the controller to work in Pegasus. What I have been doing is to have a script to kill
quitscripts folder so that I can exit Pegasus and then am free to unplug my controller.
I'm thinking using xboxdrv is a better solution and then maybe create a udev rule to force Pegasus to use js1 while xboxdrv is running. Having looked through some documentation, I really have no idea how to get started.
@dudleydes I think I can get a PS3 controller for testing this weekend. I have a few ideas to improve the gamepad handling, I'll see if I can solve this problem. Ideally Pegasus should work without any udev hacks.
After running a rom and exiting back to Pegasus, if I then try to exit Pegasus, then Pegasus reloads
You mean, you press Quit, and instead of quitting, Pegasus restarts? How did that happen? :) Or you mean after Pegasus reloads, you cannot quit, because you can't use the PS3 controller?
Darksavior last edited by
@fluffypillow hopefully analog can work as well.
AkiAfroo last edited by
i still dont know how to run pegasus on windows. (when launch show me black screen) what i could read is because need a setup file or i have to indicate where to look. (thats the problem i have.)
i have my emulationstation full configure any tips where/how start. ?
thanks in advance.
@fluffypillow In the hope that you may be able to replicate the issue of Pegasus reloading when I select to
Exit Pegasusfrom the
Quitmenu, here is my set-up.
I have a PS3 controller connected by USB and a Rii mini wireless keyboard plugged into the pi.
I have built the Linux Joystick Mapper binary and placed it in the
/home/pi/joymap/folder for testing purposes. In the same folder, I have the mapper file,
In the folder
home/pi/.config/pegasus-frontend/scripts, I have placed a
kill-joymap.shscript in the
You can find copies of all of these files at my gist.
To replicate the issue, I launch a rom and then exit back to Pegasus. From the
Quitmenu in Pegasus, I choose to
Exit Pegasus. The console will briefly appear before Pegasus restarts. I have included a copy of
lastrun.logwhen this happens in the gist.
My thinking is that the line
Gamepad: Could not read from input device (No such device)in the
lastrun.logsuggests that, for some reason, the PS3 controller is not available. Because of this, the Linux Joystick Mapper program fails to run and the PS3 controller can't be used in Pegasus after it has restarted.
fluffypillow last edited by fluffypillow
@AkiAfroo Pegasus looks for the ES2 directory
.emulationstationin you home dir,
C:/Documents and Settings/Username/on Windows. You can override the home dir by defining the environmental variable
PEGASUS_HOMEbefore launching Pegasus (
HOMEis also supported). The easiest way to do that is to create a
launch.batwith the following content:
set PEGASUS_HOME=C:/some/directory pegasus-fe.exe
and start Pegasus using this script. The directory you set
PEGASUS_HOMEto should contain the
.emulationstationfolder. You can use whatever editor you like for creating the file (Notepad should be fine too).
@dudleydes Thanks for the detailed report! It seems the exit issue is caused by your
start-joymap.sh, where you launch a new instance of Pegasus. When you exit from that, it is when your script actually ends, and thus the original Pegasus is restored.
@fluffypillow Thanks for the reply. I can see the logic now and how the
start-joymap.shscript would be starting a new instance of Pegasus each time I exited a rom. Not the most efficient way of doing things!
I searched online how to run commands in the background and found that removing the command to launch Pegasus in
start-joymap.shbut leaving the ampersand should work. I have tested this and it seems to work fine.
AkiAfroo last edited by
@fluffypillow thanks i will try as soon as..
@dudleydes I was just playing around with multiple PS3 controllers, and noticed that you can run xboxdrv in daemon mode, which should solve the reconnection issues. I've launched it like this:
sudo xboxdrv --detach-kernel-driver --mimic-xpad -s --next-controller -D --dbus disable
There was a bug in xboxdrv where unplugged controllers didn't un-register themselves, but that was fixed in version 0.8.6. You might want to try that if you have troubles.
Also you can see a bunch of debug information if you set the env var
QT_LOGGING_RULES="qt.gamepad=true"before launching Pegasus.