@thesnackist I haven't tested on a Pi 3, admittedly! Though I wouldn't be surprised if something is missing on the Pi 3 that was added in the Pi 4's hardware when it switched to the A72 CPU.

@folly said in PICO-8: Retroarch lr-retro8 core installation script:

@benmclean

Can you share your controller.svg ?
Let me see how it looks on Linux.

I tried it on RetroPie and it looks correct on there. Just not on Windows. Weird.

@dirtbagxon Fantastic! Thanks for your support!

John

@dteam said in Development of module-script generator for lr-mess and mame standalone:

@folly
For Google Drive issues, would it be easier if I put everything on GitHub?

Let's wait for Matt first, perhaps he can improve his script.

But indeed github could be a better way in the long run.

There are some advantages like :

forking easy collaborating perhaps skipping files when cloning for an update

But there could also be some downsides :

how much data will we have in the future and what is the data-limit of github ? I think cloning doesn't work when we add files manual locally because it wants to sync with the repository. So testing files on the harddrive becomes more difficult. Perhaps we also face some ownership issues

We can do some tests with a few files and see how it works.

@ln_rc said in Daphne - Removing Fullscreen Parameters to Avoid Errors:

@DirtBagXon @johnodon Thank you for the information! I added back the full screen, it definity the $params and not the -fullscreen. This is the commands file that I used based on a tutorial on this webpage:

-nocrc -noissues -noserversend -latency 950 -x 640 -y 480 -bank 1 00110111 -bank 0 10011000

Is there a better version of a general .commands file to use?

I'll take a look at the hypseus emulator as well. The Daphne emulator has been working pretty well for me, but it doesn't hurt to see all the options.

There isn't really a one size fits all .commands file, as these files are game specific. i.e. each game has a different version in its own folder:

https://retropie.org.uk/docs/Daphne/#command-parametres

Alter arguments and get it to do what you want it to do. If you are including -bank switches then you need to start reading, and understanding, the arcade dip switch setting configurations. These are at the more complex end of config.

Dip switches are documented on the excellent DLP site: http://www.dragons-lair-project.com/tech/
General options for Daphne are documented here: http://www.daphne-emu.com/mediawiki/index.php/CmdLine
Hypseus has a few more: https://github.com/DirtBagXon/hypseus-singe#extended-arguments-and-keys

Feeling overwhelmed :) Daphne is notoriously tricky to configure, so just spend some time with it.

Remember, you don't have to include any options. Defaults (empty .commands file) work fine most of the time.

If you did remove $params as the last argument from the daphne.sh script, you should add it back and fix the commands files. This option allows you to customise all games individually.

Note: These same arguments in $params (i.e. <game>.commands files) are also used by the hypseus.sh script, so any issues you address in Daphne will be ported to Hypseus Singe automatically.

There are some options that are now deprecated in Hypseus, -nohwaccel being one. These don't work well in the port to SDL2, especially on the Pi.

 

@sleve_mcdichael said in lr-duckstation - Experimental new PlayStation 1 emulator:

Does this also work in reverse?

I answered my own question, it does indeed work in reverse. I have a game I'm sure I've saved since I switched to duckstation. Switched Duckstation core option to use Libretro .srm as memory card type, then named the _1.mcd file back to .srm and it loaded up fine.

New running games:

Sin Gold the latest GOG version runs out of the box with highest settings (even in 1920x1080, although a little slow and with a tiny HUD. So I prefer 1280x720) Jazz Jackrabbit 2 GOG comes with the plus patch, which also renders in 800x600. The (opening) videos are glitched, but gameplay seems to be fast and fluent.

Where I have some problems is Alien vs. Predator Classic 2000 from GOG. The game runs out of the box, Fullscreen and very fluent, but after some time there are some texture errors: They glow in bright colors and the lighting gets bright and glitchy. I'd think this should be fixable, but I don't know how...

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

@mrc_munir have you seen a lot of graphic errors?
Is it only speed and sound issues for the emulator?

@mitu

Haven't read all the posts.
I understand seeing it now.
Btw, Thanks for restoring it ;-)

@arcadez2003 Thank You!

Please add Vs. From Below

https://vs.frombelowgame.com/

@csl

No problem but I think we see things from a much different angle.

I don't know the exact answer, you should ask a "global moderator".
But, I think, it basically comes down to how much time the developers can or want to spend and what they think what should be added or not.

And when something isn't there, some people become developers themselves.
Perhaps you can contribute to the open source community too.

I think you can just add gameandwatch in line 50 of /home/pi/RetroPie-Setup/scriptmodules/libretrocores/lr-mess.sh
I haven't tested though !
Let me know if it works for you, perhaps we can learn from this.

https://github.com/digarok/gsplus/issues/52

godfollower created this issue in digarok/gsplus open Enhancement request- RetroArch/libretro integration #52

bringing this thread back from the dead, as i encountered the same issue on my pi zero. any updates?

Now that I am back to playing with Wayland/Sway, I found the best solution is what @etheling was doing...using imv as the image viewer. The difference is that I am using runcommand-onstart.sh to display the loading screens so I don't have to mess with editingruncommand.sh. The key is to NOT name you launch images *-launching.png (I use *-launch.png) as this will invoke feh via runcomand.sh.

#!/bin/bash ROMPATH="$3" ROM_BN_EXT="${ROMPATH##*/}" ROM_BN="${ROM_BN_EXT%.*}" LAUNCHIMAGE="/home/pi/RetroPie/roms/$1/images/$ROM_BN-launch.png" imv-wayland -f -s full -x "$LAUNCHIMAGE" & &>/dev/null IMG_PID=$! sleep 4 imv-msg "$IMG_PID" "q"

@dirtbagxon wow, thanks. Time Gal works like a charm