• Retropie on a PC - video issue

    3
    0 Votes
    3 Posts
    418 Views
    testudoT

    @andini

    If you are using Wayland as your display server (now default on Ubuntu 22.04 on) try switching to Xorg instead.

  • Waveshare 12287 not working with retropie

    5
    0 Votes
    5 Posts
    430 Views
    Z

    @mitu Thanks! I will give it a go and get back to you :-)

  • And suddenly no ScummVM Games are working...

    20
    0 Votes
    20 Posts
    4k Views
    windgW

    @10vorne
    You will found the info about scraper media paths here : https://retropie.org.uk/docs/Scraper/

    Of course it is possible to copy the configs folder. Inside you will find configuration files about emulators, retroarch,controllers, emulationstation and some others important files.

    You can read about backup options here : https://retropie.org.uk/docs/Updating-RetroPie/#making-a-backup-option-2

  • FBNEO Cheats?

    11
    0 Votes
    11 Posts
    6k Views
    B

    @Retro-Arcade-Fan said in FBNEO Cheats?:

    made a dummy cheat.dat file in bios/fbneo

    Why would you need this ? FBNeo won't read it

  • Installation of Xpad driver failed.

    16
    0 Votes
    16 Posts
    2k Views
    M

    @windg Nice.

  • Retroarch recording and sound

    3
    0 Votes
    3 Posts
    1k Views
    2Play2

    @hellricer I was about to say that you might have overrides (reading your top post), therefore the diff output location
    on RA 1.15 the output dir is simply named records and the configs go to records_config folder (for example you can have custom config.cfg file in there.

    As per RA docs you need also to have custom FFMPEG compile with
    --enable-libx264 --enable-gpl --enable-libmp3lame options
    but this does not fix the hissing sound which I believe you hear when you start the recording.
    As you stated, the output file though is video/audio ok which I also confirm from my testings

    Since you say you tested all other options in video_record_quality, you can test this override config and retest

    Option 1:
    Edit your main retroarch.cfg file in /configs/all/ and set
    video_record_quality = "4"
    and save. You can do from network share or locally to the file if easier for you.

    Option 2:
    create a config.cfg file, in /configs/all/retroarch/records_config/
    and add the above line in there and save.

    If you compile the ffmpeg as per docs you can add even more settings to it such as:

    vcodec = libx264rgb acodec = libmp3lame audio_global_quality = 75 sample_rate = 44100 threads = 0 video_preset = ultrafast video_record_quality = "4"

    or just

    video_record_quality = "4"

    Then select in ra the file or again change in your retroarch.cfg
    from
    rgui_config_directory = ""
    to
    rgui_config_directory = "~/.config/retroarch/config"

    Forgot to add. If you use shaders you should also enable in either option the
    video_gpu_record = "true" default is false BUT i noticed with lossless it causing video stutter.

  • lr-genesis-plus-gx crashes with "Bus error"

    12
    0 Votes
    12 Posts
    1k Views
    mituM

    @Machtroid Thanks for the confirmation. Btw, if you upgrade now (again) the OS packages, there's a new kernel & firmware update (20230509~buster-1) that should fix this and the config.txt change should not be necessary any-more.

  • Issue with latest update on RPI4

    7
  • Getting rid of "scanlines" in lr-x1 (Sharp X-1)

    15
    0 Votes
    15 Posts
    1k Views
    J

    @sleve_mcdichael That did the trick. Scanlines gone. Thanks all!

  • Lightgun Breaking Controls

    4
    0 Votes
    4 Posts
    571 Views
    B

    @mitu Thank you. Your fix worked. I really appreciate you taking the time to help as this was driving me crazy. All I need now is to figure out how to dial in the adjustments for this light gun.. gameplay isn't exactly smooth at the moment.

    Thanks again.

  • Cannot run SD Snatcher, MSX2 [SOLVED]

    172
    0 Votes
    172 Posts
    60k Views
    mituM

    @fryguy1 Please don't post links to ROMs or ROM sites.
    Not sure why this reply was needed, since @Folly already provided a solution in one of their earlier posts, but I guess the more the merrier.

  • core do not support save states with lr-pcsx_rearmed

    18
    0 Votes
    18 Posts
    3k Views
    S

    @140714071407 it looks like you've got the old ZeroJay version of RetroPie-Extra. Currently it is maintained by ExarKunIv at https://github.com/Exarkuniv/RetroPie-Extra

  • RetroPie Hotkeys names in the autoconfig folder

    2
    0 Votes
    2 Posts
    244 Views
    mituM

    See here in RetroArch's source.

  • Dreamweb and ScummVM 2.6.0 git

    10
    0 Votes
    10 Posts
    1k Views
    1

    @windg Thanks for the tip with the graphic. Unfortunately, deleting the shortcuts didn't help. Before I actually do a clean install, I'll open a new thread with a suitable topic and...hope :)

  • Help with X68000 emulator

    3
    0 Votes
    3 Posts
    617 Views
    C

    @mitu I could solve the problem and now I can play the games.

    The issue was with the bios file names. The files were in capital letters. I changed that and worked without inconvenient.

  • 0 Votes
    10 Posts
    4k Views
    YFZdudeY

    @eje211 said in Dolphin works from the GUI but not from Emulation Station:

    There are still a few more things to configure, such as getting RetroPie's shortcuts to work in Dolphin, but at least the games start!

    If you are referring to the Hotkeys, you would have to be running lr-dolphin for that to work. The standalone emulator does have the ability to configure hotkeys, but you will need to do it through the dolphin settings menu.

  • Save State Issues

    3
    0 Votes
    3 Posts
    678 Views
    1

    @mitu Is there a way someone could walk me through step by step verbose logging like what that is and how I do it. I've been given this link
    https://retropie.org.uk/docs/Runcommand/#launch-with-verbose-logging
    and I still kinda have no idea how to go about doing it.

  • Lost WiFi with latest update {SOLVED}

    21
    0 Votes
    21 Posts
    4k Views
    AddisonA

    Other Pi is now back to faster wireless speeds as well.

    Awesome! :D

  • 0 Votes
    15 Posts
    2k Views
    D

    I banged my head over this for some time before coming up with a solution.

    The problem is that when you hit that power button, an interrupt is sent to the login daemon, telling it to shutdown the system. You can't interrupt that in any way, or replace it with a different operation as far as I can see.

    You can create a service with killall -s SIGTERM retroarch in its shutdown operation - but by then it's too late. Systemctl has already killed all user processes - including retroarch.

    So what I had to do was actually run retroarch as a service itself. That was systemctl left it for its own shutdown procedure. I'm fairly new services, so I don't claim this is the perfect solution but it works for me.

    This is based on "retropie" on a Raspberry Pi. If you're running some other Linux system it may or may not be helpful.

    First, we need to prevent retroarch from starting in the normal way. I edited /opt/retropie/configs/all/autostart.sh, commenting out the existing lines and adding in a call to the shell bash:

    bash #/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ mame-libretro ~/RetroPie/roms/mame-libretro/robotron.zip #emulationstation #auto

    Next I created a new service by adding a file /etc/systemd/system/killmame.service containing

    [Unit] Description=A service start and stop MAME cleanly After=console-setup network-online.target multi-user.target [Service] User=pi ExecStart=/home/pi/bin/start.sh ExecStop=/home/pi/bin/killmame.sh Type=simple StandardInput=tty-force TTYVHangup=yes TTYPath=/dev/tty20 TTYReset=yes SendSIGKILL=no KillMode=none [Install] WantedBy=multi-user.target

    Notes:

    You'll need to create that as root (eg. sudo nano killmame.service) killmame is a bad name for the service. It started off only intending to kill it, but morphed into a complete service - retroarch.service might be a better name All the tty stuff is needed or retroarch won't run The two scripts in ExecStart and ExecStop need to be created in the next step

    Now we create a directory /home/pi/bin and create the two scripts in the (can do this as the pi user):

    start.sh:

    #!/bin/bash cd /home/pi export TERM=linux export USER=pi chvt 20 /opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ mame-libretro ~/RetroPie/roms/mame-libretro/robotron.zip & bash

    The command starting /opt/retropie is what I previously had in my autostart.sh. Obviously it's specific to my game, you will need to change it to whatever you had in your autostart.sh file.

    You MUST have the & character at the end, putting the command into background. Otherwise systemctl will kill it in the early steps of shutdown. I'm not sure why.

    killmame.sh:

    #!/bin/bash # echo checking for mame running ... > /home/pi/bin/killmame.log # ps -deafww | grep libretro | grep robotron >> /home/pi/bin/killmame.log killall -s SIGTERM retroarch echo shutting down MAME at `date` >> /home/pi/bin/killmame.log

    The commented-out lines 'echo' and 'ps' were for debugging - to see if my game was actually running when it came to being shut down.

    Finally we need to register and enable our new service:

    sudo systemctl daemon-reload sudo systemctl start killmame sudo systemctl enable killmame

    All those should complete without output. If the 'start' fails, you'll need to figure out why before continuing.

    If they all work, you can reboot. Your machine should first drop into a shell prompt, but then very soon after retroarch should take over. Hitting the kill switch should now shutdown retroarch cleanly, saving high scores.

    The only glitch I've found is that if you use <ESCAPE> to exit retroarch, you'll find lots of key presses on the shell window from your game controls. Usually they're harmless but it's just possible you might accidently issue some fatal commands. Probably removing the invocation of bash from autostart.sh woud solve that, but you might then not be able to get back into a shell after exiting with escape. I generally log in remotely using ssh, so that wouldn't worry me.

    I hope this helps someone as I spent hours trawling for a solution without finding one. It was only while explaining to my wife why it was impossible, that it occurred to me to actually run retroarch as a service itself.

    If someone is able to tidy this up into a cleaner solution I'd be very grateful.

  • What does this error mean? (lr-mess)

    9
    0 Votes
    9 Posts
    1k Views
    FollyF

    @JimmyFromTheBay said in What does this error mean? (lr-mess):

    If I can run them both at the same time that'd be great, but if not then it's not worth the hassle and risk.

    Technically it's possible but I think, for you, it's indeed not worth the hassle and the risk.

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.