Announcing Pegasus Frontend

fluffypillow

@troopaking Nah, while it would be nice, I don't really have the time to manage and maintain a separate distribution. You can make one however, if you'd like to.

fluffypillow

@baksbani I guess it might work? Might need to build it manually though.

fluffypillow

It's been a while since the last update, so here's a recap of what happened the summer:

Added Android 11 support
- While this has been made to be backward-compatible as possible on Pegasus' side, but due to Android restrictions, some apps may no longer support opening files directly, or support it differently on Android 11. You might wish to contact the app developers in this case.
Added Playnite support (thanks polson!)
Added Lithuanian translation (thanks mrqside!)
Updated Russian translation (thanks mrqside!)
Linux: Fixed shutdown/reboot/suspend support in Flatpak (thanks j8r!)
Mac: Added support for the portable.txt file on this platform too
Steam: Improved support for custom game library locations
Steam: Updated the list of ignored entries (ie. Proton and runtimes)
LaunchBox: Fixed rating values going over 100%
LaunchBox: Fixed imported Steam games not launching correctly in some cases (thanks polson!)
LaunchBox: Fixed the favorite support for Steam games (thanks polson!)
Metadata: Added experimental support for URI values as files, which can be used to customize games found by third-party sources (eg. steam:12345, lutris:some-slug, etc.)
Updated the gamepad database
Themes API: Fixed support for JSON objects with memory

Technical:

It is now possible to build Pegasus using CMake; you can find the details in the documentation (https://pegasus-frontend.org/docs/dev/build/)
Updated SDL to 2.0.16

fluffypillow

New update! 2021-09-26

Redesigned the gamepad layout editor
You can now disable checking the existence of game files (useful for large game sets)
Improved loading bar
Added Japanese translation (thanks waitingmoon!)
Steam: Updated support for the recent client changes
Theme API: You can now use Qt.labs.qmlmodels (https://doc.qt.io/qt-5/qtqml-models-qmlmodule.html)
Theme API: Updated SortFilterProxyModel to the latest version

justindu

@fluffypillow Is it possible to run pegasus within the X11 desktop environment on a RPi4?

I installed the experimental packages within retropie_setup.sh, and tried to launch from terminal, and after a long scroll of text, the terminal window hangs, and no UI launches. - FYI - emulationstation and all the games are working, just not Pegasus. I'm looking for the ability to navigate and exit with a mouse/touchescreen, which emulationstation does not seem to do.

Darksavior

Setting a custom resolution for pegasus with a json file is no longer working. This is a new retropie install fully updated with the latest 12/16/2021 build of pegasus. At least pegasus uses the custom 1440p resolution that I set for my pi.
I changed to the kms driver and that fixed everything along with the ability to set other resolutions. I'll keep the rest if you're curious.

egl.json contents:

{
  "outputs": [
    {
      "name": "HDMI1",
      "mode": "1920x1080"
    }
  ]
}

autostart.sh contents:

QT_QPA_EGLFS_KMS_CONFIG=/home/pi/egl.json pegasus-fe

Verbose log:
https://pastebin.com/ZLbdLQWQ~~

fluffypillow

@darksavior Hm, wasn't KMS the default on the Pi 4? Or were there some driver changes recently? I can mention it in the docs if that's the case.

Darksavior

@fluffypillow Retropie is still on Buster and it wasn't the default. Maybe on Bullseye it is.

mitu

@darksavior said in Announcing Pegasus Frontend:

.. it wasn't the default..

As far as the rendering API is concerned, Buster is the same as Bullseye, so nothing changed here - DRM/KMS is still used on the Pi4.

KryPtAlIvIaN

@fluffypillow

I'm by no means a programmer but I managed to get Pegasus running on a batocera image.

Once installed, Pegasus did not detect any of game.xml files from Emulation Station. Is there a specific path it searches? Can I manually point Pegasus to look in a specific path? I know you can for metadata.txt but did not see how to with game.xml

Thanks!

fluffypillow

@kryptalivian Great! Pegasus looks for game XMLs in the directories set in its es_systems.xml file, which should be located at at ~/.emulationstation/ or /etc/emulationstation/ – the places where the official ES looks for them too. You can also set a custom path for the systems XML by adding a custom setting line to Pegasus' settings file: providers.es2.installdir: /path/to/your/dir, in which case Pegasus will look only in this dir.

Darksavior

@fluffypillow Hi, is a 64bit version available for the pi3/4? At the moment, if I want to use pegasus on a pi3 64bit os, then I have to manually install the pi4 version then install the missing 32bit dependencies.

fluffypillow

@Darksavior Hi, no, there's no prebuilt binary for 64 bit, but it should be technically possible to compile it. In theory though shouldn't the 32 bit release also work on the 64 bit OS?

Darksavior

@fluffypillow I don't believe so. Pegasus will complain about missing dependencies. After searching for answers, I found out that I had to install them with :armhf at the end of each one for pegasus to see them. 64bit bullseye (unsupported in retropie for now) is using newer video drivers so the pi4 version works on the pi3b+.

Darksavior

@fluffypillow Btw, the controller bug of acting crazy returning to pegasus after exiting a game still exists. The only way to get rid of it is to press Start, go inside the side menu, jiggle the dpad (or analog stick on my ps3 pad), and exit the menu.

fluffypillow

@Darksavior I think I might have managed to solve that; could you try the latest version?

Darksavior

@fluffypillow So far so good. Thanks! I tested by exiting a game 10 times. I've only tested wired so far. The controller would go crazy (wired or wireless) around the first, second, or third time exiting a game.

Darksavior

Nevermind. Moved the conv to github.