Please do not post a support request without first reading and following the advice in

Announcing Pegasus Frontend

  • I'm a bit occupied with other projects at the moment, there might be no updates this week either :/

  • I’m probably missing something really obvious, but how do you make a game pad player one? Currently, I’m using a USB wireless keyboard to type the command that launches Pegasus, so the keyboard defaults to first player, meaning I can’t use my Bluetooth game pad to start a game once it’s selected. Only player one, the keyboard, can control anything in game. I can, however, use the game pad outside of the game.

  • @shaolinbastard Pegasus has nothing to do with a pad/kb being player 1. Install joystick-selection to assign your pad as player 1 or disconnect the keyboard. I don't remember which section of retropie-setup that's in.

  • Yes, Pegasus itself works from both keyboard and gamepad; what an emulator/game considers P1 then depends on that particular program.

  • @darksavior Thanks! I'll poke around with it more this weekend. I love how much this frontend is progressing and think the UI far surpasses any theme I've tried for ES.

  • And I back with a weekly changelog! Since the last video, I was asked for some more tutorial material, so for now the updates will likely be a bit more focused on the usability aspect. Here's what changed this week:

    • Game directories can now be changed directly from Pegasus, no need to edit game_dirs.txt manually
      • It's not well tested yet on all platforms though, so feel free to report issues
      • Known bug: on Windows, file selection may work correctly at the moment, due to the file system handling differences. Will be fixed.
    • Added a very basic help/about screen to the main menu
      • Will likely have more content in the future, but at least the documentation site can be reached
      • Known bug: clicking on the button may not open the site in the browser. Will fix it.
    • Fixed a very rare case where the loading screen might not disappear
    • Fixed the main menu going crazy when the program's window is resized
    • Mouse- and finger navigation improvements

  • Update: the path issues on Windows and Android should be fixed now.

  • Hi,
    First of all, i want to say BIG THANKS to your effort! I'm looking for a loooong time for a way to use my rom collection in a "comfortable" way, but since years - it was always just a half solution.

    Retroarch was / is a nice one, with nice cores, but i not really like the "optics" (even they made the xmb, a ps3 like theme or the new one... i dont like it that way). Then i was looking for front-ends like EmulationStation or "solutions" like Hyperspin, or even a paid front-end by a spanish guy ... but i was always disappointed - it was too much or too less...
    then, some days ago, i found pegasus-frontend - and when i found out, it started already over a year ago, i was shocked, that i couldn't find it ealrier! (why it's so hard to find your project? we should change it!)

    I hope prey, that you wont stop the work on it, coz it's amazing! Its with theme support, it multi-plattform, it's VERY EASY to use and open for - everything - to use with!

    Secondly - a little wis-list and some questions :P

    1. It would be cool to have an options in future to change the color or completely deactivate the "seleced-cover-background" (the blue, android'ish background).

    2. It there a way to prevent pegasus from using the "es_systems.cfg"
      [ the gamelist.xml work's fine, but when i don't rename the es_systems.cfg, the covers of the nintendo entertainment system not showing up!? - all other systemss cover work, but the NES ones not - even i always copied the nes "node" and edited for all other systems ...]

    3. What i have to do, to add covers / banners for the steam games? do i have to make a gamelist.xml, like for other systems for steam or is there any other way?

    4. When i start a rom/game, pegasus closes and some seconds later, retroarch or a game launches. Is there a way to make it more "seamless" (it's still much better then on the emulationstation, but maybe i made smth wrong - coz i've read somewhere, that on pegasus it's already "seamless")

  • @purg-derren Thanks, glad you like it :)

    1. It would be cool to have an options in future to change the color or completely deactivate the "seleced-cover-background" (the blue, android'ish background).

    I haven't got around to it yet, but theme specific options is a planned feature, so yup, it will be added eventually.

    1. It there a way to prevent pegasus from using the "es_systems.cfg" ... the covers of the nintendo entertainment system not showing up

    Hm that's interesting, could you upload the es_systems.cfg somewhere (eg. pastebin or in a new issue)?

    1. What i have to do, to add covers / banners for the steam games? do i have to make a gamelist.xml, like for other systems for steam or is there any other way?

    There's no built-in way for that at the moment, so for now creating collection/metadata files and placing the assets there would be necessary. I should improve this in the future.

    1. Is there a way to make it more "seamless"

    Well I'm not sure it can be improved further than that. Pegasus closes when the launched program reports that it has started -- if after that it still takes seconds for the program to show something on the screen, that's not a thing I can control. As a workaround, you could do tricks like setting up a full screen black background, or running Pegasus in silent mode (if you're on a Pi or using a terminal).

    why it's so hard to find your project?

    I guess marketing isn't my strong suit, I'm a bit relying on word-of-mouth :)

  • And another weekly changelog!

    • Third-party data sources (EmulationStation and Steam) can now be enabled/disabled in the Settings menu
    • Most settings are now stored in <config-dir>/settings.txt (instead of pegasus-frontend.ini, which is somewhat more troublesome to handle internally)
      • This will also cause your current settings (fullscreen, locale and theme) to be reset -- sorry about that!
    • Made mobile friendly
    • Added a "Getting started" guide to the documentation
    • Fixed some outdated information and typos in the documentation
    • Fixed the documentation link in the Help menu not reacting to mouse clicks
    • Fixed window focusing issues with the locale and theme selector panels in the Settings menu
    • Fixed the game directory selector issues on Windows and Android

    Also in case anyone's interested, I've launched an experimental Patreon page. Don't worry, whether it's successful or not, Pegasus will still continue to be free and open source.

  • Also I've just marked this release as Alpha 9, as there might be some new (and experimental) features coming this week.

  • Super, thanks!

  • Changelog time!

    • It is now possible to manually set assets in the metadata file
    • It is now possible to manually set default assets in the collections file
      • Except it's not supported yet in the default theme...
    • It is now possible to use absolute paths in the collections and metadata file
    • It is now possible to add additional search directories to the collections in the collections file (in addition to the one where the collections.txt file itself is placed)
    • It is now possible to create a global collections file, a la ES2
      • Pegasus will look for a collections.txt file under <config dir>/global_collection (name may change in the future)
    • It is now possible to set summary and description for collections
    • It is now possible to set the working directory when launching things
      • It can be set per-game and per-collection as well
      • Now correctly defaults to the directory of the launched file (fixes some interesting occurences on Windows especially)
    • Asset searching is now documented
    • Added GOG support for Linux (desktop) and Windows
      • Windows: it just works. Similarly to GOG Galaxy, games installed older than a few years might not be detected, due to a change in the games' installers. In this case, try downloading the game again from and reinstall it.
      • Linux: there's way less information available offline, so support is a bit hit and miss. Games installed in the default location (<home>/GOG Games) can be detected, but assets might me missing. (If you have the games somewhere else, you can always just create symlinks). If you have games that refuse to show up, feel free to report it.
      • Known issue: There is no video support yet because most of them are hosted on YouTube, which is a pain to use outside of a browser
    • Updated the documentation here and there
    • More accurate reporting of errors in config files

    As always, comments are welcome.

  • @fluffypillow Awesome,keep going!!!!!

  • I've signed up just to post here :) I think Pegasus has a lot of potential, loving it so far. Happy to follow your progress @fluffypillow , I don't like the lack of customization ES offers.
    My only question for now is, are there any "finalized" themes that I can try? (looking at you @tronkyfran ;) huge fan here )
    the flixnet theme seems broken as all I see is two entries with black background.

    Thanks and keep up the good work!

  • @fluffypillow Keep up the good work, still using it over any other frontends.

  • @GeekOB Actually I do plan spending one of these weeks with creating themes (gotta show the power of Pegasus!) but then always end up working on things less visual. Please bear with me until then :)

    In other news, I've changed the URL of some pages in the documentation (in case someone has links/bookmarks to them). Also rearranged some contents and added a few new pages too.

  • Yet another announcement, keyboard keys will likely change in the next release. Currently the game details panel is opened with Ctrl and the filter panel with Shift. I'd like to free these keys to avoid interference with eg. text editing, so instead the new keys would be I (as in info) and F (as in filter/find) instead. Would this cause issues for anyone?

  • administrators

    @fluffypillow these would just be deafults no? Are. There any plans to be able to configure menu controls like with ES?

  • @herb_fargus yup, just the defaults... except you can't change from these defaults yet :) There are plans to also make keyboard keys configurable, it just haven't got implemented yet.

Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.