I saw this Project on Flathub and tried it. It works well enough and I like that its ready to go out of the box without needing to install cores like Retroarch. The UI is different from Retroarch, but is there any big advantage? Does anybody use it? And why?
Ares has a N64 core that’s mostly homegrown (not based on any existing emulator like Mupen) and has a lot of promise. It’s actually probably already the best N64 emulator, but I don’t think many people know that.
The reason for this was to build on the successes of the bsnes revival to create an easy-to-use multi-system emulator, as well as to begin adding more modern systems such as the Nintendo 64 and PlayStation, which simply cannot be emulated using the cycle-accurate model of higan.
Basically, Ares was bsnes > higan > bsnes (v2) > forked to be a multi-emulator again. Super confusing, yes.
I think like with any other standalone emulator compared to RetroArch, the main benefit would be the user interface and the entire configuration setup. Ares is a more traditional application with less functionality and narrow focus. That makes it simpler and more native to use on your operating system. Also you don’t need to learn and understand how RetroArch is setup, with all its configuration, because how many features it supports and how generic it is.
Note: I’m a huge RetroArch fan, its not dunking on it or anything like that.
Also some people don’t like that RetroArch itself does not have emulator cores, but rather use other cores (which is the entire point of it and why I’m loving it). Ares is completely its own thing (but a fork of higan, which was based on Bsnes, RIP Near). And because its much simpler, people might be understanding its source code better.
Also I don’t use and don’t know what Ares actually supports and can do. In example I have a separate and standalone Mesen, just because of its excellent debugging features (when I experimented with romhacking).
Add comment