Author: News Polite

Sony’s major upcoming update to PlayStation Plus consolidates its existing services into three tiers, the two most expensive of which offer players hundreds of games from PlayStation’s current and back catalog. As the PS5 is only backward compatible with the PS4, these new plans are the only way for players to access PS1, PS2, PS3, and PSP games on their latest PlayStation systems. Most of those libraries will be directly downloadable, but there is a major outlier: PlayStation 3 games will only be available to stream, as has been the case on PlayStation Now.

This disparity is disappointing, particularly for fans with poor internet speeds that cannot reliably stream games. Following the lack of PS3 backward compatibility on the PS4, the announcement once more raised the question: Why won’t Sony emulate its 2006 console, which has a fantastic library of games, and could there be technical issues preventing them from doing so? To find out, I spoke to the developers of fan-made PS3 emulators to understand why the unique construction of the PS3 hardware continues to haunt PlayStation. IGN has also reached out to PlayStation for comment on the lack of PS3 downloads for PlayStation Plus, but did not hear back by the time of publishing.

Development Hell

The primary roadblock to proper, official PS3 emulation could be that, well, the console was built differently. The PlayStation 3 utilized a unique structure that differed from the relatively simpler Xbox 360 and PC architectures at the time that Sony called “Cell.” The PS3 console’s CPU was comparable to the Xbox 360, running at 3.2GHz, but Sony aimed to bolster the CPU’s capabilities by including seven floating co-processors, aka the PS3’s synergistic processing units (SPUs), which were infamously complex for developers.

Here’s a brief rundown of how it worked. The processor’s setup allowed the central power processing element (PPE) to offload complex code to the extra cores. Those SPUs could handle parallel mathematical calculations, which made them perfect for intricate physical simulations, like collisions, clothing, and particles. Sony flirted with the concept in the PlayStation 2, but boosted the power in the PS3 with a floating speed that was forty times faster than its predecessor.

Harnessing the PS3’s potential – back then and in the present day – wasn’t easy in large part because the process described above wasn’t automatic. Developers had to code this handoff themselves, creating a multi-step process that resulted in a steep learning curve for programming on the PlayStation 3. We’re all familiar with the time pressures developers face and the prevalent problem of crunch that may arise as a symptom of these time pressures. When developing for multiple platforms, developers regularly ignored the complicated SPUs and just used the PPE. When it came time to port Bayonetta to PlayStation 3, Platinum Games producer Atsushi Inaba described to Edge Magazine how Platinum handed the project off to an in-house team at Sega. A failure to utilize the SPUs resulted in terrible performance compared to other platforms. Inaba called it at the time “the biggest failure for Platinum so far, the one that really sticks in my mind.” A similar story surrounds the problematic PS3 port of The Orange Box, which Valve handed off to EA rather than tackling it themselves. Simply, re-engineering games for a completely new system unlike any other was a time- and cost-prohibitive process, which meant that the Cell processor wasn’t used to anywhere near its full extent.

Despite sinking millions into Cell architecture, the complexity of its SPU hardware contributed, in part, to a slow start for the PlayStation 3. Add onto that the PS3’s much higher retail price and the extra year the Xbox 360 enjoyed ahead of its release, and the PS3’s potential wasn’t realized until late in its life-cycle.

Simulating Synergy

Sony was aware of the issues its console caused developers, though wasn’t especially apologetic about it at the time. “We don’t provide the ‘easy to program for’ console,” CEO Kaz Hirai told Official PlayStation Magazine in 2009. “A lot of people see the negatives of it, but if you flip that around, it means the hardware has more to offer.”

Some developers weren’t shy about criticizing Sony’s choices for the PlayStation 3’s architecture back then. Gabe Newell, speaking to Edge Magazine, branded it “a waste of everybody’s time.” Kazunori Yamauchi, creator of Gran Turismo, recently told TheGamer that the “PS3 was a nightmare” and that “the hardware was so complex and difficult to develop on.” A 2007 doctoral study by Daniele Paolo Scarpazza, Oreste Villa and and Fabrizio Petrini supported this, finding that “software that exploits the Cell’s potential requires a development effort significantly greater than traditional platforms.”

Thirteen years later, the PS3 architecture is still causing headaches.

There are several unofficial PS3 emulators available today. On one of them, RPC3, 65% of the PS3’s catalog is currently playable. I asked its developers about the problems emulating the PS3.

One of RPCS3’s developers, Whatcookie pointed to the PlayStation 3’s “128 byte read/write as well as the quirky floating-point format that the SPUs support” as the major bottleneck in reaching RPCS3’s stated goal of 100% compatibility. The PlayStation 5 runs on an x86 CPU like most computers. It’s one reason the PS5 is backward compatible with the PS4, another x86 system. Both have cache lines of 64 bytes, as opposed to the PS3’s 128 bytes per line.

“128 bytes of data can be written ‘atomically’ on PS3, meaning it appears as a single event, while on a system with 64-byte cache lines it appears as two events,” Whatcookie explained.

Cache in this context is essentially chunks of memory. Splitting the data into blocks – often called lines – makes the size of that memory more manageable. But it means that the PlayStation 3, which can read and write 128-byte cache lines can assimilate its own data much faster and more consistently than the PS5 which reads and writes in 64-byte blocks. This incompatibility can cause major performance issues on top of those already caused by trying to simulate the console’s Cell structure.

An alternative would be to install SPU furniture on the PlayStation 5 motherboard, which essentially means building PS3 hardware into the PS5. It’s a method Sony implemented on the PlayStation 2 and early models of the PS3, both of which included CPU architecture from their predecessors to allow backward compatibility with previous models. But of course, Sony removed those elements from the PlayStation 3 after it initially retailed at $300 more than the Xbox 360 in its earlier run of consoles. Adding that technology now would not only drive up console prices, but leave those who already own a PS5 without access to that functionality.

One user on the RPCS3 Discord told me that “developing an emulation solution for the SPUs would be ridiculously expensive [for Sony] and makes no financial sense.” Whatcookie also thought this was the case, referencing that Sony has only managed to emulate the PS1, PS2, and PSP for two generations.

“If they were making huge money from these emulators, then I think they’d put huge money into it,” Whatcookie said.

Depending on how you look at it, Sony’s struggle to emulate the PlayStation 3 is complex or incredibly simple. On one hand, an expensive maze of technological issues makes it appear a quagmire of complications. Yet it all seemingly boils down to the whole process most likely being prohibitively expensive, at least in terms of the interest and profit for PlayStation. This leaves PlayStation players with only a couple of options: Stream PS3 games through PS Now (and eventually PS Plus) or hunt down an old PlayStation 3. Either way, it’s more complicated than simply being able to download games to current consoles, as players will be able to do with PS1, PS2, and even PSP games.

Whatever the case, maybe don’t get rid of your PlayStation 3 just yet.

Geoffrey Bunting is a disabled freelance journalist. As well as IGN, he has written about games, entertainment, accessibility, and more for Wired, Rock Paper Shotgun, Inverse, and others.

Gearbox Publishing has announced Eyes in the Dark: The Curious Case of One Victoria Bloom, an atmospheric roguelite coming to PC on July 14.

Players take on the role of Victoria as she searches for her lost grandfather in the ever-changing Bloom family mansion, fighting all manner of monsters with a flashlight and slingshot in 2D twin-stick shooter style gameplay.

The game is being developed by indie developer Under the Stairs and will be available on both Steam and the Epic Games Store for $14.99.

“Eyes in the Dark creates an atmosphere of loneliness and isolation, all while giving you the tools to ultimately come out of the experience as a stronger person,” said game designer Filip Neduk said.

“Victoria’s trial – going through the mansion alone and facing her fears – mirrors the player’s need to learn and master the mechanics of the game to progress; you both go through this adventure together.”

More items and upgrades will become available to Victoria as she makes her way through the mansion including a Shotgun Bulb or matches that set your enemies alight. Each item also has a unique ability that players can mix and match to create new combos.

“One of the beautiful things that the team focused on was making sure that no two playthroughs of the game would be the same, regardless of how you guide Victoria,” added Under the Stairs’ director Vladimir Bogdanić.

The PC requirements for Eyes in the Dark were also revealed, which can be seen below:

Minimum:

• OS: Windows 7
• Processor: Core 2 Duo
• Memory: 2 GB RAM
• Graphics: Integrated graphics card
• Storage: 800 MB available space
• Sound Card: Yes

Recommended:

• OS: Windows 10
• Processor: 2.4 GHz Quad Core 2.0 (or higher)
• Memory: 8 GB RAM
• Graphics: Intel HD Graphics 4000 and higher, ATI Radeon HD-Series 4650 and higher, Nvidia GeForce 2xx-Series and up
• Storage: 800 MB available space
• Sound Card: Yes

Ryan Dinsdale is an IGN freelancer who occasionally remembers to tweet @thelastdinsdale. He’ll talk about The Witcher all day.

A former Nintendo of America employee has filed a complaint with the National Labor Relations Board (NLRB) accusing Nintendo of terminating their employment due to their involvement with a union.

The specific charge, as first reported by Axios, is levied against both Nintendo of America and recruiting firm Aston Carter, which hires contractors for various administrative and customer support roles at Nintendo. It alleges that the employee was terminated from their role due to activities connected with unionization – either joining or supporting a union, and participating in other activities such as discussing their wages and terms of employment. The complaint also accuses Nintendo of “engaging in surveillance” of union activities.

Through the NLRB, employees are protected from retaliation or termination for participating in union activities or otherwise organizing. With the complaint now filed, the next step is for the NLRB to investigate the termination to determine if it was, as is claimed, illegal and related to unionization.

In a statement shared with Polygon, Nintendo confirmed the employee in question was terminated but asserts it was not due to organization:

“We are aware of the claim, which was filed with the National Labor Relations Board by a contractor who was previously terminated for the disclosure of confidential information and for no other reason,” the statement reads. “Nintendo is not aware of any attempts to unionize or related activity and intends to cooperate with the investigation conducted by the NLRB.

“Nintendo is fully committed to providing a welcoming and supportive work environment for all our employees and contractors. We take matters of employment very seriously.”

The NLRB has been increasingly involved in video game companies’ activities lately as organization efforts continue to crop up across the industry. Just today, Apple workers in Georgia filed a petition with the NLRB to form a union. And last year, Activision Blizzard workers filed a complaint with the NLRB accusing their employers of union-busting and intimidation, and subsidiary Raven Software ultimately formed its own union. Their organizing efforts came following an ongoing series of lawsuits and accusations against the company going back to last July, beginning with a California suit accusing the company of a frat boy culture, sexual harassment, unequal pay, and more.

Rebekah Valentine is a news reporter for IGN. You can find her on Twitter @duckvalentine.