• Bad Link to Forum Home Page on Main Site

    7
    0 Votes
    7 Posts
    288 Views
    TangoT

    I'll try it again when I have access to several browser and back on my other computer.

    Weird.

  • ROM Full Name, Gamelist

    7
    0 Votes
    7 Posts
    785 Views
    L

    Hi mitu. Good info. Gives me an idea after all.

    Also, being a moderator would you mind fixing the code quotes in my previous post? Sorry... when trying to edit it is saying I am spam.

  • lr-hatari failed to build linux mint

    12
    0 Votes
    12 Posts
    1k Views
    G

    It works, brilliant job thank you!

  • Double Dragon (MAME)

    Moved
    10
    0 Votes
    10 Posts
    3k Views
    B

    @iamoasis said in Double Dragon (MAME):

    some spreadsheets that show games that have been tested on different emulators

    Some entries in those spreadsheets are wrong though, because some of the testers didn't follow the "pick an emulator then pick the right romsets for that emulator" rule.

  • 0 Votes
    2 Posts
    427 Views
    S

    You're not running into issues with building the N64 emulator mupen64plus? It's only happening on Debian Stretch (x86-64) but it could be my setup so that's why I'm asking. It's requiring a newer version of cmake than what's available:

    /home/pi/RetroPie-Setup/tmp/build/mupen64plus/GLideN64/projects/cmake /home/pi/RetroPie-Setup/tmp/build/mupen64plus /home/pi/RetroPie-Setup CMake Error at CMakeLists.txt:1 (cmake_minimum_required): CMake 3.9 or higher is required. You are running version 3.7.2
  • Retroarch Updating

    5
    0 Votes
    5 Posts
    89 Views
    Keltron3030K

    @mitu ah yeah, my bad. Guess I'll have to wait for the next version for source to be 1.8.5, or I'll have to modify the setup script.

  • 0 Votes
    6 Posts
    2k Views
    R

    @SolemnSpirit Thanks that helped!, the moment i remove the key_mgmt, i was able to connect to the wireless! :D i appreciate you posting this!

  • RetroArch's Own Config File

    8
    0 Votes
    8 Posts
    3k Views
    TangoT

    @mitu Never used Reset, at least that I know of. But thanks for that tip. I'll be sure to avoid it.

  • 0 Votes
    21 Posts
    6k Views
    TangoT

    @mitu said in Are Multiple Mice Supported or Was That Feature Trashed?:

    You can check by looking at the RetroArch's debug log and by running cat /proc/bus/input/devices.
    Remembering your first RetroArch debug log, my guess is that RetroArch counts twice a mouse device as both /dev/input/mouseX and /dev/input/eventY. You can check this theory by adding a mouse (so you have 3 devices) and using indexes 0, 2 and 4 to see if each device is detected and working.

    Okay. I can see that now, with access to the computer again. (Remember, it's in a different place than my desktop, that I use for posting.) Thanks!

    Now I have the primary Mini PAC set in Keyboard Mode and I see that it recognizes the Mini PACs as devices, but also recognizes the devices on them separately. It looks like keyboard in the Mini PAC gets an event node. Interestingly, the Ultimarc SpinTrak (the spinner) gets Event 5, not 6. When I test with cat /dev/input/event6 I get input from the spinner and I don't with event5.

    But this shows me that some of the devices are broken down into multiple devices and explains why something else is "in between" the trackball and the spinner.

    As a side note, even though this is a built in function for RetroArch, I've now done what the manufacturer claims can't be done. Xtensions claims that, in D Input Mode, you can only have one mouse device, so you can have the trackball (somehow that always ends up as the one to take priority) but not the spinner in that mode. I'll be writing them about that!

    When I have all my questions worked out, I'm going to either write up a few blog pages or make a few videos for others with the same issues. I'm hoping that they will use the so their other customers can get this working, too.

  • Bluetooth and roms go to desktop then back to retropie

    2
    0 Votes
    2 Posts
    265 Views
    mituM

    Running in a desktop environment is not supported on a Pi - I guess the relevant topic is https://retropie.org.uk/forum/topic/3/read-this-first:

    Do not report issues with running on a RPI4 - it's not yet officially supported, and there are many 3rd party guides with incorrect instructions out there.

    If you have a Pi4, you can install manually over Raspbian Lite - https://retropie.org.uk/docs/Manual-Installation/ - but remember that Pi4 support is a work in progress.

  • sigil loading ultimate doom instead of sigil

    8
    0 Votes
    8 Posts
    970 Views
    BobHarrisB

    @dalekman27 Good to hear! Enjoy :)

  • 0 Votes
    3 Posts
    416 Views
    TangoT

    Thanks!

    I never played fighting games much - always liked the spaceship games - so that explains why I didn't even think of that.

  • Error while trying to install new emulator

    4
    0 Votes
    4 Posts
    290 Views
    mituM

    @felifel We don't support 3rd party images - is clearly outlined in the https://retropie.org.uk/forum/topic/3/read-this-first topic.
    Use the image from retropie.org.uk/download to install, update your RetroPie installation and try again installing the emulator.

  • 0 Votes
    5 Posts
    833 Views
    G

    Haha yes, it works :D Simple solution is:

    First of all - if you have your copy of .sav file (or any other containing your save state), backup it to have an original one in case of losing all saved data.

    Open rom in Visual Boy Advance, restore you save and create save state using built in saving mechanism.
    Now close the game and remove in-game save file - file which is a copy of your original state file.
    Next open game in Visual Boy Advance and load state saved in built it saving mechanism.
    Go to VBA Options > Emulator > Save Type and change it to SRAM
    Perform in-game saving. New .sav file will be created in folder when your game was stored.
    Rename file with extesion for "your_game_name.srm".
    Copy it to Retropie.

    After these steps I was able to open my save state from Pocket-Go on my GPICASE :)

    BTW:
    There is a possibility that @lostless sugesstion will work to but if not, you need to perfrom above steps.

    BTW2:
    Visual Boy Advance saves in-game states files as a .sav file, so you are able to copy you states from VBA to Retroflag also.

    Thank you guys!

  • Update BlueZ?

    2
    0 Votes
    2 Posts
    718 Views
    mituM

    The blueooth packages are part of the OS (Raspbian) - they can be upgraded if a new version is released by the upstream Raspbian project and can be installed with the apt utility, or just choosing to update your OS packages from RetroPie-Setup when you do an upgrade.

  • 0 Votes
    22 Posts
    2k Views
    S

    @BuZz I unintentionally got two failed installs so I'll share them as they had your exit code fix. They failed differently so at least it's something. :) The N64 emulator exited with 1 as expected, but Splashscreen exited with 0 (it didn't continue to install but I don't know how to tell when it's done done). Edit: It should end with Info: [message] on success?

    1: basic_install exited with 1 when mupen64plus failed. Ran on Debian with amd64. See full log.

    = = = = = = = = = = = = = = = = = = = = = Building 'mupen64plus' : N64 emulator MUPEN64Plus = = = = = = = = = = = = = = = = = = = = = [snip] make: Leaving directory '/home/pi/RetroPie-Setup/tmp/build/mupen64plus/mupen64plus-video-glide64mk2/projects/unix' head: cannot open '/home/pi/RetroPie-Setup/tmp/build/mupen64plus/GLideN64/src/Revision.h' for reading: No such file or directory current revision "50e83004" last build revision /home/pi/RetroPie-Setup/tmp/build/mupen64plus/GLideN64/projects/cmake /home/pi/RetroPie-Setup/tmp/build/mupen64plus /home/pi/RetroPie-Setup CMake Error at CMakeLists.txt:1 (cmake_minimum_required): CMake 3.9 or higher is required. You are running version 3.7.2 -- Configuring incomplete, errors occurred! make: *** No targets specified and no makefile found. Stop. /home/pi/RetroPie-Setup/tmp/build/mupen64plus /home/pi/RetroPie-Setup Removing additional swap /home/pi/RetroPie-Setup Could not successfully build mupen64plus - N64 emulator MUPEN64Plus (GLideN64/projects/cmake/plugin/Release/mupen64plus-video-GLideN64.so not found). Errors: Could not successfully build mupen64plus - N64 emulator MUPEN64Plus (GLideN64/projects/cmake/plugin/Release/mupen64plus-video-GLideN64.so not found). The command '/bin/sh -c if [ "$(uname -m)" = 'x86_64' ]; then sudo ./retropie_packages.sh setup basic_install; fi' returned a non-zero code: 1

    2: basic_install exited with 0 when splashscreen failed. Ran on Debian with arm32v7. See full log.

    = = = = = = = = = = = = = = = = = = = = = Configuring 'splashscreen' : Configure Splashscreen = = = = = = = = = = = = = = = = = = = = = /home/pi/RetroPie-Setup/scriptmodules/supplementary/splashscreen.sh: line 91: systemctl: command not found /home/pi/RetroPie-Setup Removing intermediate container c40e0a51fa8f ---> 3e4f12bb8360 [snip] Successfully built 63739c10746d Successfully tagged rc:docker-multiarch
  • 0 Votes
    6 Posts
    2k Views
    T

    Thread necro, but same problem, and a way to resolve...

    Get into the command prompt go to the ~/RetroPie-Setup/scriptmodules/supplementary directory Delete the old retropie-manager.sh file Download the correct script from the github repo (https://raw.githubusercontent.com/RetroPie/RetroPie-Setup/master/scriptmodules/supplementary/retropie-manager.sh) Go back to RetroPie setup again and now the script should work and install retropie-manager.

    ("code" is below if needed)

    F4 cd ~/RetroPie-Setup/scriptmodules/supplementary rm -r retropie-manager.sh wget https://raw.githubusercontent.com/RetroPie/RetroPie-Setup/master/scriptmodules/supplementary/retropie-manager.sh
  • question about which emulator to run PC (dos) games

    2
    0 Votes
    2 Posts
    237 Views
  • High Score not showing properly

    2
    0 Votes
    2 Posts
    304 Views
    mituM

    We don't support 3rd party image, as explained in https://retropie.org.uk/forum/topic/3/read-this-first.
    Install the RetroPie image from https://retropie.org.uk/download and update the emulators, then try again and see if you can reproduce the error.

  • 0 Votes
    2 Posts
    239 Views
    V

    Nope. This didn't work. The internal resistance of the capacitor is too high to deliver enough current to prevent a power interruption. You get a very low current output for a long time, not a high current output for a short time. I found only very large supercaps such as car audio "stiffening" caps have low enough resistances, and those are about the size of a soda can so it's a no go.

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.