Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • dparks
    Participant

    cd RetroPie-Setup
    sudo ./retropie_setup.sh

    That loads a pretty blue and white menu for your viewing pleasure.

    in reply to: HELP!!! #87098
    dparks
    Participant

    Cool project! I started something like it a few years ago, but didn’t have a raspberry pi at the time.

    For the sake of portability (and because I haven’t mucked around with the GPIO pins on the pi yet), I would wire it up to another controller with a USB on it. Something like this, though I can’t confirm its compatibility with the pi: http://www.diyarcade.com/usb-arcade-control-encoder

    That way, if you get frustrated or bored with using the raspberry pi, you can just plug the USB into another machine without having to completely rewire. From there it would just be a matter of plugging it in and configuring your emulators to recognise the buttons.

    I ended up wiring my arcade buttons up to the PCB of an old wired Xbox 360 controller as an obsession with street fighter 4 took hold. This is a pain in the arse, and I would not wish it upon anyone.

    in reply to: v2.5 some problems #87097
    dparks
    Participant

    I had the same issue with the N64 emulator, which was fixed by reinstalling mupen64plus from source (after updating the setup script first) from retropie_setup.sh. That fixed the black screen thing for me, but i’m still left without fullscreen for now.

    As for the black border thing, does it exhibit the problem all the time? Or just particular emulators? Have you tried mucking around with any of the output settings in es_systems.cfg?

    Can’t help you with the controller thing for now.

    I’ve got mine with a 256 GPU split, which seems to be working alright for now. There was no rationale behind this number, it just sounded cool.

    in reply to: Raspberry-pi 2 compatibility #87076
    dparks
    Participant

    Under the Nintendo 64 Entry (there will probably be two of them), there’s this line:

    <command>/opt/retropie/supplementary/runcommand/runcommand.sh 1 “/opt/retropie/emulators/mupen64plus/bin/mupen64plus –configdir /opt/retropie/configs/n64 –datadir /opt/retropie/configs/n64 %ROM%” “mupen64plus”</command>

    The “1” after “runcommand.sh” sets the output mode, in this case I believe it’s VGA.

    in reply to: Raspberry-pi 2 compatibility #87071
    dparks
    Participant

    I’ve managed to get my RP2 up and running without too many glitches thus far on your most recent image. MAME4ALL plays NBA jam very fluidly, and the PSX RetroArch emulator works like a dream.

    Mupen64plus plays Mario 64 and Mario Kart pretty smoothly with n64 plugin and almost no other changes (Rice without tinkering was a little stuttery, but I believe this has been discussed). I still cannot for the life of me get it to run completely fullscreen (that is for output to match the height of my 1080P TV). It will output enlarged with setting in es_systems.cfg set to 1, or else it appears in the bottom left corner. Changes to gles2n64.conf seem to have no effect.

    I’m sure with a bit more coffee and a lot more swearing the solution will be obvious!

    Anyhoo, excellent work thus far, guys and gals!

    in reply to: Configs ignored for pisnes/pifba #81913
    dparks
    Participant

    Here’s a little update:

    Exiting emulation station and opening any file with nano (not necessarily either control cfgs and not necessarily writing to it) and then restarting ES causes the error to go away…until reboot.

    I should also mention that I’ve set emulationstation to autostart on boot, if that makes any difference.

    My brain hurts.

Viewing 6 posts - 1 through 6 (of 6 total)