Announcing Pegasus Frontend

fluffypillow

PS. I'll be away for a few days, excuse me for late replies.

AndersHP

@fluffypillow Faaantastic! I can't wait. Enjoy the time off (if that's the case, anyways).

phulshof

@fluffypillow said in Announcing Pegasus Frontend:

@phulshof I've used the es-tolkit-videos for GB and N64, and ScreenScraper videos for NES and SNES. All GB and N64 videos have the same H263 format, and have display problems, and all NES/SNES videos use AVC, but don't have any problems. If I remember correctly, AVC (alias H264) is the format that can be hardware accelerated on the Raspberry Pi (with gst-omx), which is why it has no issues, I guess.

I just tried AeroFighters Assault (USA) for the N64 on my Linux PC; that part works fine. I'll try to find some time tonight to set up my pi, and test it there as well. I'll keep you posted.

phulshof

I just checked on my pi as well: no issues there either (though the videos are far from great quality to be honest; the ones from EmuMovies are miles ahead). So, we're down to two possibilities:

I installed a gstreamer (codec?) library that you did not.
RetroFE uses gstreamer differently from your code.
Could you give me the output of the following command?
apt list --installed | egrep "gstreamer|libav"

fluffypillow

@phulshof Yeah the videos work fine on desktop, I've only noticed problems on the Raspberry so far. The Qt framework isn't perfect either, so yes, there could be a bug in the Multimedia module as well. Here's the output of the command on my Pi 3: https://pastebin.com/71tQiQ0y.

( By the way, those are test videos for ES theme development, which is why their quality is so low. )

Kqpout

@fluffypillow Thanks for your work !

Alas, the windows builds you provided don't seem to work on my W10 (neither does anything)
Will try building with latest sources tomorrow.
(we need this on windows as a successor to ES)

Darksavior

If anyone was wondering, you can scrape the wheel (logo) pictures with universal xml scraper. Make sure it keeps them as png or they won't be transparent. For some reason it won't scrape some game's logos despite there being one on the ss site.

The names aren't the same, of course. In a windows command prompt you can just do rename *-image.png *-logo.png

fluffypillow

@Kqpout I've just tested it on a friend's Win10, worked fine (in the sense that it produced a black screen and empty systems bar, since he didn't have any emulators or ES installed). What kind of problem you get, does it fail to launch?

Also you can get the latest automatic Windows build from here (choose the flavor=mingw row, then select the ARTIFACTS tab). The builds aren't on the GitHub releases page yet because they run on a different site; hope I can fix this eventually.

Kqpout

@fluffypillow Yes, it just does nothing, no error, no window, the process just close after one or two seconds. Launching from a cmd window show nothing.
It's the same with the latest build, even as administrator or with compatibility.
Win10 64 bits, 14393.1358

Kqpout

So I tried to compile it! And saw the error!

"Found C:/Users/pophi/.emulationstation/es_systems.cfg
Required parameter <extension> is missing or empty in a <system> node"

And indeed one of my systems didn't have <extension>.

Now it works :)

But maybe it should run anyway or display an error message ?

fluffypillow

Yeah, error reporting on the UI is not yet done :)

Darksavior

@fluffypillow Will we be allowed to resize the boxart rows in the future? I believe that will fix the look of the arcade sections using flyers for boxart. 3 rows should make the flyers legible.

fluffypillow

@Darksavior at the moment the number of items per row is fixed (in the theme), with "hardcoded" overrides for certain systems. I certainly want to change that, but not sure what'd be the best way for that.

fluffypillow

Week 17:

external scripting support has landed
- documentation available in the wiki
a bunch of documentation fixes and source code improvements
- added links to the latest Linux/Windows builds in the README
- better organization of the files in the Windows package
- developers: added a list of packages and PPAs you can use on (desktop) Ubuntu to the Build guide to easily build Pegasus (no need to compile or install Qt manually)
created a RetroPie script, on review at the moment

Darksavior

@fluffypillow Bug in pegasus-fe_alpha2-47-g3fee22f_rpi2-static.zip.
If you scroll down your games, eventually they'll all disappear. Then it's unusable. Can't even see the text either. The last build I tried was #31 i think..

retrolang

I can also reproduce @Darksavior 's bug, but only with a keyboard. I can't scroll fast enough with a controller for it to occur. I need to hold down the down arrow key on a keyboard to make it happen. Don't really see any errors at the command line but: this one: glGetGerror 0x505, not sure it's related though. If you scroll back up, previously loaded images disappear and will fail to load.

Darksavior

@retrolang Yes, I managed to exit pegasus with the distorted image to see the same error. I did use a keyboard to scroll since pegasus won't use my dpad to control the menu, but it does SEE the dpad as an analog stick for some reason..

fluffypillow

I can also confirm the bug on Pi 3 + keyboard (though it also freezes for me sometimes). The bug appears somewhere between #39 and #45; I'm trying to find out which commit exactly. It seems something causes Pegasus to go out of memory (that's the OpenGL error 0x505).

pjft

@fluffypillow That's video/texture memory. You're trying to load textures but the GPU memory is not available.

You can check by running

sudo vcdbg reloc

When that happens.

You may want to implement something similar to ES Video RAM's texture cycling - but addressing the current implementation's shortcomings :)

Happy to chat if it'd help.

fluffypillow

@pjft GPU memory and textures are handled by the Qt library -- which I've recently updated on the build server to 5.9.1. It's supposed to be a minor maintenance/bugfix release to 5.9, but as it turned out it was the cause of the bug. So for now I'll revert to 5.9, and try to report the bug to the Qt devs.