Announcing Pegasus Frontend
@fluffypillow Ah, sorry, I don't really know. My previous update was around where PageUp/Down was introduced.
Right now I'm on alpha7-99-gafcfb69 (pretty sure it's the latest - updated a few days ago).
@andershp No problem; looking back the changelogs after the favorite support was added, I suspect the custom filters update that might have broke it. Will double check.
fluffypillow last edited by fluffypillow
Meanwhile I've just finished uploading the first builds of the frontend chooser, you can get them here. The program can also install the frontends, but that requires launching with
sudo(because the RetroPie scripts). If you've set to start Kodi on boot, that should be remembered. There's basic gamepad support, nothing special. Just extract somewhere and run, should work out of the box.
halfmanhalfcake last edited by
@fluffypillow Good work on the updates
General question on platform compatibility, would it be possible to port Pegasus to the Nintendo Switch as an homebrew app for example? Would like to use it as a frontend for emulation.
@halfmanhalfcake Well I'm not familiar with Switch development, but in theory if there's at least software rendering support (or better, OpenGL/Vulkan), and the emulator programs can be launched with parameters, then yeah, it might be possible.
As for the weekly changelog+recap:
- Created a frontend chooser for Retropie, downloads here
- Fixed the favorites filter not working (thanks @AndersHP)
- Pegasus now logs if there are directories in
game_dirs.txtthat couldn't be opened (might help @Seya16)
- Android builds are now properly optimized
- Compatibility modules (ES2, Steam) are no longer built for platforms where they aren't available (ie. Pegasus won't search for ES2 on Android)
- Cleaned up the code of the main theme a bit
- Fixed some minor mouse issues
Seya16 last edited by
Hi me again,
So with the new update I'm now sure that the directories paths that I put on the game_dirs.txt are recognize (What I did is to change some folder's name in the text file to see if it will be able to find the directories or not) but I couldn't get it to find the games. I did create the collections.pegasus.txt where I put some basic text for testing purposes but nothing still have the same problem... Maybe it's just me, maybe I did somethings wrong but I don't know where :/...
Anyway thanks for your dedication and your hard work on this project.
@seya16 Hmm interesting, so the directory paths are correct, but Pegasus still doesn't see the txt files (no
Found /path/to/whatever.txt). I've just made a version with additional logging, you can get it here. It will also print warnings when
- no collection files found in a directory
- no games found in a directory
- the file opening has failed (though it seems it doesn't reach that point for you)
Seya16 last edited by
Big thanks mate ! but it does show how stupid I am :/ I didn't see that I have to put the collection text file on the rom directory not on the pegasus-frontend folder. So sorry, I feel that I did waste your time on this :/....
But thanks again, at least it's make me test the app furthermore, so I will come back at you when for feedback purposes.
@seya16 Hey no problem :) Yes, collection files are local to a rom directory; a kind of global collection file support is also on my roadmap, but not implemented yet.
@fluffypillow Favorites all good again, this frontend is getting better and better, almost perfect for me now.
What's the status in making it possible to remove/turning off the few seconds of code when booting the frontend, booting games, and quitting games?
It would look so seamless without these strings of code in between.
@andershp Actually I have an idea for improving the seamless launching, I'll see if I can try it out the weekend. The other two issues are somewhat different though:
- The startup delay can be reduced by optimizing some lower-level code, which is a bit time consuming, but I've started working on it already (as a side-side-side project).
- Pegasus reloads the UI when the launched program says "Ok, I'm done!". Not sure how much that could be improved, but I'll see what can be done. Perhaps it'll also speed up when the startup time gets optimized.
So this week I've updated the Qt version (ie. the UI code); this should make Pegasus start up somewhat faster and may fix a color depth issue someone mentioned earlier. It's a big change under the hood, so feel free to report if something's broke. The changes are not available on Android/Windows yet, there are still some build errors to be fixed there.
I've also put up some actual content to pegasus-frontend.org, so you can find the latest downloads there too. Also started working on more seamless game launching, there are just some silly bugs left to fix.
- Finished the work on the seamless launching; the UI now disappears only when the launched program has started successfully. Any delay left now is up to the launched program.
- Added a
--silentcommand line parameter, which will make Pegasus not print anything to the terminal. Might come handy for startup, or in case a launched program itself shows the terminal.
- Updated the Android release too with the new Qt libs.
Aand the Windows build got the update as well.
Darksavior last edited by Darksavior
I couldn't get any games to show up in the windows version. Steam games automatically showed up. I'm probably doing it wrong, even after reading the documentation. I'd like better examples. I converted my
gamelist.xmlfrom my pi to
metadata.txtand made a
game-dirs.txtthat it doesn't care to see. I'm not sure how
collections.txtwork and did it like the example but got nothing as well.
I also tried the windows version of ES to see if that might get me anything but Pegasus will only see that in a specific place and even then it tells me it can't parse
es_systems.cfgor something but I'd rather not use this method..seems like extra work.
game_dirs.txt, with an underscore; fixing that should solve the collection/metadata loading. But yeah, providing some actual example configs would be a good idea.
BJRetro last edited by
What is the effect of adding this package to a RetroPie Raspberry pie already running emulation station? Do you just not see emulation station any more and this front end replaces it? If so is there any way to “go back” or switch between them easily or at that point do you have to reload a backup image/fresh install? Thanks! (Looks very nice by the way, which is why I might want to try it, but on the other hand I finally have a 128gb setup that I can “just play” for the last month or two and am a bit worried about screwing that up).
BJRetro last edited by
I see there is a front end chooser and that you can edit a certain file to run Pegasus automatically but I didn’t see instructions on how to do that or what you need to do in that file to change back to emulation station running automatically. Also seems from some posts (though hard to read all 700) that if you change front ends you might need to change the locations of RomS and their metadata so that is the sort of thing I am getting at - once you download this how hard from a practical standpoint is it to switch back and forth or “go back” to the ES version even with the front end chooser or editing of the startup file? Thanks - I am sure this is a noob question.