4 ms·
Modern emulation devs keep the heat low by making it extremely cumbersome and complex to use their emulators. The last time I looked, you had to have a hacked s
by Gigachad 5y ago
Modern emulation devs keep the heat low by making it extremely cumbersome and complex to use their emulators. The last time I looked, you had to have a hacked switch and run some home brew tool to dump files of the system which you can then use to run the emulator.
This in my opinion is to make using the emulator even harder than just running pirated games on your already hacked switch. And then once the console is discontinued, the devs just make it work out of the box.
- matheusmoreira 5y agoI don't think it's hard on purpose. Not sure what those files are but they're in all likelihood copyrighted and therefore illegal to distribute. So the emulator developers make it the user's problem. It's just like the PlayStation emulators and their BIOS images.
- Gigachad 5y agoMost emulators reimplement that stuff. Virtualising the console is the whole point of the project. I’d expect in 5 years you won’t need any files because the console will no longer be commercially viable.
- matheusmoreira 5y agoIndeed. I agree that virtualizing the whole console is the goal. It is also true that older systems had some software in them that got reverse engineered and replaced by emulator developers. There are GBA BIOS images circulating out there but they are not necessary for GBA emulators to work. This is the ideal. However, older systems were also much simpler. The GBA BIOS functions may have been simple enough that it was not difficult for the emulator developers to reverse engineer and reimplement them natively. Newer systems such as the PlayStation no doubt had extremely complex software controlling hardware like the disc drives. I've even seen references to C standard library functions in the debugger documentation and many notes detailing how buggy they were. I have no doubt there are games which rely on those bugs. Reimplementing all this software would be a significant undertaking. Easier to just make the user obtain a copy of the original software. That's how its done to this day even though the PlayStation is already 5 generations behind. It's definitely possible to emulate or reimplement this software, it's just hard and the focus of emulator projects is usually on the hardware. There are other projects which aim to do this stuff though! I've seen game engine emulators which are open source reimplementations of the engines of older games. Users are expected to plug in the copyrighted game assets themselves. Perhaps one day consoles will be nothing but standard PCs under the hood and emulating them will consist of reimplementing the APIs the games use to interface with the operating system just like Wine and the Windows API.
- Gigachad 5y agoI think it's likely that both of these can be true. That it is easier for the developers to not emulate it, but also that there is no will to get it done right now because it makes emulation hard for non developers but still easy for them. Which lets them develop in the dark without the media and legal teams on them.
- Firehawke 5y agoAbsolutely this. The firmware contains copyrighted data and that data is also critical to the functioning of the Switch, both emulated and real. Modern handhelds are not like the older ones, there's actually an OS involved and a lot of per-system settings that uniquely identify your Switch-- especially when it connects to Nintendo's servers or authenticates if you're allowed to play a digital game.
- matheusmoreira 5y ago> it connects to Nintendo's servers or authenticates if you're allowed to play a digital game Always wondered about that. I have no doubt all current systems do this sort of thing. How does the emulator handle it?
- dfxm12 5y agoI don't know in this specific case, but for other games/emulators you can either use a hacked version of the game that doesn't require a security check, or, if you can reverse engineer what the authentication server does, point the game to some other server (i.e. https://en.wikipedia.org/wiki/Bnetd#CD_key_non-interoperability https://en.wikipedia.org/wiki/Bnetd#CD_key_non-interoperabil...) that acts that the authentication server.
- dabeledo 5y agoOlder handhelds had also their quirks! The original gameboy boot bios would load the Nintendo logo from the cartridge ROM and would run a "checksum" of the logo data, to compare it with a constant value stored in the Bios itself - it the logo in the cartridge is the copyrighted Nintendo logo, it would start the game. With that Nintendo wanted to be sure that any cartridge would require a copyrighted logo so a License would be technically required.
- matheusmoreira 5y agoSEGA also did this! The so-called trademark security systems. Completely insecure, but violating it gave the console manufacturer the perfect excuse to sue the violator. Lawsuits involving this system had really interesting results. In one case, the judges not only ruled that the trademark infringement was fair use, they said that SEGA made the trademark infringement necessary in order to produce compatible games due to their own security system. The infringement was SEGA's own fault! The world used to be great before DMCA criminalized even the attempt to cricumvent these things. https://en.wikipedia.org/wiki/Sega_v._Accolade https://en.wikipedia.org/wiki/Sega_v._Accolade