emulator

apple-removes-the-first-ios-game-boy-emulator-released-under-new-app-store-rules

Apple removes the first iOS Game Boy emulator released under new App Store rules

4K apple tv, App Store, Apple, emulator, emulators, gaming, gba, guidelines, iOS / /

Easy come, easy go —

iGBA seems to have taken unauthorized code from earlier GBA4iOS project.

–

Photos of iGBA that appeared on the App Store before the app was taken down.

Enlarge / Photos of iGBA that appeared on the App Store before the app was taken down.

Over the weekend, developer Mattia La Spina launched iGBA as one of the first retro game emulators legitimately available on the iOS App Store following Apple’s rules change regarding such emulators earlier this month. As of Monday morning, though, iGBA has been pulled from the App Store following controversy over the unauthorized reuse of source code from a different emulator project.

Shortly after iGBA’s launch, some people on social media began noticing that the project appeared to be based on the code for GBA4iOS, a nearly decade-old emulator that developer Riley Testut and a partner developed as high-schoolers (and distributed via a temporary security hole in the iOS App Store). Testut took to social media Sunday morning to call iGBA a “knock-off” of GBA4iOS. “I did not give anyone permission to do this, yet it’s now sitting at the top of the charts (despite being filled with ads + tracking),” he wrote.

GBA4iOS is an open source program released under the GNU GPLv2 license, with licensing terms that let anyone “use, modify, and distribute my original code for this project without fear of legal consequences.” But those expansive licensing terms only apply “unless you plan to submit your app to Apple’s App Store, in which case written permission from me is explicitly required.”

Images from the original, circa 2014 version of GBA4iOS.

Images from the original, circa 2014 version of GBA4iOS.

“To be clear, I’m not pissed at the developer [of iGBA],” Testut added on social media. “I’m pissed that Apple took the time to change the App Store rules to allow emulators and then approved a knock-off of my own app.”

Hurry up and wait

MacRumors reports that Apple cited two sections of its App Store guidelines in removing iGBA: one related to spam (Section 4.3) and one related to copyright (section 5.2). Right now, it’s a bit ambiguous whether the copyright violation refers to the copyright on the emulator source code itself or the emulator’s ability to easily play copyrighted games from Nintendo and others.

As we discussed earlier this month, the wording of Apple’s recent App Store guidelines update makes it unclear if developers can release general-purpose emulators with the ability to play ROMs they don’t control the rights to. Aside from iGBA, a Commodore 64 emulator named Emu64 XL and built off of the open source VICE project was recently launched on the iOS App Store.

Apple has yet to respond to a request for comment from Ars Technica. But Testut wrote early Monday morning that “to Apple’s credit, though, once they were aware of the issue, they did take it seriously. So I really don’t believe this was malicious at all — just an unfortunate situation for everyone involved.” Testut added that iGBA maker La Spina “reached out to me via email to personally apologize for the mess. So no hard feelings there.”

But Testut did have some hard feelings regarding Apple’s treatment of AltStore, an alternative marketplace for sideloading iOS apps that he’s trying to launch under the EU’s new regulations. That would provide Testut with a legitimate way to distribute Delta, a “sequel” to GBA4iOS that emulates many classic Nintendo consoles on Apple devices.

“My frustration stemmed entirely from the fact we’ve been ready to launch Delta since last month,” Tetstut wrote on social media. “This whole situation could’ve been avoided if Apple hadn’t delayed approving us until after changing their rules to allow emulators.”

Apple removes the first iOS Game Boy emulator released under new App Store rules Read More »

switch-emulator-suyu-hit-by-gitlab-dmca,-project-lives-on-through-self-hosting

Switch emulator Suyu hit by GitLab DMCA, project lives on through self-hosting

DMCA, Emulation, emulator, gaming, gitlab, Nintendo, suyu, Switch, takedown / /

They can run… —

Developer says there’s “no way to confirm” if Nintendo was involved in takedown.

–

Is a name like

Enlarge / Is a name like “Suyu” ironic enough to avoid facing a lawsuit?

Suyu

Switch emulator Suyu—a fork of the Nintendo-targeted and now-defunct emulation project Yuzu—has been taken down from GitLab following a DMCA request Thursday. But the emulation project’s open source files remain available on a self-hosted git repo on the Suyu website, and recent compiled binaries remain available on an extant GitLab repo.

While the DMCA takedown request has not yet appeared on GitLab’s public repository of such requests, a GitLab spokesperson confirmed to The Verge that the project was taken down after the site received notice “from a representative of the rightsholder.” GitLab has not specified who made the request or how they represented themselves; a representative for Nintendo was not immediately available to respond to a request for comment.

An email to Suyu contributors being shared on the project’s Discord server includes the following cited justification in the DMCA request:

Suyu is based off of Yuzu code, which violates Section 1201 of the DMCA. Suyu, like yuzu, is primarily designed to circumvent Nintendo’s technical protection measures, namely Suyu unlawfully uses unauthorized copies of cryptographic keys to decrypt unauthorized copies of Nintendo Switch games, or ROMs, at or immediately before runtime without Nintendo’s authorization. Therefore, the distribution of Suyu also constitutes unlawful trafficking of a circumvention technology.

A Suyu Discord moderator going by the handle Princess Twilight Sparkle shared a message Thursday evening citing the project’s “legal team” in reporting that Suyu will have to use the self-hosted Git repo “in the foreseeable future. Getting our GitLab back most likely needs us to go through a lawsuit, which is going to be very difficult… Thanks for your understanding.”

Troy, listed as a “Core Suyu Developer” in the Discord server, wrote Thursday afternoon that the DMCA request came from an “unknown source” and that there is “no way to confirm” if Nintendo was involved. “There is also a possibility that the person who sent this DMCA is a copyright troll, like on YouTube, based on the wording of the DMCA reason that was sent to GitLab,” Troy wrote.

Suyu Discord moderator and contributor Sharpie told Ars Technica that “we don’t have any more information than you at this time.”

Earlier this month, Sharpie outlined to Ars many steps the project’s developers were taking to avoid potential legal consequences, including avoiding “any monetization” and taking a hardline stance on any discussion of piracy. Despite those precautions, Sharpie admitted to Ars that “Suyu currently exists in a legal gray area we are trying to work our way out of.”

Switch emulator Suyu hit by GitLab DMCA, project lives on through self-hosting Read More »

here’s-how-the-makers-of-the-“suyu”-switch-emulator-plan-to-avoid-getting-sued

Here’s how the makers of the “Suyu” Switch emulator plan to avoid getting sued

Emulation, emulator, gaming, lawsuit, legal, Nintendo, Switch, yuzu / /
Is a name like

Enlarge / Is a name like “Suyu” ironic enough to avoid facing a lawsuit?

Suyu

Last week, the developers behind the popular Switch emulator Yuzu took down their GitHub and web presence in the face of a major lawsuit from Nintendo. Now, a new project built from the Yuzu source code, cheekily named Suyu, has arisen as “the continuation of the world’s most popular, open-source Nintendo Switch emulator, Yuzu.”

Despite the name—which the project’s GitHub page notes is “pronounced ‘sue-you’ (wink, wink)”—the developers behind Suyu are going out of their way to try to avoid a lawsuit like the one that took down Yuzu.

“Suyu currently exists in a legal gray area we are trying to work our way out of,” contributor and Discord moderator Sharpie told Ars in a recent interview. “There are multiple plans and possibilities for what to do next. Things are still being organized and planned.”

Doing things differently

The Suyu project arose out of “a passion for Switch emulation” and a desire not to see “years of impressive work by the Yuzu team go to waste,” Sharpie said. But that passion is being tempered by a cautious approach designed to avoid the legal fate that befell the project’s predecessor.

After consulting with an unnamed “someone with legal experience” (Sharpie would only say “they claimed three years of law school”), the Suyu development team has decided to avoid “any monetization,” Sharpie said. The project’s GitHub page clearly states that “we do not intend to make money or profit from this project,” an important declaration after Nintendo cited Yuzu’s profitability a few times in its recent lawsuit. Other emulator makers also told Ars that Yuzu’s Patreon opened the project up to a set of pesky consumer demands and expectations.

The Suyu devs have also been warned against “providing step-by-step guides” like the ones that Yuzu offered for how to play copyrighted games on their emulator. Those guides were a major focus of Nintendo’s lawsuit, as were some examples of developer conversations in the Yuzu Discord that seemed to acknowledge and condone piracy.

Xenoblade Chronicles the day before its release.” height=”626″ src=”https://cdn.arstechnica.net/wp-content/uploads/2024/03/yuzuleak-640×626.png” width=”640″>

Enlarge / In a blog post cited in Nintendo’s lawsuit, the Yuzu developers discuss compatibility with a leaked copy of Xenoblade Chronicles the day before its release.

Suyu, by contrast, is taking an extremely hard line against even the hint of any discussion of potential piracy on its platforms. The Suyu GitHub page is upfront that the developers “do not support or condone piracy in any form,” a message that didn’t appear on Yuzu’s GitHub page or website.

The No. 1 rule listed on the Suyu Discord is that “piracy is prohibited.” That includes any talk about downloading games or “asking for system files, ROMs, encryption keys, shader caches, and discussion of leaked games etc.” Even a mention of the word piracy with regard to legal questions is enough to earn a warning on the Discord, according to those rules.

Here’s how the makers of the “Suyu” Switch emulator plan to avoid getting sued Read More »

flurry-of-firmware-updates-makes-analogue-pocket-an-even-better-retro-handheld

Flurry of firmware updates makes Analogue Pocket an even better retro handheld

analogue, analogue pocket, Emulation, emulator, fpga, Game Boy, Game boy Advance, gaming, Nintendo, openFPGA, retro console, Retro Gaming, Tech / /

super game boy —

Display filters for FPGA cores, custom Game Boy color palettes, and more.

–

An Analogue Pocket running <em>Super Mario World</em> on an openFPGA core with the scanline filter enabled.” src=”https://cdn.arstechnica.net/wp-content/uploads/2024/01/IMG_1480-2-800×533.jpeg”></img><figcaption> <p><a data-height=Enlarge / An Analogue Pocket running Super Mario World on an openFPGA core with the scanline filter enabled.

Andrew Cunningham

We’ve got a soft spot for the Analogue Pocket, the premium portable game console that melds 2020s technology with the design of the original Game Boy. Since its release, Analogue has added some new capabilities via firmware updates, most notably when it added support for emulating more consoles via its OpenFPGA platform in the summer of 2022. This allows the FPGA chip inside of the pocket to emulate the hardware of other systems, in addition to the portable systems the Pocket supports natively.

But aside from finalizing and releasing that 1.1 firmware, 2023 was mostly quiet for Pocket firmware updates. That changed in December when the company released not one but two major firmware upgrades for the Pocket that slipped under our radar during the holidays. These updates delivered a combination of fixes and long-promised features to the handheld, which Analogue has been re-releasing in different color palettes now that the original versions are more consistently in stock.

The most significant update for OpenFPGA fans is the ability to use display filters with third-party FPGA cores. Part of the appeal of the Pocket is its 1,600×1,440 screen, which is sharp enough to perfectly re-create the huge chunky pixels of the original Game Boy screens. By default, most FPGA cores now get access to a similarly high-quality CRT screen filter named after the Sony Trinitron TV, adding a touch of retro-blurriness to the sharp edges of 8- and 16-bit games. I’ve seen lots of bad, unconvincing scanline filters in retro game re-releases, and this isn’t one of them.

The basic Trinitron filter is available by default for “suitable” cores, which in our testing tends to mean “home consoles that were meant to be connected to a CRT TV.” FPGA cores for portable systems like the Game Boy or Game Boy Advance, which shipped with old but scanline-less LCD screens, don’t have the filter available. Third-party FPGA core developers will need to add support for additional screen filters themselves, something that most developers still haven’t done as of this writing.

  • A zoomed-in photo of the screen with no filters enabled. It’s sharp and crisp, and even zoomed in with a good mirrorless camera it’s difficult to make out individual pixels on the Pocket’s screen.

    Andrew Cunningham

  • The same scene with the Trinitron CRT filter enabled. Subtle scanlines, visible CRT “pixels,” and just the right amount of blurring makes the picture look more period-accurate.

    Andrew Cunningham

  • Zoomed out, scanlines off.

    Andrew Cunningham

  • Scanlines on, default “integer” scaling used. This is the most accurate aspect ratio, but it leaves a black border of unused pixels around the screen.

    Andrew Cunningham

  • Scanlines on, Integer+ mode used. This eliminates the black border and, to my eyes, looks just fine on the Pocket’s screen and makes the effect of the scanline filter easier to see.

    Andrew Cunningham

The Trinitron filter looks good on the Pocket’s screen, but it’s subtle; you may appreciate the scanline effect more and notice its downside less if you’re playing while connected to a TV with the Analogue Dock. And at least on the NES and SNES cores I tested it with, it has the undesirable side effect of shrinking the game picture down on what is already a fairly small screen. This default setting can be tweaked without visibly degrading the image quality, at least not to my eyes; just switch from the default Integer scaling mode in the display settings to Integer+.

The screen filters are probably the most interesting and requested new feature for the Pocket, but both firmware updates have many other smaller fixes and additions. Firmware version 1.2 fixes numerous issues with sleep/wake and save states for various games, allows FPGA cores to use cartridge adapters, and lets FPGA cores know when the Pocket is in a dock; when docked, it also adds support for additional controllers and fixes issues with others. Version 2.0 adds support for custom color palettes for Game Boy games, allows FPGA cores to switch aspect ratios when docked, and fixes a “video issue with some openFPGA cores and resolutions” when docked.

To update the Pocket’s firmware, connect the device’s microSD card to your computer and drop one of the firmware update .bin files into the root directory (make sure you delete any older firmware files first since the Pocket won’t delete old update files once it’s done with them). Next time you boot the console, it should install the firmware update and reboot. As usual, when performing any software or firmware update, it’s best to ensure the console is fully charged or plugged in before you start the process.

Flurry of firmware updates makes Analogue Pocket an even better retro handheld Read More »