Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

Announcing Pegasus Frontend



  • @fluffypillow it's the same issue for me

    another request, will you add support to other games from uplay and origin? it would be great



  • @fluffypillow

    With regards to adding native support for LEDBlinky to Pegasus it would require modifications to Pegasus. If you are interested in doing this, the developer (support@LEDBlinky.net) of LEDBlinky is more than willing to work with you on the integration.

    Current features missing from LEDBlinky when not integrated with Pegasus are not limited to below.

    • Lighting the front-end controls
    • Lighting the game controls as you scroll through lists
    • Running various animations while the FE is active, etc

    Lighting the relevant controls for a non-MAME game requires the FE to pass the ROM/Game name to LEDBlinky. If Pegasus provides a way to run a script file when events occur, then you can run LEDBlinky commands in those scripts. This requires Pegasus to expose one or more events like FE Start, List Select, Game Start, Game Quit, FE Quit, etc.

    What do you think?



  • @wallmachine Pegaus already supports some of these events.
    https://pegasus-frontend.org/docs/user-guide/scripting/



  • @Meldrak > will you add support to other games from uplay and origin? it would be great

    Yes adding support for them would be really nice (and also for things like Epic or Battle net), but I think I'll wait with them until we reach the beta version (there are still a bunch of things to work on!).

    @wallmachine Yes that sound exactly like something you could customize well with scripting. The only missing thing from your list is probably the on-scroll-change effect, as that depends on the selected theme and not handled by Pegasus internally.



  • Also a weekly update!

    • Added gamepad button repeating (ie. you can now hold down the gamepad buttons/axis to scroll through your games)
      • (this is for platforms other than Android, as it already worked there)
    • Added manual line breaking (\n) support to the metadata format
    • Fixed a crash on Raspberry Pi 1 and Zero
    • Main theme: Fixed selection pointing to nothing on collection change
    • Main theme: Fixed incorrect game info on filter change
    • Metadata converter site: Fixed Logiqx manufacturer entries not getting converted
    • Updated to Qt 5.12.3 (brings minor optimizations and bugfixes)

    Known issues:

    • The main theme forgets the last launched game. Will be fixed soon.


  • @jdrassa said in Announcing Pegasus Frontend:

    @wallmachine Pegaus already supports some of these events.
    https://pegasus-frontend.org/docs/user-guide/scripting/

    @fluffypillow said in Announcing Pegasus Frontend:

    @wallmachine Yes that sound exactly like something you could customize well with scripting. The only missing thing from your list is probably the on-scroll-change effect, as that depends on the selected theme and not handled by Pegasus internally.

    I'm all ears if someone has already done this because I wouldn't have a clue where to start with the scripting.

    Just to confirm something like this won't be implemented?



  • @fluffypillow Maybe make it so it doesn't delete the binary before checking to see if there's a new version. My pi boots to the terminal prompt because it couldn't find pegasus. I'm not a normal user so I replaced the last binary available manually.

    Available releases:
    https://github.com/mmatyas/pegasus-frontend/releases/download/continuous/pegasus-fe_alpha11-81-g60dcaef_android.apk
    https://github.com/mmatyas/pegasus-frontend/releases/download/continuous/pegasus-fe_alpha11-81-g60dcaef_win-mingw-static.zip
    Package platform: rpi3

    Looks like the latest Pegasus release is not yet available for this platform. This happens when the build is so fresh it's being uploaded right now, or when there's a technical problem on the download server. Either way, this is a temporary problem, so please try again in 1-2 minutes. If the problem persists, consider reporting it on the forum!



  • @fluffypillow said in Announcing Pegasus Frontend:

    Added manual line breaking (\n) support to the metadata format

    This particular feature update seems to have an unintended side effect of not allowing you to use a directory that begins with the letter 'n' in your metadata file (at least on Windows where it uses backslashes as the directory separator).

    I happened to be setting up some n64 files tonight and it took a few minutes of wondering why in the world it was not finding the files until I renamed the path!

    So this does NOT work with the latest build:

    directory: ..\..\..\roms\n64
    

    However this format will work as the letter n is no longer the first character so it doesn't interpret it as a newline:

    directory: ..\..\..\roms\testn64
    


  • Yeah I should stop doing releases late at night...

    @Darksavior ok, should be fixed now. I think removing the binary is how the ReroPie setup script operates, I wonder if that could be customized? Will also see if I can improve the release uploading, sometimes things seem to get lost on the way...

    @msheehan79 ah yes that wasn't intended. I've reduced the \n replacing to the description and summary fields now, which were the original targets. Will also make some way to write \n there too later.

    @wallmachine not inside Pegasus, yes. I'd prefer not to add Windows-, device- and emulator-specific code if it can be avoided, but this seems to be something one could control well from scripts. Maybe you could contact the developer, perhaps they already have a set of scripts or commands you could call with Pegasus.

    EDIT: I've just found some documentation on their page, this could help with writing scripts.



  • Anybody else running front end with ROMs on external storage on shield TV? I'm wondering if it's normal for the front end to take quite a while to initially load ROMs from external hard drive when I was running from the internal storage I had about 3,000 games that loaded fairly quickly now on external I have about 5,000 tried with both the HDD and SSD And it takes a couple minutes to say how many games found then another minute to go into the frontend but when I exit a emulator after playing a game it goes right back the front end and loads up fairly quickly I don't know if it's a bug or its just because the amount of games/assets?



  • @jerzeeloon there have been reports of slow USB access, but it seems to be depending on the device. Do you see anything out of order in the log file (<storage>/pegasus-frontend/lastrun.log)?



  • Weekly update! The week was more spent with experimenting and trying out a few things, so only some smaller changes this time:

    • Added support for disabling the mouse cursor if needed
    • Fixed the file selector not appearing for multifile games
    • Fixed the main theme not remembering the last launched game

    Also there'll be likely no updates next weekend (I'll be away for a few days).



  • @fluffypillow is there a way to configure/map controls inside pegasus-frontend and tell retroarch to use that configuration from pegasus-frontend?



  • @spartan not yet :(



  • Hello,
    I test Pegasus-fe since some times, and it's very promising. Unfortunately, it's difficult to find new themes.
    I 've find only an additional one (very nice, so it's the one I used)...

    I've just a question, and don't find it in the docs. Is there a way to change the video playback volume ? or simply disable the video snapshot sound ?



  • @carlhungus74
    I too would like this volume-feature, I would guess that the video playback is consistently about 30% louder than the actual game sound.



  • I just installed Pegasus this morning and really like the look of it. I'm currently using a SN30 PRO controller from 8bitdo and I have them configured and working properly in the front end. When I launch a game they don't work however the keyboard I have attached does work. The controller works perfectly in EmulationStation.

    Any suggestions on how I can fix this?


  • Global Moderator

    @Magma You'll need to configure the controller in your emulator also, Pegasus is just the frontend, has no influence on the emulator's settings.



  • @mitu I have to configure it per emulator even though it worked fine in EmulationStation on Retropie? How would I go about doing this? I didn't see a per emulator option in Pegasus.

    Is there a way to just copy the settings that were used in EmulationStation?


  • Global Moderator

    @Magma You didn't mention you're using RetroPie. If you configured the controllers in Emulationstation, at least the RetroArch cores should work. Can you get a verbose log from Runcommand from a RetroArch based emulator ? and post it on pastebin.com ?



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.