From now on, there will be more frequent rolling updates.

We are close to automating releases on the buildbot so that we can have weekly releases for the most prominent platforms.

Version 1.3.2 is available here:

I will add OSX 32bit and PowerPC releases to this later on. PS3 will be back at some later undisclosed time, same with original Xbox and 360.

Regarding the releases from this point on: give us as much feedback as possible, and with each week we can try to address some of this feedback and make RetroArch better. A ‘Release early, release often’ approach instead of the drought of stable releases that was the norm before will hopefully result in more sustained progress.

40 thoughts on “RetroArch 1.3.2 released

  1. So is there any difference between this and the newest nightly?

    1. Matías Ferrero

      March 16, 2016 — 3:10 pm

      Was going to ask the same. Also, a detailed changelog between 1.3.0 and 1.3.2 would be nice. As always, thanks for this new release of RetroArch, it changed my life.

    2. Libretro RetroArch

      March 16, 2016 — 8:45 pm

      The changelog is basically whatever happened on Github inbetween v1.3.0 and v1.3.2.

      The intent is there for the next bi-weekly release to have a changelog, for this release it couldn’t really be done, too much time has passed and too many commits passed to really make a good rundown on it.

      1. Matías Ferrero

        March 16, 2016 — 9:30 pm

        Ok thanks anyway.

  2. Алексей Попович

    March 16, 2016 — 7:10 pm

    In the latest version it’s still not possible to bind SELECT button on PS3 controller, connected via MFI (Controllers for All). It’s always binding as a button number 3. Please remove this bug.

    1. Libretro RetroArch

      March 16, 2016 — 8:44 pm

      Unfortunately it’s a MFI protocol limitation, not even the extended MFi spec has a Select button. Apple deemed it not worth it to have a proper Select button for assignment on their gamepads. Quite stupid really.

      1. Алексей Попович

        March 17, 2016 — 2:20 am

        Thanks for reply. Please tell, can I connect PS3 controller some how instead MFI? (On iOS). Because it’s really important to have all buttons when emulating PSX games.

        1. ★ ☆☆☆☆☆ ★ HOW TO USE THE PS3 CONTROLLER INCL. ALL BUTTONS ★ ☆☆☆☆☆ ★

          To use a PS3-Controller (bluetooth) for iOS it is and was inevitable to install “Controllers for All” and “BTstack” from Cydia. (For Mac you also need the App “SixPairMac” to connect PS3 to the iDevice)

          Here is what I found out for the RetroArch-Version

          Ofcourse everyone, like me, fired up “Controllers for All”, connected the PS3-Controller and afterwards opened RetroArch (

          In the Setting-Menu, when trying to bind the inputs etc. all of us had to cope with the issue that some of the buttons did not work:




          “Left-Analog-Stick”-Press (Pushing/Pressing the stick down)

          “Right-Analog-Stick”-Press (Pushing/Pressing the stick down)

          I read hundreds of posts and visited hundreds of websites to find a solution but found NOTHING.

          Pre-Post: Finally, after fiddling with RetroArch etc. for weeks I found out how to have all (!!!) buttons work.

          The “Solution” worked on all of my devices running version iPhone 5s & 6, iPad mini 4, iPad 3, iPad Air 1 & 2.

          This is what I did… Finally the Solution for all (my) Devices running &

          STEP 1. Close all Apps and restart the iDevice. – 1.1 Connect PS3-Controller and the iDevice to Mac vial USB. – 1.2 Use “SixPairMac” to connect both to “get to know each other” – 1.3 Unplug both (PS3-Controller and iDevice) from Mac. Wait until PS3-Controller stops “blinking” the red LED. – 1.4 Optional: Check If both are (really) connected. I switched OFF iOS Bluetooth and switched ON “BTstacks”, “Controllers for All” and afterwards the game “LEGO® Star Wars™: The Complete Saga”. When my PS3-Controller seemed to work I continued to Step 2.

          STEP 2. Turn OFF both “Controllers for All” and the “internal” iOS-Bluetooth function! (YES, SWITCH THEM OF!) – 2.1 Leave “BTstack” turned ON – 2.2 “Close” iOS-Settings (also from Dock!) wait for a couple of seconds. Make sure PS3-Controller is OFF and the the red LED is not “blinking” etc. Also make sure the iOS-Bluetooth”Logo” up to the right on the iDevices is “grayed out” and not “black” and “thick”!

          STEP 3: Turn ON RetroArch. 3.1 Press the PS3-Middle-Button (with the PlayStation-Logo) and wait until both the red PS3-Controller LED lights up Player 1 and the “grayed” Bluetooth-Logo on the top right corner becomes “black and thick”

          STEP: 4. Enter the RetroArch Input-Settings. Make sure “w/ Analog” is checked in Device-Type and the Left Analog stick is select. Also the “Device Index” should be set to the “Controller with Analog Sticks”. 4.1 Start to bind all Keys.

          ENJOY RetroArch ( & with PS3-Controller) and ALL BUTTONS AND ANALOG-STICKS WORKING!

          Solving Issues: I did have issues but (how stated above) got it working on ALL(!!!) my iDevices. If it won’t work for you ( & DON’T STOP. It WILL work! The good thing with me was to know that it DID work at least once on my iDevice so I never gave up. I KNEW it could work so I just tried to find “the issue”.

          At the end I found out that the following workflow always “helped” to fire back up everything again if issues start (mostly when the iPad lost battery):

          Close all Apps (also from the dock)

          Restart the iDevice.

          Turned iOS-Airplane-Mode ON and OFF

          Followed STEP 2 to STEP 5

          As for now with iOS-RetroArch-Version 1.2.2 (Early Nov. 2015) the above Workaround sadly does NOT work anymore… (Somebody wrote this is because Apples “Controllers-MFI” is not supported anymore…?)

          I hope this somehow helps the Dev-Team in understanding how to get things working concerning the PS3-Controller. Since i’m not a developer I don’t know what to make up with that information. 😉

          1. Lol ;d

            Controllers For All is basically set up for apps and stuff, not really Emulators like RetroArch, pressing PS button to bring up the RetroArch GUI instead asks if you want Controllers for All to turn off the remote (a very stupid feature).

            Simply, just use BTstack alone, without Controllers For All. ;d I don’t even have Controllers for All installed.

          2. Oh, ok! Thanks for the update!
            I always thought that “ConrollersForAll” ist needed to get everything set up (also if “not used” afterwards)
            Well again: Thanks for the Info!
            Definitely learned something. 😉

          3. Hey no problem. You can have ControllersForAll installed if you want, just disable auto pairing and set it as manual if you use RetroArch more often. ;3

            ControllersForAll is mainly for AppGames, not emulators like RetroArch ;d

  3. Matías Ferrero

    March 16, 2016 — 10:05 pm

    Ok, I have to report an issue. Using x64 for Windows, when listing cores there are no descriptions (new users will have trouble) and after installing a core, they dont seem to be working as they show in “Load Core” but when trying to play a rom it doesnt detect any core at all.

    1. wow, wonder how long we’ve had this issue.
      gonna push a hotfix tonight

      1. Matías Ferrero

        March 17, 2016 — 4:19 am

        I also tested RetroArch x64 2016-03-16 nightly and has the same issue. So I went back to 1.3.0. Thanks anyway!

      2. Matías Ferrero

        March 19, 2016 — 5:07 am

        Any news on this?

        1. the nightlies are fixed but we haven’t released another “stable”

          1. Matías Ferrero

            March 25, 2016 — 5:57 pm

            Yeah I noticed that few days ago. I recomend to release another stable as soon as possible, so new users dont get a bad “stable” release.

  4. Hi, great work! Really love it. Playing Zelda – A Link to the Past right now.
    Where do I have to report issues? Found some:

    – No visual feedback for some actions like “save current config”
    – it’s hard to tell which settings are saved for the whole retroarch program and which for specific cores
    – when changing from ingame to menu via hotkex-combi, dynamic wallpapers are ignored
    – configuration is not always loaded at start, sometimes I have to load manually
    – some of the settings are really confusing and I would love to have more explanations or a normal and expert view

    Keep on the great work! It’s the best project I’ve come across in the last time 🙂

    1. Uh, save current config actually prints a message.
      RetroArch always saves systemwide unless you have core specific configurations enabled.

      I have never seen an instance of configuration not being loaded at start, unless you’re using an external launcher or something, you’d need to narrow down the cause.

      1. Hi, tried it again. The first report was from windows, this time I tried on linux – same here. (on linux 1.3.0) “Save new Config” prints a yellow message on screen, “Save current config” shows no message. Additionally, on linux, Paths with umlauts (ä,ü,ö,…) are not stored correctly. And another one: mupen64plus search (playlist) only recognzes one of 3 n64 rom formats.
        PS: is there a better place to report bugs?

  5. When playing Super Bomberman 2 on PocketSNES (N3DS), pressing a button makes the input for that button stop working until you press another button.

  6. When playing Super Bomberman 2 on PocketSNES (N3DS), pressing a button makes the input for that button stop working until you press another button.

  7. Will NDS emulation for Android ever gain touchscreen usage? 95% of games are virtually unplayable without it.

  8. Dumb question probably…as I got an ouya at a yard sale and am playing around with it and saw this in their this the same version as what is available there in their store? If not is there a way of porting this version via a side load or is this compatible at all, or even needed? Thanks for not attacking the noob and answering my questions 😉

  9. Running 64-bit Vista and I’m still getting this error message that I’ve been getting from the last few nightlies and 1.3.0 stable now: “The procedure entry point GetNumaNodeProcessorMaskEx could not be located at the dynamic link library KERNEL32.dll.” The only release that works for me is a nightly that was shortly after 1.3.0’s release in about January.

  10. Anti_Ameritopian

    March 18, 2016 — 4:51 am

    Any time I try to load a SMS game and use the Emux core it instantly crashes on both Android and my windows 7 PC.

  11. Any chance of seeing Dreamcast cores like NullDC on RetroArch?

    1. we have reicast

  12. When I move the retroarch folder to a folder named “#! Prince” it switches to a flat dark theme but if I name the folder “Prince” it works fine.

  13. please help me …the mouse cursor shows up when i enable screen overlays…its very annoying ..i lost a great feature that i need !

    1. overlays were meant to be for input not for screen decoration.

  14. Hey, is there any chance to BB10 version you promised long time ago? 🙁

  15. Can an administrator activate my account please? I registered last wednesday, but I haven’t received the activation email. I have checked the spam folder and everything. My username is darleyni.

  16. Someone let me know when the mGBA core will have cheat support, because I am so freaking sick of VBA-Next.

    1. no etas for anything

  17. on marshmallow mouse ,keyboard and xbox 360 controller wired are not working in menu but a bluetooth controller works. any fixes planed? it is a pain on android boxes.

    1. I’ve had this same problem too.

      1. move to the current nightlies, it’s been fixed for a few months

  18. I have a issue trying to load A specific PSX Game, I’ve tried multiple versions of the ISO and have edited the Cue files to match the bin and it still won’t show up in the library, nor does it ever run properly. People say they’ve been able to run Symphony of the Night but I don’t understand how. Sorry if I sound like a noob, I just started using RetroArch.

  19. I need help with getting a DS3 controller to work in retroarch. I can get it to work fine in the menu screen but as soon as I load a game it says it’s not configured. I should also add I’m loading roms from kodi using rom collection browser from a Matricom gbox q Android TV box. Anyone have any ideas? I’m about to pull my hair out.

Comments are closed.