Slashdot Mirror


Is There Anything Wrong w/ Playstation 2 API?

adubey asks: "Over and over I've heard game programmers say that it is difficult to write games for PlayStation 2. A lot of these quotes came from gaming sites or the mainstream press, where there probably aren't as many programming-literate readers as there are on Slashdot. So perhaps Slashdot might be a better place to ask ``what is wrong with the PlayStation 2 API?'' Are there any PSX2 programmers here who might be able to give some insight? Can this even be discussed without breaking any NDAs?" This is the first time I've heard of such a thing. Where did this rumor get started?

3 of 9 comments (clear)

  1. Hardware Managment by robbieduncan · · Score: 2

    Although I am not a PSX2 programmer I remember reading that the API for PS2 has made the individual games programmer more responsible for the transfer of data and control between the various processing units in the PS2 and ensuring that the work done by these units is synchronised. This makes the offloading of the graphics and sound to the relevent chips more difficult, but allows for increased effeciency and custom uses. Sorry can't remember where I read this, so can't provide a link.

  2. Ars had a great technical article long ago... by MrScience · · Score: 2

    I usually go to www.arstechnica.com for the real news. At any rate, this article discusses the emotion engine and why it is so difficult to code for. It also has a few good links for other background info. Needless to say, it's not just a rumor, Cliff.

    Have fun! :)

    --

    You quitting proves that the karma kap worked. The most annoying of the whores shut up. --CmdrTaco

  3. Poor documentation and bizarre architecture by Echo|Fox · · Score: 2

    I heard this firsthand from someone who is presently coding on the PS2. Can't mention who specifically, since I have no idea what his NDA's are like.
    Anyway, his beefs were three-fold. First, the documentation given to them by Sony was bloody awful. The translation wasn't so hot, and some parts ranged from confusing to flat out wrong. Some documented functions just didn't behave the way the docs said they would. It's hard coding blind.
    Secondly, the architecture is overly strange whereby established procedures just couldn't be used. There are multiple paths one can take to accomplish and no one really knows which ones work yet since the design is so foreign. I got the feeling that prior console or PC programming experience was probably a bad thing, since the way you previously would have done things was no longer valid. These sentiments were echoed by Dr. Buchanan, head of Research at Electronic Arts at a presentation at the University of Alberta last year.
    Oh, and the third thing? And I quote: "It doesn't have enough texture memory to render my ass, let alone a good game."