• Current state of lr-mame?

    Moved Help and Support
    5
    0 Votes
    5 Posts
    389 Views
    H

    @barbudreadmon
    I figured it out.. it was older retroarch mame cfgs
    in the retropie configs folder.
    I deleted them and it came right on.
    No sound problems, no black screens.

  • Run Wii games on Raspberry Pi 4?

    Help and Support
    2
    0 Votes
    2 Posts
    2k Views
    mituM

    Yes, it's possible to start the games, but they will run very poorly. If you want to play Wii games, try another system - preferably a PC (x86).

  • Is it possible to run retropie x86 on a pi4

    Help and Support
    5
    0 Votes
    5 Posts
    453 Views
    S

    @DeathByOrangez PCSX2 is for PC computers only, it won't run on Raspberry Pi.

  • 0 Votes
    3 Posts
    431 Views
    R

    @mitu Thank you!

    It's possible I'm confused by the implementation vs. the Raspberry Pi version...EmulationStation uses X11 on x86? I assumed no, and that was my whole motivation for not doing so (plus the obvious memory and time burn from launching an X display you aren't going to use anyway). If that's not the case, it sounds like xrandr is absolutely the way to go (and the closest analog to what I'm doing today).

    onstart will almost certainly be required, because my display lies and says it can't do PAL ;)

  • 0 Votes
    5 Posts
    746 Views
    S

    @barbudreadmon Looking at the Udoo website, this is a much more powerful device than mine with better processor, graphics and more RAM. I think this explains why I can't emulate PSOne on such an old low-end machine.

  • Moonlight on RetroPie x86

    Help and Support
    2
    0 Votes
    2 Posts
    312 Views
    mituM

    No, there isn't one included in RetroPie, only the 'embedded' variant is included.
    You can install one of the releases for Moonlight-Qt since it provides packages for Linux which should work on Ubuntu/Debian.

  • 0 Votes
    22 Posts
    3k Views
    W

    I hade some trouble with this as well so I created a script that keeps the window active and maximized.
    Hope it can help others :)
    https://github.com/william-andersson/rpie_run

  • 0 Votes
    3 Posts
    488 Views
    S

    @mitu Thanks for the reply. I apologize, I'm rather new to using RetroPie on Ubuntu. I was just going by what the default value was on the emulator selection screen when you press a button while the ROM is launching.

    9247c15c-3e81-4c7c-bd79-bea1c6087614-image.png

    I ended up installing lr-mupen64plus-next as you suggested, and the difference is amazing :) This is what I was hoping for. Thanks!

  • 0 Votes
    6 Posts
    695 Views
    DjDiabolikD

    @mitu said in impossible to build lr-PUAE on Intel NUC:

    Upstream project will fix their build on newer distros with a recent glibc, you'll have to wait until they do so to use lr-puae. Use an older Ubuntu LTS version or one of the other Amiga emulators available (lr-puae-2021, fs-uae) in the mean time.

    mmmm.. using a old version of lts it's not best idea for me. For absurd i have installed OS recently on this miniPC :)
    Try to consider fs-aue but reading this guide quickly:
    https://retropie.org.uk/forum/topic/18409/guide-getting-emulationstation-to-work-with-fs-uae
    Need to re-read whit more accurancy and know if it's on my knowledge :)

    You're probably low on RAM - on an 64bit PC I thin you need at least 8Gb (if not more) to compile current MAME.

    mmmm also here.... my actually miniPC as only 4GB of ram DDR3. i can limit the usage of build in some mode (problably on future i can't build future version or update thru retropie-setup but but it's better than nothing) ?

  • 1 Votes
    4 Posts
    2k Views
    thelostsoulT

    @Crush Proton is not new and has reached version 7. It is based on WINE and DXVK and some other stuff. You can find out what is compatible in Steam: https://www.protondb.com/

    I use Proton on my desktop PC instead WINE. It can be used without Steam running too. But the Proton version needs to be downloaded from Steam UI first. I recommend Proton Experimental. Here is a script, you can try: Proton script Or you can try one of the forks, who added some more stuff and made it a bit better.

  • Redream on x86_64

    Help and Support
    10
    0 Votes
    10 Posts
    1k Views
    S

    @Crush said in Redream on x86_64:

    @sleve_mcdichael would it still help you if i test that now that @BuZz will fix the tags?

    Buzz will probably take care of it but it might get you up and running sooner if you don't want to wait for the fix to push through. I think 64bit is probably is the right flag to use here; looking at the other modules it's only used a couple of times, but it is used outside this particular module, while x86_64 is not (not as a module_flag, anyway. Its use for other things like as a platform identifier in this same module is still fine, I think.)

    pi@retropie:~/RetroPie-Setup/scriptmodules $ grep -rni . -e module_flags | grep -e 64 ./supplementary/splashscreen.sh:16:rp_module_flags="noinstclean !all rpi !osmc !xbian !aarch64" ./libretrocores/lr-dolphin.sh:18:rp_module_flags="!all 64bit" ./libretrocores/lr-kronos.sh:18:rp_module_flags="!arm !aarch64" ./libretrocores/lr-uae4arm.sh:18:rp_module_flags="!all arm aarch64" ./libretrocores/lr-mupen64plus.sh:18:rp_module_flags="!aarch64" ./libretrocores/lr-mupen64plus-next.sh:18:rp_module_flags="" ./emulators/mupen64plus.sh:18:rp_module_flags="sdl2" ./emulators/redream.sh:17:rp_module_flags="noinstclean !all gles31 aarch64 x86_64" ./emulators/np2pi.sh:17:rp_module_flags="sdl1 !all rpi !aarch64" ./emulators/dolphin.sh:18:rp_module_flags="!all 64bit" ./ports/solarus.sh:18:rp_module_flags="!aarch64" ./ports/love.sh:18:rp_module_flags="!aarch64" ./ports/love-0.10.2.sh:18:rp_module_flags="!aarch64"
  • 0 Votes
    6 Posts
    554 Views
    mituM

    That means pcsx2 didn't install properly. Try re-installing and then look in the last log file under $HOME/RetroPie-Setup/logs to see if there are any errors related to the installation.

  • 0 Votes
    9 Posts
    3k Views
    mituM

    @DTEAM Please open a separate topic and post a verbose RetroArch log, along with the details of your system.

  • Downgrade to 86x now go back to 64x

    Help and Support
    10
    0 Votes
    10 Posts
    944 Views
    H

    I got retroarch libretro's pcsx2 working if anyone wants
    to make a script for this one as well..

    A different bios location is needed so far...

    Instructions are in the last post on thread link below.

    https://retropie.org.uk/forum/topic/31074/pcsx2-install-on-ubuntu-20-04/3?_=1633627954899]

  • 0 Votes
    11 Posts
    3k Views
    pjftP

    @gaz I am out of ideas here, and having never used the Lightgun outside of the Raspberry Pi, I would definitely suggest bringing this back to the Sinden Lightgun discord, as Andy will likely be able to best help troubleshoot the scenario.

    Specifically, if the gun works in other software such as the test apps, it might be something simple that I am not knowledgeable enough nor experienced enough to detect. The Linux-specific channel there might be the best to get to the bottom of this, but do share whatever you find here, as if there's something that we can change on our end I suspect we'll be happy to accommodate.

    Sorry about that.

  • SOLVED: joy2key_sdl.py throwing error

    Help and Support
    9
    0 Votes
    9 Posts
    971 Views
  • 0 Votes
    3 Posts
    6k Views
    johnodonJ

    Thanks @brandflake11

    I got this one figured out. It was a PITA! :)

    Long and short of it is this...

    xrandr treats both displays and one large one (extended). You can see below that Screen 0: is recognized as 5760x1080 (4K TV + 1080P monitor):

    Screen 0: minimum 320 x 200, current 5760 x 1080, maximum 16384 x 16384 VGA-1 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 800mm x 450mm 3840x2160 30.00 + 24.00 29.97 23.98 4096x2160 30.00 24.00 29.97 23.98 1920x1080 60.00* 59.94 30.00 24.00 29.97 23.98 1920x1080i 60.00 59.94 1680x1050 59.88 1280x1024 75.02 60.02 1440x900 59.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.00 30.00 59.94 29.97 24.00 23.98 1024x768 75.03 70.07 60.00 800x600 72.19 75.00 60.32 720x480 60.00 59.94 720x480i 60.00 59.94 640x480 75.00 72.81 60.00 59.94 720x400 70.08 DP-2 connected 1920x1080+3840+0 (normal left inverted right x axis y axis) 509mm x 286mm 1920x1080 60.00*+ 50.00 59.94 1920x1080i 60.00 50.00 59.94 1680x1050 59.88 1280x1024 60.02 1440x900 59.90 1280x800 59.91 1152x864 75.00 1280x720 60.00 50.00 59.94 1024x768 70.07 60.00 800x600 60.32 56.25 720x576 50.00 720x480 60.00 59.94 640x480 66.67 60.00 59.95 59.94 720x400 70.08 HDMI-2 disconnected (normal left inverted right x axis y axis)

    This is what my autostart.sh file looks like:

    #! /bin/bash #set primary display and resolution. xrandr --display :0 --output HDMI-1 --mode 1920x1080 --primary & #call cvlc to play a startup animation. Wait for it to end before continuing. cvlc --random --play-and-stop --play-and-exit --fullscreen --video-on-top --no-video-title-show --quiet --gl=any --preferred-resolution=1080 ~/RetroPie/splashscreens &> /dev/null #start ES in a terminal (openbox). gnome-terminal --full-screen --hide-menubar -- emulationstation --no-splash

    Naturally, feh sees the display the same way so you need to use the --geometry switch to identify the starting pixel on the 2nd monitor. This is what my runcommand-onstart.sh looks like:

    #! /bin/bash ROMPATH="$3" ROM_BN_EXT="${ROMPATH##*/}" ROM_BN="${ROM_BN_EXT%.*}" CONTROLSIMAGE="/home/pi/RetroPie/roms/$1/images/$ROM_BN-controls.png" feh --geometry +3840+0 "$CONTROLSIMAGE" &>/dev/null &

    This essentially gets the full path to the romfile and trims the extension to get the rom base name.
    It then builds the path to the controls image I need and displays at the starting position I tell it to (3840x0) which is the entire screen of the 2nd monitor. When I exit the game, and merely kill feh via runcommand-onend.sh:

    #! /bin/bash killall feh &

    This is working perfectly. Now I just need to find a fancy graphic to display on the 2nd monitor when it isn't showing controls. :)

    John

  • 0 Votes
    5 Posts
    2k Views
    YFZdudeY

    @mitu said in x86 Ubuntu install trouble / dependencies:

    You could change your current Ubuntu repository mirror and retry (apt update first). You can use apt-cache policy to check the troublesome packages and see what version are available and from which repository.

    I was unable to find held packages, but you got me going in the right direction. For whatever reason, my sources.list file had a comment in it that suggested that because I used a smaller ISO it might not have been the full file. Perhaps a side effect of not allowing online updates during install.

    So I got hold of a more 'full' listing of the official sources and ran apt update and it suddenly had way more packages to update and then the install script could find more of what it needed.

    Thanks!

  • 0 Votes
    3 Posts
    945 Views
    mituM

    @yfzdude said in Trouble creating desktop launcher file [SOLVED]:

    I'm still curious if any GNU/Linux wizards know why the original method was not working. Either way it is working now.

    Because runcommand needs a terminal to show the launch menu, launching ES directly would break this. On Debian and friends, you can use x-terminal-emulator as the terminal starting command, which would be expanded to one of the installed terminal emulators.

  • 0 Votes
    2 Posts
    414 Views
    S

    Alright, update, it is still possible. I modified the code in the original post to create folders based on the game name instead of relying on ps_iso_tool to extract a game ID and creating folders based on that. Seems to be working perfectly.

    (I have absolutely no idea how to code, so I'm kinda shocked I was able to figure this out.)