Skip to content

Comment on Activision’s Kotick: ‘We May Not Make Games For The PS3 Next Year’parent

Comments

Between the PS3, Wii, or Xbox 360 I prefer the PS3. Granted, FPS on the Xbox suck when compared to FPS on a PC; so I don't really play any multiplier games on it. Basically, I feel console gaming is mostly about the arcade feel and the PS3 wins that.

PS: The largest gap IMO was needing to buy recharable battery's for the other systems. That really bothered me for some reason.

The main problems I have with the PS3 are 1) the size & and the content of its software library 2) the QA level of the games

Programming for the PS3 is no easy task given the strange design of the cell processor and short comings of Sony's SDKs and frameworks. Given this, I feel that most developers/publishers are less apt to take risks with PS3. This leads to less games, and more games that are mainly ports from the 360. To add insult to injury most of these ports (and DLC) come later and they also tend to have a lot more bugs.

In defense of PS3, the other consoles aren't perfect either (360's were breaking left and right, and not having a hard drive by default was a big mistake game wise; Wii's software library is mostly shovel ware for 5 year olds); but imo the PS3's shortcomings are still the worst

EDIT: if PS3's new motion controller is as good in real life as it was at E3, it may change things.

"Programming for the PS3 is no easy task given the strange design of the cell processor and short comings of Sony's SDKs and frameworks."

Isn't the Xbox 360 processor based on the Cell design?

yeah all of the cpu's for this gen of consoles are from IBM including the Wii

Someone can correct me, but to me the main difference between the 360's cpu and PS3's cpu, besides the number of cores, is that the 360's cpu cores are more general purpose while not all of the Cell's cores are equal... The Cell has one main core (PPE) and 8 Synergistic Processor Elements (SPEs). These SPEs are not as powerful as a normal core (and I think one of them is reserved for the OS), and (I think) they're main purpose is solely for graphics (well mainly good at dealing with floating point nums). If I remember correctly, the 360 has three general purpose, equally powerful cores (PPEs) in its version of the IBM cpu.

I can imagine someone from IBM probably selling a Sony exec on how the Cell processor can save money by having Cell do both general processing and handling all the video rendering without a separate GPU... which we all know didn't quite work as well as Sony had hoped, since PS3's had an NVidia chip plopped in last min (this probably explains why programming for a PS3 really sucks since Sony wasn't planning on having a separate GPU)

The PS3 has a graphics card. SPE's can be used to preprocess some information to increase graphics quality or to crunch numbers for AI code, or do any number of things. The problem is you can either code for the lowest common denominator between the systems and mostly ignore SPE's or build a game focusing on the PS3.

PS3 has:

  Cell@3.2Ghz, yada yada
  RSX 550 MHz, 300+ million transistors, ~200 GFLOPs
PS: The RSX has a higher GFLOPs than the Cell but it's only really usefull for specific graphics operations.

"The PS3 has a graphics card"

I mentioned that. The problem is PS3 wasn't meant to have a graphics card. The Cell was envisioned to do everything from the start. Years of planning went by before something inexplicably changed (maybe what they saw in real life didn't match what IBM promised?). The graphics card was added in at the last minute (which essentially resulted in a quick hack for release) or Sony's SDK/frameworks would have made it easier to use everything.

In Sony's defense, MS and Nintendo had some planning snafus too. Wii has that weird system for OS updates / new features and 360 will always be associated with red rings.

The 360's processor is based on the good part of Cell, not the impossible-to-program parts.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.