apoc06

my apologies. the attach rates are approximately [or as approx as the source assumes] 6.59 for the xbox360, and 3.58. that brings the numbers to about 7 and 4.

note: these are only the us figures.

anyways, even with the updated numbers the equation still stands. doubling the size of the ps3 userbase while maintaining that all of the new users will have similar buying habits equates to: PS3 owners are still buying loads of games, but very few EA titles.

if the ps3 userbase was equal to the xbox360s and the attach rate tripled to 12 games per console, EA would have still only made $51M, because PS3 owners refuse to buy their subpar software.

i look at it like this, i own both consoles. in my eyes, the second that a developer comes out and says 'x version is inferior'. i immediately realize: "they really dont care to make decent software. im not buying this". i eliminate the potential possibility of me ever buying that game. the second that they said that they couldnt [read: didnt put in enough effort] get their flagship game to run at equal framerates, i eliminated that purchase from my shopping list. [im not paying for live again, so most multiplayer stuff i buy on PS3]

EA ruined their own payday, and tons of PS3 owners are on strike against EA and capcom. if you dont keep your customers happy, what do you expect? they get no sympathy from me.

until ea creates games on the ps3 that are equal or better than their xbox360 counterparts, i wouldnt buy anything from ea on the ps3 either.

if the xbox360 attach rate is around 7.8 games, and the ps3 is about 5.5... taking userbase into consideration, that equates to the ps3 owners buying nearly the same amount of games, but would only increase EA's sales to $35M.

that means that ps3 owners are buying the games, its just not from EA. can you blame em?

this nega-review is actually more useful than most reviews. i need to know the downsides of a game. if i can live with the bad, then i know its a game i should own.

if MS retains the halo brand, and bungie does not wish to continue to create halo games, why would MS "need" to keep them? bungie has created some great IPs. i loved oni, halo and myth well before i realized that the were all created by the same studio that is creating halo games.

however, their original ips never really sold outrageously well. even myth was eclipsed by the balder's gate series. marathon sold well, b/c it was one of the few solid games available exclusively for the mac at the time.

w/o halo perhaps ms is worried that they may become their next rare. [which i could imagine MS letting go of before bungie]

you can ALWAYS count on bungie for a hit. but halo is undoubtedly their homerun. the problem is that every team needs players you can count on for hits, even if it doesnt go out of the park everytime like halo did. i hope that MS keeps them on board, with the support of MS' financing bungie has tons of hits and even a few homeruns left.

sounds like they changed it alot. the new format sounds like midnight club to me. am i the only one?

geez, did no one watch the interview?

#1. the kid saved his dad's life. period. most adults would have panicked and went into shock.

#2. the kid has been asking for a ps3 for a while.

#3. he's nine! sure if he was an adult, he would have just been doing what was expected. at nine years old, he knew how to work the CB to call for help and he knew not to panic.

#4. how is he a brat? the kid didnt ask for a reward. the father offered to get him a reward for his heroism. the kid responded that as the reward, he wanted the ps3 he has been asking for.

whoever is playing really sucks.

wipeout is not meant to be played this slow. the graphics look good, but they need to show off gameplay at one of the faster classes.

coding against a moving engine is tough, but what developers often do is pick a 'blessed' version or a 'stable build' as a footprint and build off of that.

imagine choosing a linux kernel to build your application on. it works fine on that kernel. if a newer kernel becomes available, you recompile your code for that kernel and if there are any problems with dependencies that arise, you either abandon the new kernel branch and continue on as normal, or you just patch the section of your code thats now buggy. developers arent trying their code on every single new build of the engine.

you dont start building a house and then change the foundation. if you can get away with it, fine. but youre gonna have to fix the few bricks that get broken when you shift the foundation. if you dont want to fix what breaks, maybe you shouldnt even bother trying to alter the foundation.

"no one has written anything in machine code in years"? lol. if youre not a programmer, or have no knowledge of creating games dont make blanket assumptions like that.

the reason most games are written in c/c++ is because c is fast. as fast as c is, assmebly is even faster. parts that need to run /really/ fast are written/ optimized in assembly.

you would be amazed to learn just how many of your favorite games have sections of code written in assembly. [ESP ps2 games]

what happened to wipeout XL|2097?