News for hackers. Stuff that matters.

A comment on Hacking the Xbox 360 Hypervisor Part 2: The Bad Update Exploit. Parent comment

Re:Hacking the Xbox 360 Hypervisor Part 2: The Bad Update Ex... by trashface on Monday March 03, 2025 @08:27PM (#43249055)
PS3 was wacky, but the 360 wasn't that different from a PC at the time. There were some differences in rendering API, it had a few features not available on PC hardware. And the CPU cores were actually slower than an equivalent intel, but you had 6 of them, rare for the time. If your game was relatively portable and already used a API relatively close to D3D, it wasn't too hard to bring it up on the 360. I worked on a 360 game FWIW.
[ Parent | on HN ]
Re:Hacking the Xbox 360 Hypervisor Part 2: The Bad Update Ex... by jamesfinlayson on Tuesday March 04, 2025 @01:48AM (#43251147)
Which game?
[ Parent | on HN ]
Re:Hacking the Xbox 360 Hypervisor Part 2: The Bad Update Ex... by trashface on Tuesday March 04, 2025 @12:21PM (#43257531)
It was an early xbox live arcade game. Not AAA.
[ Parent | on HN ]
Re:Hacking the Xbox 360 Hypervisor Part 2: The Bad Update Ex... by rekoil on Tuesday March 04, 2025 @03:07AM (#43251739)
Xbox 360 is also a PowerPC architecture, which on its own makes it quite a bit different from normal PC hardware, and even if that's a target that's more common to emulate there's still heavy performance losses in doing so.

It might have been easier to port to because of good OS design, but running games for it will still be inefficient compared to running on actual hardware.

[ Parent | on HN ]
Re:Hacking the Xbox 360 Hypervisor Part 2: The Bad Update Ex... by iforgotpassword on Tuesday March 04, 2025 @05:26AM (#43252812)
360 emulation was already quite good a year ago, now there's even an experimental fork of xenon that does recompilation for even more performance.
[ Parent | on HN ]
Re:Hacking the Xbox 360 Hypervisor Part 2: The Bad Update Ex... by rickdeckard on Tuesday March 04, 2025 @03:49AM (#43252096)
Regardless of the D3D-like API-layer (which helped Microsoft compensate for the peculiarities of PowerPC), they're both PowerPC architectures.

You apparently don't know the Story how Sony spent big R&D-money with IBM to transition from MIPS to the custom PowerPC Cell Architecture, while IBM was already selling parts of this development to Microsoft for Xbox 360, and Microsoft ultimately beating Sony in market-launch with a chipset Sony partially financed...[0]

There's a nice book about it from two of the IBM Chip-Designers called "The Race for a New Game Machine" by David Shippy and Mickie Phipps

[0] https://www.theguardian.com/technology/blog/2009/jan/01/sony...

[ Parent | on HN ]
Re:Hacking the Xbox 360 Hypervisor Part 2: The Bad Update Ex... by PaulHoule on Tuesday March 04, 2025 @10:56AM (#43256340)
Nintendo also used PowerPC for GameCube, Wii and Wii U.
[ Parent | on HN ]
Re:Hacking the Xbox 360 Hypervisor Part 2: The Bad Update Ex... by trashface on Tuesday March 04, 2025 @12:28PM (#43257629)
The PS3 system design was radically different. We considering porting the same PC game we (relatively) easily ported to 360 to that platform, but rejected it because it would be months of work, at least. Didn't matter that it was a similar CPU (technically) to the 360.
[ Parent | on HN ]
Re:Hacking the Xbox 360 Hypervisor Part 2: The Bad Update Ex... by pjmlp on Tuesday March 04, 2025 @12:30PM (#43257641)
Microsoft was helped by PS 3 being a pain to program, given the Cell architecture, a mistake that Sony didn't repeat, and hence why the 360 was the only XBox that had an upper hand against Sony.
[ Parent | on HN ]
Re:Hacking the Xbox 360 Hypervisor Part 2: The Bad Update Ex... by maximilianburke on Tuesday March 04, 2025 @10:39AM (#43256070)
The 360 had three hyperthreaded cores, not six.
[ Parent | on HN ]
Re:Hacking the Xbox 360 Hypervisor Part 2: The Bad Update Ex... by trashface on Tuesday March 04, 2025 @12:20PM (#43257521)
It had 6 hardware threads, but yes pedantically there were three cores.
[ Parent | on HN ]