RetroArch 1.2 – July 4 release kickoff

Posted by on Jul 4, 2015 in Android, Blog, Libretro, RetroArch | 8 Comments

Download here!

First things first – we are back. It has taken us a very long time to make a new release of RetroArch due to numerous complications, so apologies for missing numerous release dates before (first Christmas, then somewhere in April, etc.). It tells something about the development hell we’ve been through that I’ve just skipped an entire version number (1.1) and gone straight to 1.2.

Let me first get some important stuff out of the way before we continue. For our iOS and Blackberry 10 users: we were not ready today (July 4) to launch on these platforms, you’ll unfortunately have to hold out for one more week before we have something for you. Rest assured that there will be plenty to enjoy a week from now.

With that out of the way…

What is RetroArch being released on today and tomorrow?

  • Android (DONE) (Uploading to Play Store right now)
  • Windows (DONE)
  • Linux (DONE) (Repo packagers, go ahead and update the respective packages)
  • Mac (Maybe July 5 2015)
  • Consoles (Wii / PS3 / PSP ) (July 5 2015)
  • Consoles (Xbox 1 OG)        (Maybe July 5 2015)
  • iOS (Next week)
  • Blackberry 10 (Next week)

Other platforms will have to wait, but rest assured the wait is not much longer.  *
I could write an entire book about all of the new features in RetroArch, but instead I’m just going to summarize it up in a few bullet points so that you can get the gist of it. In the upcoming weeks you will see plenty of more big announcements coming from us, and we will also provide you with much-needed user documentation on everything you can do with RetroArch now.

– Brand new eye candy menus to choose from! –

RetroArch now lets you select between three menu display modes: RGUI (a very classic, low-resolution menu), GLUI (a more advanced GL-based menu that lends itself well to touch-based devices), and XMB (a horizontal crossbar menu that is the most eyecandy-rich of all three right now).

Thanks to improved touch support, you should now be easily able to control RetroArch’s menu by dragging up or down and clicking on items. And thanks to built-in DPI awareness support, menu elements should now be scaled according to the DPI (Dots Per Inch) reported by your system.*

* NOTE: The XMB menu driver’s touch support right now is kinda iffy. We recommend that you use GLUI on touchscreen-based devices, like mobile (Android/iOS/etc).

– Scan files/directories and add them to game system collections! –

You can now scan files and/or directories, and RetroArch will look for a match inside its database. If it finds a match with a known game on a given system, it will then add this game to a collection based on the system of that game. This way, you can have ordered collections of games without having to browse your filesystem all the time looking for a ROM/game to play.

To use this feature, go to ‘Add Content’ and select either ‘Scan Directory’ or ‘Scan File’. *

* NOTE: Some programs right now might not yet have a database system in place to allow you to scan said content. Some of the current ones that still need to be addressed are MAME and CD-based systems such as the PlayStation. You will see this rectified in an upcoming RetroArch update.

– View database information about each game once added to a collection! –

Once you have a few collections, you will be able to view detailed information about the game, provided by RetroArch’s new database features. You will be able to view the developer of the game, the year it was released at, any kind of special hardware it used on the ROM cart package, the publisher that released the game, etc. *

* NOTE: The amount of information provided per game can vary and is dependent on the database’s completion. We encourage contributors to help us out building up these databases.

– Download programs (‘cores’) online –
RetroArch no longer comes with programs preinstalled, instead you download these now from our buildbot from within the program. Go to Online Updater -> Core Updater and select any of the cores you’d like to have installed. It will then download that core from our buildbot. This way, you are in control of exactly which programs you have installed and RetroArch does not take up any additional space for things you don’t need.*

We add new cores onto our buildbot routinely, so as soon as they will be uploaded you will be able to download them and use them with your current copy of RetroArch without even having to update the main program. Stay posted for more exciting new stuff coming up ahead.

* NOTE: We make no guarantees about server availability or uptime.

– Update everything! –

It isn’t just program cores that you can install this way from our buildbot. You can also update all of the asset files that RetroArch depends on. You will always be able to download the latest shaders, onscreen gamepad overlays, cheat files and whatnot directly from our servers from within the app.

All of this content is updated on a daily basis, so you can be sure there will be plenty of new things to check out on a weekly basis.

– Download Game & Watch games and play them with our exclusive Game & Watch emulator ! –


People in their early to mid-30s might have seen these things in the wild back n their day and will probably be familiar with these old standalone handheld games that predated the Game Boy, but don’t let their age fool you: these games still are very useful time killers and their age if anything gives them even more charm appeal.

Go to ‘Add Content -> Download Content’ to download any of these Game & Watch games. From there, you can play them with our Game & Watch emulator which has been built from scratch by a valued libretro contributor. Some of the standout features include faithful reproduction of the handheld’s screen layout, high-resolution bezels, nice simulation of the sound effects, etc. Give these a try.*

* NOTE: We owe a certain amount of thanks to Madrigal’s simulators for being able to offer these games to you.

– Built-in input mapping –
It is now possible to bind your gamepad from within the program without having to go through the chores of previous versions. Go to Settings -> Input Settings and select ‘Bind All’ to bind each and every button one at a time, or bind the actions individually. If you are using a gamepad which is supported by us, it will be autodetected and autoconfigured to align with our gamepad abstraction, the RetroPad.

– Ability to remap controls –
An often-heard complaint before was the inability to change the controls. We have made this possible now. Once a game is loaded, go to the ‘Quick Menu’ and select ‘Core Input Remapping Options’. From there you can change the controls per core, and you can also save these changes to a config file.

– Ability to enter and load cheats –
It is now possible to input cheats and apply them to the currently running game. This was also an often-heard complaint and omission pointed out by users, so we have provided this as well this time around. *

* NOTE: Some programs might not yet have cheat support integrated. As soon as we include cheat support for these cores, you will be able to download the updated core from within the app (see ‘Download program cores online’).

– Multi-language support! –

This release comes with (preliminary) multi-language support. Go to Settings -> User Settings and choose a language. Right now we provide translations for Dutch, German, Portuguese, and French.*

* NOTE: Some of the language translations might be more incomplete than others. Others (like Japanese/Chinese/Russian) are not available right now, and we seek translators for those as well.

– Over 80+ programs now and counting –
RetroArch and the libretro ecosystem has expanded in scope dramatically since the last release over a year ago. There are now over 80+ programs to choose from among its collection, and you can be sure that number is bound to increase from here on out. *

* NOTE: The amount of program cores available might vary based on the system you are using.

– Built-in image viewer (and media player) ! –

We have thrown in an image viewer inside RetroArch now. It is possible to display JPEG, PNG, TGA and BMP images.*

As if that is not enough, for the Windows release we now have an integrated media player. It is possible to play music and movie files now from within RetroArch. This might seem like an unorthodox way to use RetroArch, but it has certain tricks up its sleeve that other media players do not, such as frame interpolation and a wide array of shaders and audio filters to choose from. ** ***

* NOTE: Expect this feature to be improved in the coming weeks, there are still some power management issues to sort out with high-resolution images.

** NOTE: Expect this feature to be heavily improved later on. We will want to start supporting remote controls and also to provide a fancy overlay for video playback purposes. Also, expect a very nice audio visualizer soon for the playback of music files.

*** NOTE: The integrated media player support is available for any version of RetroArch that comes with built-in ffmpeg support. RetroArch is dependent on ffmpeg for making it possible to playback these files.

– Tons more besides to discover and enjoy –

This quick writeup does not even scratch the surface of everything that has been added to RetroArch over the span of a year. We worked hard on making this release happen and as such did not have the time to write about every single new feature in detail before dropping this release. Over the next few weeks we will have a more increased Youtube channel presence where we will drop videos which will show you all you can do with RetroArch right now. Please look forward to these videos.

Also, don’t hesitate to contact us with your ideas on what could make RetroArch better and how to improve it. We definitely want you to provide us with a lot of feedback on this release so that we can improve the next release in response to user feedback.

From now on, you can expect continuous updates. It took us a long time to set the entire infrastructure up to make all this possible and we also had to rewrite RetroArch entirely at least 5 to 6 times over the past year, but rest assured that this huge media dropout was a one-off event.

If things are not perfect today (and nothing will ever be perfect), be rest assured that from here on out, updates will be quick to arrive. We are not going to have a repeat of this endless delay schedule that has plagued us since last year, and above all we now want continuous user feedback so that we can improve things as we go along. Most importantly, me and others have practically worked themselves to death on this release for over a year and we really want to push this release out now so that people have something in their hands and we can go from there.

Oh yeah, there will be another big blog post after this that will detail some other new projects we’re working on shortly, but for now I have to focus on actually pushing this release out. So let’s see if we can get that done today and we’ll drop all the other major announcements shortly after.

Some other notes (Xbox 360 missing, etc)

* The only exception to this release promise is the Xbox 360 port. I have been routinely screwed and scammed by the ‘underground’ console hacking scene and right now I’m sitting on this paperweight RGH Xbox 360 that is useless for development, so that port is on indefinite hold until somebody can get me either the XDK back that I gave somebody in good confidence that it would go to Ced2901 (but it never did apparently), and I presume the guy I gave it to just hoarded it. or we can get a replacement for it. I won’t mention names but the guy who took my XDK and never gave it to the person he said he was going to give it to knows who he is. Anyway, if you guys still consider this Xbox 360 version important, let me know but I’m not going to go and take money out of my own coffers again to make that happen. I’m done with the console scene shenanigans.

Some other notes (3DS / PSP version)

We could maybe push out a PSP version of RetroArch 1.2 in the upcoming weeks. I’m hoping to get back with the main contributor (aliaspider) who worked on these ports so that we can be assured that we can at least push out the PSP version in a more or less stable and decent state.

Regarding RetroArch 3DS: it’s still very much a work-in-progress and I don’t think either me or aliaspider would feel comfortable to ship anything right now in terms of official release at this stage, and we need a lot of work done on the cores before we can render some of them playable on the slow 3DS (it’s even slower than the PSP it seems).

“In the run-up to RetroArch 1.1 – what’s new pt. 5

We’ve been away for half a year so there is a lot to talk about in this new upcoming release. Rest assured I’m working hard as hell to meet the Christmas sweet spot.  It will take a couple of blog posts to go through it all. So let’s start with the first one. I’m putting these articles out now because I really don’t fancy having to write all this stuff later on in the holidays when I drop this stuff.

In this blog post, let’s talk some more about new cores

Dungeon Crawler Stone Soup


Meancoot made this libretro port a year ago or so but it was never really in a shippable state until now. I’ve rebased the port and I’ve made sure changes from upstream can be easily pulled in.

So what is it? It’s an old-school dungeon crawler in the vein of Rogue and Nethack. The game is meant to be played in single-player mode and is originally played with the keyboard (you can even use vim bindings). Quite popular, and the libretro port supports the tile-based graphics that make the game somewhat more graphically appealing.

What’s been done right now?

– Should work on iOS, Android (not tested yet) and PC.

– Has rudimentary RetroPad joypad controls (not recommended though), and working touch controls. Also has RetroKeyboard and RetroMouse support.

– Save states in the libretro sense are not ‘implemented’ but it supports the game’s basic ‘saving’ routines so it should work the same as the standalone version in that respect.

What’s to be done in the future?

– Meancoot originally added a Libretro GL-based render path which could result in some even better performance on platforms where GL is supported. Right now the current version is using software rendering which is still fast enough for our needs.

– Problem with the upstream Dungeon Crawler codebase is that they have been ‘upgrading’ to C++11 and as a result it will no longer compile on older compilers/systems where C++11 support can not be taken for granted. I’m undecided as to whether I should add hacks to the current shallow fork so that it can also compile as C++98 or whether I should just keep maintaining the year-old previous port by meancoot which should still be C++98-compliant. We will see. I’d definitely like to see this core running on older systems since it’s such a graphically low-key game anyway.

TGB Dual


This is a Game Boy/Game Boy Color emulator made by a Japanese developer. It dates back to 2001. It has been around as a libretro core for some time but only recently have some very important things been added to it.

For instance, it now has split-screen multiplayer support. This means that you can play GB Link games on the same screen with Player 1 and Player 2 controlling either of the two virtual Game Boys.

Some games that used GB Link support to good effect include but are not limited to : Tetris, Dr. Mario, Super Mario Bros. Deluxe and (of course) the Pokemon games. So for people that’d like to play two-player Game Boy games on the same device, this will be quite a nice addition.

What’s to be done in the future?

– Make it endian-safe so it can run on big-endian targets like game consoles (PlayStation3/Wii/etc) and PowerPC Macs.

In the run-up to RetroArch 1.1 – what’s ‘new’ pt. 4 (PowerPC Mac)

Posted by on Dec 12, 2014 in Blog, Mac, PowerPC, RetroArch, RetroBox | 12 Comments

We’ve been away for half a year so there is a lot to talk about in this new upcoming release. Rest assured I’m working hard as hell to meet the Christmas sweet spot.  It will take a couple of blog posts to go through it all. So let’s start with the first one. I’m putting these articles out now because I really don’t fancy having to write all this stuff later on in the holidays when I drop this stuff.

In this blog post, let’s talk about something else than cores that’s going to be new in v1.1

RetroArch on PowerPC Mac


Some generous gifter called nogagplz has been sending me some PowerPC Mac-based laptops over the past year and that stuff hasn’t been gathering dust to say the very least.

So RetroArch now runs on Mac OS X PowerPC. The cores that are known to be endian-safe (basically all the cores out now for the big-endian PowerPC based game consoles like the Wii, PlayStation3, etc) will be making an appearance on RetroArch PPC OSX.

Not sure how big the Mac PowerPC community still is but my main motivations for getting RetroArch out on this (by now obsolete) platform is that it is a lot easier to debug code on something resembling a PC than it is to be mucking about with gimped consoles that don’t even support gdb out of the box. So it makes PowerPC development a lot easier and what’s more, I personally want to see libretro (and by extension RetroArch) running on everything. So going even further back in time in the past and making sure RA runs on that is all part of the plan.

What’s been done?

– RetroArch OSX PPC runs on OSX starting from 10.5. It might be possible to lessen the requirements even more. Only time will tell.

What’s to be done in the future?

– Get better performance out of it (could be better at least on my iBook G4). The OpenGL renderpath must be suboptimal given how ancient and suboptimal GL implementations must have been back in those days. Hopefully there’s something lower-level to tap into.

OS9 port after v1.1??!

If I’m REALLY crazy (no promises) I might attempt a port of RetroArch on even OS9. The only main motivation for this would be that the guy who supplied me the Powerbook G3 stocked that HDD with a truckload of old classic games, some of which are quite some nice ports that are actually better than their PC equivalents (Wolfenstein 3D, Doom, Hexen, Quake II is a solid port, Killing Time, Carmageddon, etc, etc) so it’s quite a nice game box right now. Having RetroArch on here would sweeten the deal even more and it would add yet another platform to RetroArch’s belt.

In the run-up to RetroArch 1.1 – what’s ‘new’ pt. 3

Posted by on Dec 12, 2014 in Android, Blackberry, Blog, iOS, Libretro, RetroArch | One Comment

We’ve been away for half a year so there is a lot to talk about in this new upcoming release. Rest assured I’m working hard as hell to meet the Christmas sweet spot.  It will take a couple of blog posts to go through it all. So let’s start with the first one. I’m putting these articles out now because I really don’t fancy having to write all this stuff later on in the holidays when I drop this stuff.

In this blog post, let’s talk about some more about new cores and some fixes to existing cores


This is a Sony PlayStation emulator. A core for this has already existed for quite some time. You’ll notice though that with the release of Android 5.0, the current version on the Google Play Store is broken. The new version that we’re pushing out fixes this.

Beetle/Mednafen PSX

Apart from some updates, we also added an optional widescreen hack courtesy of PCSXR. In the long run I want to look at introducing more enhancement features like this.


Even though we already have a lot of Super Nintendo emulator cores (well, let’s make that ‘the most amount of SNES cores out of any project’), a lot of them still had too high performance requirements for some really low-power devices out there. CatSFC is a libretro fork of SNES9x based on SNES9x 1.43. It should be a lot faster than SNES9x Next (our current fastest SNES core if you exclude PocketSNES).

The nice thing about our fork of CatSFC is that we added some stuff to it in the progress. For instance, SNES9x’s sound pre-blargg APU has always been quite bad. So what we did with CatSFC was put it in optionally. Even with the blargg APU it’s still a lot faster than SNES9x Next.

Obviously this core might only be interesting for people that have devices where power is not at a premium, like the Raspberry Pi, Xperia Play and similar low-power systems like that. The more choice the merrier.

What will be done in the future?

– Should already be endian-safe but you never know. Will give this some test runs on some PowerPC-based Macs I currently have where even SNES9x Next can be too slow right now.

– The reason we (or well, aliaspider) originally started this CatSFC core is because we wanted a SNES emulator with a bit more performance than SNES9x Next running on the PSP.  Right now it still doesn’t run at fullspeed on PSP, so we haven’t yet succeeded at this. However, Raspberry Pi users and other devices like that should already be reaping the fruits of the labor being done right now.

In the run-up to RetroArch 1.1 – what’s ‘new’ pt. 2

Posted by on Dec 12, 2014 in Android, Blackberry, Blog, RetroArch | 2 Comments

We’ve been away for half a year so there is a lot to talk about in this new upcoming release. Rest assured I’m working hard as hell to meet the Christmas sweet spot.  It will take a couple of blog posts to go through it all. So let’s start with the first one. I’m putting these articles out now because I really don’t fancy having to write all this stuff later on in the holidays when I drop this stuff.

In this blog post, let’s talk about some other new cores you can expect.

4DO – 3DO core

We ported over an emulator that emulates the 3DO. The emulator in question is 4DO, itself a fork of 3DOh.

In case you don’t know, 3DO was a short-lived game console released in the early ’90s. It was one of the first ‘next-generation’ 32bit game consoles that were released, and it predated the Sega Saturn and Sony PlayStation by about a year. Studio 3DO had some lofty ambitions at the time where the 3DO would grow up to become a video game standard like VHS where every licensee would just make a 3DO-compatible player. Unfortunately, the hardware was a bit too weak and after PlayStation/Saturn launched, 3DO died a slow death.

The few standout games for this platform can probably be counted on one hand but there was some notable stuff. A great port of Super Street Fighter II Turbo with nice redbook CD audio, Electronic Arts at the time made some good games like Need For Speed and Road Rash (both probably still better than what these franchises have become in the current-day), and Gex by Crystal Dynamics first made its appearance here. It also has the dubious distinction of playing host to the first Naughty Dog game, a game called Way Of The Warrior. It’s a standard one-on-one beat ‘em up, a bit of a Mortal Kombat/Street Fighter II derivative of the day. Guess we all have to start somewhere.

Anyway, regarding the core implementation – things are up and running, you will need a pretty powerful device for this so the faster your CPU is, the more chance you have of actually running this at fullspeed. There is a core option that lets you play games at 640×480 instead of the original framebuffer resolution. Do keep in mind that this will raise performance requirements even more. Save states are implemented but they can cause issues with certain games right now. It’s something we still have to fix.

What’s done?

– Core works, save states work but still have bugs, etc.

What’s to be done in the future?

– Backport more stuff over from 3Doh-related forks.

– Make it big-endian compatible so that it can run on big-endian consoles and old PowerPC Macs.

– Look into the multithreading speedhacks done in an Xbox 360 port of 3Doh assuming this doesn’t come too much at the cost of accuracy and can remain a toggleable option.

In the run-up to RetroArch 1.1 – what’s ‘new’ pt. 1

Posted by on Dec 12, 2014 in Android, Blackberry, Blog, iOS, RetroArch | 5 Comments

We’ve been away for half a year so there is a lot to talk about in this new upcoming release. Rest assured I’m working hard as hell to meet the Christmas sweet spot.  It will take a couple of blog posts to go through it all. So let’s start with the first one. I’m putting these articles out now because I really don’t fancy having to write all this stuff later on in the holidays when I drop this stuff.

In this blog post, let’s talk about one of the big new cores you can expect – gpSP.


There has been some complaints in the past that the Game Boy Advance libretro cores are a bit too slow on some older systems. So people with lower-performance devices should probably be glad by the arrival of this core.

This is a Game Boy Advance emulator written by Exophase originally for the PSP.  It was a fast and reasonably compatible GBA emulator that later on made an appearance on platforms like iOS and Android by unofficial porters.

Exophase stopped working on this emulator around 2009 and ever since then the codebase has been gradually decaying. The interpreter CPU core was broken on 64-bit CPUs, the x86 dynarec was 32-bit only, and there is just no central repository that aimed at making this a reasonable first-class citizen that could compete against things like VBA-M and bgba.

So the libretro core is an attempt to do all that. It uses as a base notaz’ gpsp repo but strips out the Pandora/Raspberry Pi/GP2x-specific code and aims for a more general-purpose codebase. We managed to get the ARM dynarec working on Android with some code edits, and we also fixed a few bugs that was preventing the interpreter core from working on Intel 64bit architecture.

Performance-wise, the main substantial difference is when the dynarec is enabled obviously. This core should be substantially faster right now on ARM 32bit systems (Android/iOS/Blackberry, etc) than VBA-M and the VBA-Next cores ever did. It should be fast enough on Raspberry Pi and low-end Android devices like the Xperia Play. The 32-bit x86 dynarec should also be very beneficial for users that don’t mind putting up with 32bit code. Getting a 64-bit dynarec up and running is something that is on the installment plan (for me anyway).

Savestates should work but don’t expect to be able to use savestates from other gpSP-based emulators like Gameboid or whatever.  We had to change the savestate format/size during our 64bit compatibility patches, so this is unavoidable. Though really you shouldn’t expect savestates made with non-libretro based cores to be compatible with libretro cores necessarily anyway, so let’s not pretend like this is an issue.

As for how the performance is like with the interpreter? It varies from game to game. Games like Tekken Advance and Super Mario Advance are actually slower with the interpreter core than the same games on VBA Next, but then you have the odd exceptions like Metroid, Zelda, Wario Land, Donkey Kong Country games and Astro Boy where the performance with interpreter gpSP is at least twice as fast as VBA Next. Hopefully in the long run we can fix these remaining bottlenecks with interpreter core so that there is a nice counterweight to VBA-based emulators that is at least substantially faster even with just the interpreter core.

So what’s done?

– Runs on Android with the dynarec.

– Runs on 32-bit Intel with the dynarec.

– 64bit compatibility patches so that interpreter core runs on 64bit CPUs.

– Savestates work, SRAM works, most general features you’d expect from libretro, etc.

What still needs to be done in the future?

– Get the ARM dynarec working on iOS which requires some more patches. For now, the iOS port is using the interpreter so performance is not yet as great as it should be.

– Find some way to drop support in for Normatt’s open-source BIOS replacement so that users don’t necessarily have to use the ‘official’ GBA BIOS.

– Make the performance with the interpreter core a lot more even across games. Some games getting easily twice the performance as VBA Next while some games are actually 100fps lower than VBA Next seems to indicate that there is room for improvement here.

– Do the same as what I did with VBA Next/VBA-M cores and just ‘bake in’ the needed ‘assets’ that this emulator needs. Right now it needs a file called ‘game_config.txt’ present in the system directory which enables some idle loop optimization speedhacks among other things. This should all just be baked into the core later on.

– Make it big-endian compatible so it can run on consoles and PowerPC-based Macs.

– (If I have time to waste) write a PPC dynarec so we can really have a fast GBA core on PowerPC-based targets.

Hyperkins’ Retron5 – continuing licensing problems

Posted by on Sep 24, 2014 in Blog, GPL, Hyperkin, Non-commercial, RetroArch | 7 Comments

Yesterday, Hyperkin responded to our earlier article by acknowledging that they indeed did do what we claimed them of having done. In response, they posted a raw source code dump of the video game emulator software in question, confirming they were indeed infringing copyright and violating licenses.

However, they did not open source the code taken from the RetroArch project that is used within Hyperkin’s own frontend software.

By using RetroArch’s GPLv3 code, they are not only violating the license but breaking clauses that prohibit “Tivoization”

Today, Hyperkin posted another statement regarding the allegations of RetroArch code, admitting that code is indeed used in their product shipped in all versions of their firmware below the most recent release.

I’d like to clarify one point regarding the allegations over at we are not using any of RetroArch in our “frontend” ( While it is true that a few ASM functions from RetroArch were previously found in our frontend library, these were merely remnants of old test code which we unfortunately forgot to remove. The offending code has been removed as of the v2.0 update. We’re sorry that this code was left in the binary up until recently; it was merely an oversight on our part. Furthermore as you will see from the source release of the emulator cores, we have our own interface between the frontend and the core plugins, totally different from that used by RetroArch itself.

As our frontend does not include any code from the RetroArch frontend then it does not fall under GPLv3 as they claim, and thus is not bound by any of the anti “TIVO-ization” stuff.

We believe that previously distributed copies of Hyperkin’s firmware now fall under GPLv3 licensing and anti-tivoization terms and must be open sourced in order to adhere to the license. Also, we do not know the legality of selling a product with a firmware containing GPLv3 code in a TIVOized state, and then removing that GPLv3 code later on in a successive firmware update to effectively TIVO-ize it. That is something for FSF lawyers to ponder.

Visual evidence of RetroArch’s code in use by Hyperkin’s frontend binaries can be found here: (see middle section titled “RetroArch”)

This can be compared against this codebase snapshot (they based the code’s inclusion on this snapshot of the code) –

They’ve also alluded to using forced firmware updates to make sure the user cannot run original copies of the GPL software they bundle on this device, further adding to the TIVoization claims –

Q: Assuming someone does break into it, how are you going to deal with that?
A: We do provide firmware updates through SD card support. If we start noticing people hacking and things like that—which I’m not against whatsoever; that’s the times we live in now, where if you could hack something, you’re a genius—we can release firmwares at any moment that would be required to start playing games. With that, you know, we can limit the control on that. – See more at:…5#.VCKBh-IvBhE

There is another problem with what was stated here –

They claim they no longer have any RetroArch code in their latest firmware and that  they have their own API that they use to dynamically link the core against their frontend (unreleased and closed-source). The problem with this is that their API appears to be not GPL-compatible.

For evidence, download the ZIP contained in here  ( and look at engine/retronCommon.h.

This API would need to be under a GPL-compatible license to be compatible with FCEU and VBA. Furthermore, it’s unknown what license the ‘frontend’ is licensed under, and since it’s closed-source and kept concealed, there’s no way of knowing if it infringes on the GPL license or not.

A core being exposed to the frontend through an API like this constitutes a combined work, because it is not a ‘well-separated work’ as per the terms stated here –

The core doesn’t do anything without the frontend, and the frontend links to this core dynamically through dynamic linking. The core is reliant on the frontend to do the audio/video/input processing, without which nothing would be displayed on the screen, no input would be received by the core, and no audio samples would get output.

Therefore, we believe that their latest acknowledgements raises even more questions as to the level of compliance they’ve demonstrated so far with the GPL license. It raises therefore even more questions than it solves, further adding to the already quite considerable list of problems with this device.

Non-commercial cores – SNES9x Next

And of course, the fact that the two non-commercial cores are still being shipped with the device is another problem altogether. The license for SNES9x states specifically:

Permission to use, copy, modify and/or distribute Snes9x in both binary
and source form, for non-commercial purposes, is hereby granted without
fee, providing that this license information and copyright notice appear
with all copies and any derived work.
This software is provided ‘as-is’, without any express or implied
warranty. In no event shall the authors be held liable for any damages
arising from the use of this software or it’s derivatives.
Snes9x is freeware for PERSONAL USE only. Commercial users should
seek permission of the copyright holders first. Commercial use includes,
but is not limited to, charging money for Snes9x or software derived from
Snes9x, including Snes9x or derivatives in commercial game bundles, and/or
using Snes9x as a promotion for your commercial product.
The copyright holders request that bug fixes and improvements to the code
should be forwarded to them so everyone can benefit from the modifications
in future versions.
Super NES and Super Nintendo Entertainment System are trademarks of
Nintendo Co., Limited and its subsidiary companies.


“Commercial users should seek permission of the copyright holders first” – refer to Hyperkin’s Retron5 licensing software page here –

They used the SNES9x Next fork specifically. This is a fork that I created specifically to serve as a libretro core. My list of contributions extends to the following:

– Added game-specific speedhacks to make them fullspeed for low-power systems like the Nintendo Wii and PlayStation3. This includes games like Final Fantasy III/VI, Star Fox, Star Fox 2, Super Mario World 2: Yoshi’s Island, and numerous other cores which were previously too slow on such devices.

– Added SuperFX overclocking code to make it possible to run SuperFX games at faster rates.

– Converted the entire codebase from C++ to C89.

– Wrote the libretro API integration parts together with Themaister/Hans-Kristian Arntzen. (NOTE: Libretro is licensed under the MIT license)

As you can guess, they have never sought my permission to use this in their commercial product. And they will never get it either. They are expressly forbidden by me (one of the copyright holders) to use this version of SNES9x in their commercial product. I’m still awaiting a response from the rest of the upstream SNES9x devs but I can’t expect their reaction will be that much different.

I will be taking steps of my own accord to ensure that this situation will be rectified.

Non-commercial cores – Genesis Plus GX

The Genesis Plus GX developers have been made aware of the facts as well and they can make their own moves as to how to deal with this.

On SNES9x Next however, I have considerable copyright claims and therefore I am in an ideal position to clamp down on this misuse of its code.

Last parting message

This can be read from Hyperkins’ response to our earlier article on

It has always been our intention to release the relevant source code for the open source emulators used within RetroN 5. We have not been as quick as we could have been, since we have been busy improving the RetroN 5 user experience. The relevant source code has now been released. From this point forward we will not only keep our copy of this code updated for those who wish to obtain the latest version, but also submit patches for any fixes that we implement back to the original projects so that the entire community may benefit. Hyperkin will continue to endeavor to fulfill the licenses of any project used within RetroN 5 and any other software we write.

If Hyperkin is indeed serious about this, they will save my time and the time of the Genesis Plus GX developers by pre-emptively (and immediately) stripping the non-commercially licensed SNES and Genesis cores from their product. We’d rather be busy doing actual development that users benefit from and that benefits the community instead of having to go to the trouble of sending a bunch of Cease & Desist notices.

Also, let it be known that as of this moment I have contacted the FSF regarding the GPL violation matters because there remains too many unanswered and unsolved problems for us to be thoroughly satisfied. Our beef is not with the product – if Hyperkins’ Retron5 was put out in a honest way and in a way that wouldn’t infringe upon the licenses of these emulators, they would be legally allowed to use it in this way. As it stands, they did not do their homework before putting this product out and their actions so far reek of negligence, irresponsibility and a calculated move to reap the rewards of copyleft code without having to honor the license’s terms.

RetroArch, Libretro core license violations by Hyperkin’s Retron5

Posted by on Sep 19, 2014 in Blog, GPL, Libretro, Non-commercial, RetroArch | 40 Comments

We have an open-source project called RetroArch. It has a development interface called libretro that allows for the easy creation of emulators and games that can plug straight into this program called RetroArch. This development interface is open to others so that they can run these pluggable emulator and game cores also in their own programs or devices. You can find this project on Github. ( We also have a website – We started this project in late 2010 and we have been steadily increasing in popularity. We are on over 15 different hardware platforms right now that you can run RetroArch on, including Android (which this Retron5 device is based on).

These open-source programs are covered under certain licenses. Several of the emulators are covered under non-commercial licenses, which means they cannot be sold or profited from.

We have discovered that Retron5 is in violation of the licenses of several projects:

Genesis Plus GX
1. It uses the open-source emulator ‘Genesis Plus GX’ by author Eke-Eke for its Sega Genesis/Mega Drive module ( This core has been licensed under a non-commercial license. It can therefore not be sold as, or part of, a commercial product.

Proof is in the accompanied screenshots at the bottom of this post.  None of the authors were contacted about their code’s use in the Retron5 hardware.



More evidence: (1, 2, 3, 4, 5, 6)

SNES9x Next

2. It uses the open-source emulator ‘SNES9x Next’, which is itself a derivative of SNES9x ( I (Squarepusher) personally made this version of SNES9x. It has a few differences compared to normal SNES9x. It has SuperFX overclocking code and it has certain game speed hacks that make games run faster on slower hardware. This comes at the expense of some graphics inaccuracies though.

We could tell it was the SNES9x Next core because the exact same strings for variables to do with the speed hacks and the SuperFX overclock code popped up in their SNES core.

SNES9x is licensed under a non-commercial license. Like Genesis Plus GX, it can therefore not be a part of a commercial product.

What also bears pointing out is that SNES9x Next has never been released in any other version than the libretro version. Libretro is the development interface of RetroArch if you remember. We will return to this later on.

Proof is in the accompanied screenshots (see below). None of the authors were contacted.




More evidence (1, 2, 3, 4, 5, 6).



3. It uses the open-source emulator ‘FCEUmm’ for its NES module, which is itself a derivative of FCE Ultra. FCEUmm is licensed under the GPLv2. Technically they would have been allowed to sell this IF they had made sure their frontend was compatible with GPLv2. Unfortunately, this turns out not to be the case as we’ll find later on – since they are using GPLv3 code inside their frontend as well which is technically incompatible with this license.

Proof of it being FCEUmm is in the accompanied screenshots (see below).

More evidence (1, 2, 3, 4, 5, 6)

VBA Next

4. It uses the open-source emulator ‘VBA Next’ for its GBA module. VBA Next is a derivative of another emulator called VBA-M. I (Squarepusher) made this version specifically and I could recognize it was this version because of the fact that I have built-in a game database into this emulator. The game ID strings that are used to identify the ROMs appeared in Retron’s GBA module as well. As for the rest of the code, it is undoubtedly VBA. The screenshots showing the code flow of operation will illustrate this clearest.

VBA Next is licensed under the GPLv2. None of the authors were contacted. Proof is in the accompanied screenshots (see below).


More evidence (1, 2, 3, 4, 5, 6)










5. We found obvious bits of RetroArch’s sourcecode inside their frontend. Now the reason we could identify these snippets is because it is inlined Assembly code that is hard to obfuscate. The relevant parts are the ARM NEON-optimized sinc resampler code and the audio integer to float conversion routines. If you want photographic evidence, I refer you to the second link I posted below.

All of the other C code of RetroArch seems to have been obfuscated so it will take us some more time to identify these parts. What is evidently clear though is that they are already in violation of the GPL license that we covered this RetroArch code under. GPL version 3 specifically forbids TIVO-ization. Let me explain later what TIVO-ization is. It basically means that you use opensource software to make a locked-down hardware device that doesn’t allow you the freedoms that the GPL generally provides to users and developers alike.

Since they have used our libretro cores evidently and since the only way to actually use these cores is through a libretro frontend implementation, and since actual RetroArch code has already been identified in their frontend, this raises serious questions as to how much of their frontend constitutes ‘original work’ and how much of it is just RetroArch. Either way, they are in the wrong for several reasons here:

– They should have also made these publicly available for every user to download since that is part of the rules and stipulations of using GPL code.
– They made a locked-down crippled hardware device based on open-source software. You void your warranty if you attempt to modify the copyleft-licensed software on this product and furthermore it doesn’t even allow you to do this.  It is not possible to run the original, non-crippled RetroArch frontend on this device, only the crippled one provided by HyperKin. It also uses encryption as a means to obfuscate and hide the originating source of this software. This is TIVO-ization and the GPL version 3 was specifically made to prevent this.

What is TIVO-ization?

Tivoization /ˈtiːvoʊɨˌzeɪʃən/ is the creation of a system that incorporates software under the terms of a copyleft software license (like the GPL), but uses hardware restrictions to prevent users from running modified versions of the software on that hardware. Richard Stallman coined the term in reference to TiVo’s use of GNU GPL licensed software on the TiVo brand digital video recorders (DVR), which actively blocks users from running modified software on its hardware by design.[1][2] Stallman believes this practice denies users some of the freedom that the GNU General Public License (GNU GPL) was designed to protect.[3]

The GPL version 3 was specifically made because GPL version 2 did not provide enough safeguards against abuse like in the case of the TIVo digital video recorders. They would take from open source, not credit anybody and not give anything back either – and even create a closed platform around it where they would set themselves up as owners of the software (and in effect the hardware).

GPLv3 forbids you from building a gated community around open-source software like this and giving nothing back in return. The fact that they have used RetroArch’s GPL version 3-licensed audio resampler code in a product that is running a locked-down, encryption-crippled version of Android is already bad enough. That they don’t even provide to users the ability to run content on this device without any restrictions is another serious concern.

Anyway, as it stands right now in its current state the product is using parts of our software illegally. There were also some other things found that were legally questionable like a Microsoft-licensed Verdana font which is covered by a End-User License Agreement, so there are multiple license violations here at play.

More evidence of RetroArch appropriation (1, 2, 3, 4, 5, 6, 7).

Multiple license violations, multiple conflicting licenses, bad faith

The problems with this are many-fold, but for us it comes down to mixing non-commercial cores on this device with more permissively licensed cores,  the infringement of the emulator authors’ rights, the lack of credit paid where credit is due, the lack of freedom in the hardware device (which restricts the user in what he/she can do and makes him/her reliant on Hyperkin to serve as the gateway keeper since he/she can’t uncripple this version of Android on their device without voiding their warranty and they can’t run the uncrippled RetroArch frontend on it either), and the multiple conflicting licenses. Also, the fact that changes / patches to the sourcecode have not been provided to customers of this device. These should have been made available on a public place free of charge.

Open-source is not a matter of doing with it as you please. The license is there for a reason and it needs to be followed, and it dictates how you should go about your business when deciding to make a commercial product out of such software. GPL is known as a ‘viral license’ which means that the community behind this uses the viral nature of the GPL as an effective strategy to ensure more and more software gets licensed under the GPL, since every bit of GPL code that gets incorporated into another project needs to be made GPL or GPL-compatible as well otherwise it’s a violation of the license. As it stands right now, the software for the Retron5 is very likely illegal to distribute.


1. – This image gallery shows comparisons of the infringing derivative Retron code vs. the originals

2. – This shows the RetroArch audio resampling and audio conversion routines in the Retron frontend

3. – Another image of the audio resampling code. Originally from this tweet:

4. Regarding the MS Verdana font: – “Verdana is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.”

(EDIT: A section here about the ARM Mali drivers was removed since it appears to not be related to these issues)

(EDIT2 [9/20/2014]: Updated with more pics of evidence)

After RetroArch v1.1 – RetroBox

Posted by on Aug 9, 2014 in Blog, RetroArch, RetroBox | 36 Comments

I was meaning to make this announcement after RetroArch v1.1 was released and this idea has been a bit long in the works. However, due to some sudden unexpected Kickstarters that have taken similar concepts and tried to create some kind of questionable monetization scheme around it, I felt compelled to make a pre-announcement about what we’re going to do post-RetroArch v1.1

RetroBox and why it’s needed

So the concept of RetroBox is based on a couple of problems:

  • There’s no real game console that is ‘open’ and which allows RetroArch to be on there without a jailbreak or a hack of some kind.
  • The ‘consoles’ that are open have an OS (Android) that is absolutely unsuitable for real-time performance oriented apps, such as (I don’t know) games. I’ve talked about this incessantly since 2012, but finally even the commercial games press seems to be becoming aware that there are definite performance bottlenecks associated to Android that prevents games from running at a stable deterministic framerate (read about all the problems here for instance – hardware that should be more than powerful enough with any other OS that do the job properly –
  • SteamBox/SteamOS seemed like the perfect vehicle at first for a true ‘open source’ gaming console that gives us a little bit more freedom than the typical Sony/Nintendo/Microsoft offerings. However, plenty of problems there as well. First of all, the fact that it’s limited to Intel. Second, the high prices these SteamBoxes are going for. Third, the unconventional gamepad which seems just totally ill-suited for the kind of ‘retro games’ that are commonly played in RetroArch. Fourth, the fact that it’s still by a commercial company like Valve, which operates its own DRM app store, and therefore at any time (no matter how well-intentioned) can change what is allowed and what isn’t on the platform to suit its business model. Fifth, SteamOS is a bit less ambitious than I initially thought it would. Still being dependent on X11 means we still don’t escape the X11 performance tax when ideally they should have just made their Steam launcher run on top of DRM/KMS inside a console for optimal latency. A bloated Debian distribution might make for a ‘safe’ OS but not sure if Debian is the right way to go for a gaming OS and it’s going to cause a lot of maintenance issues in the future.
  • All of these ‘alternatives’ that exist so far, either fall into the Android camp and are therefore no good (Ouya and the usual suspects), and/or they are being run by entrepreneurs who put their bottom line first before any passion for the project in general. Trying to base your operations around such a thing is like trading one evil (the big silo’ed off console platform holders) for another one, and in the end I’m not sure if the newer evil is going to be all that better to begin with.


So what is the RetroBox project going to amount to?

  • Figure out a way to turn ARM/x86 small form factor boxes (from Intel NUCs all the way into XBMC boxes) into plug-and-play game consoles powered by RetroArch.
  • Have a free open source distribution that is very lightweight.
  • Strive for the most optimal conditions possible – ie. DRM/KMS mode, no X11, minimal packages installed in this distro other than what libretro ports/RA actually needs.
  • Make this a ‘Proof of Concept’ for what a game console centred around the libretro API can be.
  • Plug-and-play – can be operated with a gamepad entirely, keyboard and mouse are entirely optional.

RetroBox will be an open-spec game console. It’s not owned by any particular company, and it will operate much like the 3DO/VCR model where any manufacturer could make his own box. Because RetroArch is so impressively multi-platform and portable, you don’t even have to limit yourself to a specific processor architecture like ARM – most libretro ports are available for most microarchitectures available, so you can pick and choose your own hardware.

The aim here is to create an ecosystem that is more open, more optimal and definitely more interesting than what is provided so far by the Androids, iOSes, and Steams of this world. And to have a POC game console platform of our own that illustrates this best.

Why is RetroArch a good fit for this?

  • From its inception, RetroArch has featured a gamepad-controlled UI that has thrown many PC users for a loop that were used to traditional WIMP point-and-click UIs. We have sticked to our guns for a long time and maintained this was the right road to travel, because we always envisioned RetroArch as this ‘game console platform’ all unto itself. RetroBox will see that high-level concept come into reality and made even more convenient.
  • Our API perfectly allows for the kind of plug-and-play portability we want and need through this game controller abstraction called the RetroPad.
  • RetroArch is second to none when it comes to optimal audio/video. Despite the so-far pretty lacklustre eyecandy found in its UI, there is basically nothing out there it plays second fiddle to when it comes to this department. And it’s also one of the few projects that aims for certain best practices on Linux like ensuring that everything can be ran from DRM/KMS instead of just solely depending on X11.  Latency, audio/video performance, and the impeccable shader subsystem all make for a great platform for a game console.
  • People are already doing this right now anyway. There’s an obvious demand for this and there’s an obvious need among all those ARM boxes to introduce some sanity to them and to make sure that things run right out of the box. It’s a lot of work having to fiddle around with these boxes and to even get semi decent/passable performance out of them. Might as well focus on this and make it part of the overall plan

So what is this project NOT going to be?

Every effort will be undertaken to ensure this will not be your typical sleaze-ridden entrepreneurial ‘scam’ where the main incentive is ‘get-rich-quick’. There will be NO Kickstarters, no Indiegogos, no crap like that going on. I would find it morally unconscionable raking in thousands of bucks for an undertaking like this off something that is typically going to be used by most people as a way to play emulated videogames run on copyrighted trademarked video game consoles made by commercial companies. If other people want to sell out and try to make themselves a buck off this ‘retro game stuff’, they can go ahead and do it. We will try to maintain a clean nose and keep ourselves out of this potential legal quagmire. The ramifications will be huge in the long run and we refuse to have any part in it.

So, crowdfunding is not an option. So far we are going to run the RetroBox project with our own personal finances and with the hardware we already have. Which is why it’s essential that we have your support in this endeavor. Hardware gifts will be of the utmost importance in ensuring this project will become better. However, hardware gifts will only be necessary for stuff we necessarily need – so that this doesn’t become another way of profiteering altogether.

Not just about emulation

Also, RetroBox will NOT be only about emulation. I keep stressing that RetroArch is NOT a multi-system emulator frontend, and I mean it. I want to ultimately see this evolve into its own game platform, with indie games, emulators, games, virtual reality applications and rich multimedia applications all competing for the user’s same attention. So you will be also seeing a lot of additional stuff not related to emulators at all, but which will be just as exciting.

Of course, because this is an open-spec console, emulators don’t get relegated to the sidelines like they would on a traditional videogame console. This is what will make RetroBox different – the freedom is in the hands of the user, and the platform holder doesn’t dictate to the user what he/she can’t do with this box.

What about features that people want to see?

We will try to make sure that this has as many of the bells and whistles that these sleaze-ridden KIckstarter-founded projects have such as Ignition and Gamertopia. The whole NES Remix-idea for a kind of retro game console is a good idea, as is netplay, leaderboards and that kind of thing. We think we can do all of this better anyway because of RetroArch’s impeccable cross-platform nature. I think we can do this netplay in a way that every RetroArch port out so far on any platform can play together with the RetroBoxes all the same.

What about standardization?

  •  There will be a Retro Performance Level (going from 0 to 15 and beyond) introduced that will range from very low-tier hardware to top-tier hardware (such as, say, SteamBox specs). Libretro cores will be able to look at this level at runtime, compare it to the performance level of the box in question and thereby evaluate whether or not the machine it’s running on will be able to run the core at fullspeed. If it can’t, it will display a warning.
  • This console will be about libretro ports using the libretro API. Therefore, we can gut any part of the Linux distribution that we don’t need.
  • I strongly believe in zero dependencies and keeping everything as lightweight as possible. Cores are also designed with this ‘zero-dependency’ ideal in mind. Everything that a libretro core should need should already be baked into the core from the start, so that it isn’t necessary for us to ship a truckload of packages (all of which can be potential dependencies and maintenance hazards) into the main distribution. So that means that if a core requires libusb, libusb gets baked in. If a core requires SDL, either the SDL specific code gets entirely removed or SDL gets baked in. Zero dependencies and making sure as much as possible is contained within the same dynamic library as the core itself will make this game console model sustainable.
  • By keeping this limited to the libretro API, it will basically be no different from any other RetroArch port to any platform we have done before in the past, like the PS3, 360, and whatnot. It is the same concept, except this time we’re going to make it happen for all this commodity hardware that is around.

So what will all this take?

  • Time
  • Community support. More hands on decks for this project, the better – since we will need to cover a lot of hardware
  • Dedication and the will to see this through to completion. Not going the obvious sleaze-ridden entrepreneur route obviously puts us at a large commercial disadvantage to play on an even playing field but then having risks is all part of the fun and we think users can see behind the promises of most of these other projects anyway. We have had a consistent track record so far and we are not going to compromise on our core values now either.

So when will all this start?

So yeah, this announcement is a bit of a ‘jumping the gun’ type of affair, but I felt I had to say something. I felt compelled to make this post because I see a lot of Johny-came-latelys trying to make a buck for themselves by filling an obvious gap in the market, and I just want them to know about our plans and that there’s something coming up that will put all their ‘accomplishments’ to crap. Hopefully people have gotten wise at this point and they don’t buy into another Ouya. Then again, given the obvious sleaze associated to these Kickstarter-led ‘game consoles’ and the empty hollow platitudes and ‘dumbspeak’ (and most importantly the amount of money they can accrue), you never know.

This project will start being kicked into high gear after RetroArch v1.1 is released. If you are interested in helping out in any way possible, drop us a mail at  This project is being started because most importantly we feel like doing it and not out of any sleazy attempt to ‘get rich quick’ or whatever the incentive is by most of these entrepreneurs. Hopefully our attempt to keep this ‘real’ and not branch off into entrepreneurial la-la land will be appreciated by endusers, developers and platform holders alike.

RetroArch v1.1 – What to expect

Posted by on Aug 5, 2014 in Android, Blog, OpenGL, PPSSPP, PSP, RetroArch | 71 Comments

Here’s a rundown on what you can expect from RetroArch v1.1, the next version of RetroArch to be released. Please bear with us that it has taken us so long since v1.0.0.2 to come up with a new official release. This v1.1 version has been long in the making to ensure that this new version will be a big major milestone for RetroArch in general.

So, here’s what the release will comprise of –

Going all PSP – PPSSPP core


We have ported the popular PlayStation Portable emulator, PPSSPP, over to the libretro API. This marks the second big libretro implementation to be using libretro GL after Mupen64 Plus.

It is shaping up to be a very stunning release.  Linux users will especially appreciate the changes we’ve made which makes it possible to run PPSSPP in DRM/KMS mode (something which wasn’t possible in standalone since glew has X11 dependencies).

We’re aiming for two modes of operation. One mode will be in which the PPSSPP core functions much like standalone – where it saves everything inside a main PPSSPP assets directory and you install games from PPSSPP’s GUI. The other mode is more like a headless mode – the way every libretro core has functioned up until now. Saves will be saved in .srm form and it will be possible to directly boot ISOs/PBPs/.BINs without having to install them first from a GUI. There’s something to be said for both modes of operation.

We of course take no credit for any of the real emulation work in PPSSPP – the only thing we take credit for is porting it to the libretro API. We take nothing away of the accomplishments made by this team and we hope that the libretro port can be pushed upstream once it’s done. Please pay them a visit at and support their efforts to improve PSP emulation – they’ve already come a long way in the two years it has been public.

We’ve made some screenshots of the core in action which you can check out here and on Twitter. We’re striving to expose as many of PPSSPP’s features as possible through core options for headless mode operation.

Needless to be said, we think this will be one of the main standout features of RetroArch v1.1. Hopefully it will open up people’s minds about how RetroArch and libretro doesn’t necessarily mean retro-grade graphics – some of these games  like Tekken 6 and Soul Calibur Broken Destiny don’t look far removed from their PS3 versions when upscaled to 2x or 3x. And to see it running as fluidly as it does in RetroArch without any audio breakup whatsoever or any frames dropped is a sight to behold.

The PPSSPP core will be available for PC (we’re aiming for Linux/OSX and Windows), and mobile (iOS/Android/Blackberry). After version 1.1 is released, we will research an Xbox 360 port.

Going all PSP – RetroArch PSP


Just having a PSP core would be one thing, but RetroArch v1.1 is going to go one extra mile by also simultaneously appearing on the PSP itself.

Nearly all of the credit for this port should go towards aliaspider- I played only a minor but crucial part in the proceedings. He has really done a bang-up job porting over a great many new cores over that are useful for the PSP, as well as improving the performance of existing cores so that they run well on the PSP.

Right now we have greatly improved the performance of FCEUmm, NXEngine, Gambatte, Mednafen PC Engine (and others) so that they run fullspeed at PSP. Please keep in mind that a PSP for general purpose code is about two times as slow as a Raspberry Pi. So you’re dealing with a very weak CPU here, and so it necessitates specific PSP-specific code to really get the most out of its performance. And thankfully the libretro API allows for this – the libretro API doesn’t prevent you from taking advantage of PSP-specific hardware features in order to speed up performance inside a core.

Aliaspider also made a port of TempGBA over to the PSP. This is a Game Boy Advance emulator based on gpSP Kai (itself based on gpSP – a now defunct emulator by Exophase). There’s also a preliminary port of the popular CPS2/Neogeo emulator, but it isn’t yet done. No idea yet if this core will make it for the v1.1 release.

Like hunterk’s previous blog post indicated, the portability of RetroArch is really coming into its own now. With the PPSSPP core, it will be possible to run RetroArch PSP itself. So essentially what you have is that RetroArch PSP can be made to run inside a PSP emulator which itself is being run inside a native platform version of RetroArch. How much farther can we go from here? The future only knows.

New cores

Several new cores will be appearing. We made a port of fMSX and BlueMSX to the libretro API. This was a home computer released in the mid-1980s that was backed up by a consortium of companies (among them a little company called Microsoft and another small fish called Sony). Oddly enough, while it couldn’t really be considered a major worldwide success, it was relatively popular in Japan and (of all countries) The Netherlands. This home computer is also noteworthy for receiving some of the first games Hideo Kojima made in his career, such as Penguin Adventure (one of the first games I ever played BTW) and Metal Gear 1/2.

There will be RetroKeyboard support for these cores to sweeten the deal, but we will also try to have some sane default configs for the RetroPad per-game for some of the more popular games.

There will also be a Vectrex core, Vecx. This was another ’80s game console, and the main notability of this game console is that it wasn’t using sprite rasterization but rather vector-based. For all practical purposes it could be considered the first real home console capable of ‘3D graphics’.


Lakka – a new GUI beginning


Lakka will appear inside RetroArch starting as of version 1.1. So far, users have been using a very low-fi menu called RGUI. It is perfectly scalable from low-resolution displays to high-definition TVs, but there’s no denying it looks very much like something you would expect from a DOS program.

Lakka will be a more full-featured eyecandy UI. It will require OpenGL support inside the RetroArch version, so expect this to be usable on RetroArch PC and Android/iOS/Blackberry (PS3 maybe if it makes it for v1.1).

In terms of features and appearance, Lakka looks a lot like the PSP’s XMB frontend.

In the future, more menu drivers can be added, each being tailored towards a specific enduser preference. We have made the menu code far more generic to allow for different implementations which doesn’t require the coder to rewrite all the settings logic again and again.

You can watch a video of a prototype in action here – keep in mind that this is still a prototype and that the final version will look a lot more refined. In case you wonder, the guy showcasing it here is one of the authors responsible for the Lakka GUI –  Jean-Andre Santoni (known also as kivutar).

Audio DSPs / Software Video Filters

We already touched upon this in the previous blog post about RetroArch v1.0.0.3 (which has now morphed into version 1.1). This feature has been implemented and it makes it possible to apply audio DSP filters and video software fitlters to RetroArch’s audio/video output.

Blackberry 10

We received a Blackberry Z10 phone from Blackberry sometime ago. In return, we will fully support Blackberry 10 starting as of v1.1. A new audio driver has been written, ALSA QNX, which should be far more optimal than the OpenAL driver we had before. We also intend on writing a nice Qt UI which wraps around RetroArch itself.

I know there has been a lot of discontent among Blackberry users that there have been so few releases, but rest be assured, we’re working on it.

Revamped iOS / OSX ports

I finally bought a Macbook Pro, and so I’ve been spending a lot of work on the OSX / iOS ports of RetroArch as of late. We’ve revamped nearly all of the settings so that it is possible for settings to be exposed to WIMP menus. This will be put to good use in the OSX / iOS ports of RetroArch.

The iOS version will be totally revamped as well. Cjori was working with me sometime ago on Controllers For All support. Hopefully I will be able to approach him a week before release time or so that we can do some final beta testing before we put the final polished version out.

X-Arcade Tankstick support


I received an X-Arcade Tankstick courtesy of Xgaming, and in return this device will be fully supported. Android support will be added, and I will also look into making it possible to bind it in RetroArch as two separate game controllers instead of it being recognized as a keyboard.

After v1.1, I will look into adding USB input drivers for the PlayStation3, Wii and Xbox 360 ports so that we will be able to use the X-Arcade Tankstick on thosee consoles as well without using their proprietary gamepad converter (which costs an additional $30).

Revamped Android port

Lots of work still remaining on the Android Port. The input code has been totally revamped and it should be possible to map a new gamepad directly from the menu. New input overlays have also been made (such as a a default RetroPad overlay) which works quite well.

Maybe if we make it in time we can revamp a lot of the UI code as well using our new generalized settings code which should prevent code duplication issues in the future.

Improvements to existing cores

Lots of improvements have been made to Mupen64Plus since the last new release, as well as a lot of other cores. We will also try to bring over the MAME/MESS 2014 cor e to Android – this might not appear on the Google Play Store since this will increase the APK size by about 150MB or so – instead a more fully featured version might be available on our new website.

New server

Starting with the release of v1.1, there will be another big change – a new server (Virtual Private Server), and with it will come a buildbot. We will finally have the ability to do continuous integration tests and have daily builds for the cores and the RetroArch platform versions. The existing website will soon be moved over to the new host – the transition will be as seamless as possible to the user, so hopefully you guys won’t notice when we finally make the switch.

So when will it come?

The rest of this month will be spent by me and others feverishly working to get all of this stuff in a presentable state. We also want to do a fair bit of Quality Assurance so that this next big version will be very solid. The estimated release is somewhere in early September. A new release is contingent on all these different factors all coming together. In case some parts might take longer than expected, we might just drop a version of v1.1 with some of these features being added later. In any case, you shouldn’t have to wait longer than early September.  Again, we’re sorry for some of the delays and announcements from before but we’re really trying to ensure here that this next RetroArch release will be a real big gamechanger and so the delays are justified from that perspective. Hopefully you’ll agree once it is dropped.

Also, I’m sure I neglected to mention a fair few new features as well in this writeup. In any case, there have been far too many changes since February of this year to sum up in one blog post. When v1.1 hits I will put up a more comprehensive overview of everything that has been added ,changed and improved.