[Ed Note: Updates will be posted below the jump, as they come in. Thanks! - R.T.]
Remember the N64? Remember how it didn’t brick itself because the internet went down? Yeah me, too.
If you’re a PlayStation 3 owner, or if you spend any time on the internet, you might have noticed that PSN seems to be having issues. Just in case you missed it, a few hours ago people began to notice their PS3s were unable to connect to the PlayStation Network as well as corrupting their dynamic themes and even their… *dramatic pause* …trophies.
Perhaps the most aggravating and (possibly telling) issue with this whole thing is the fact that it’s affecting single player games. That’s Single. Player. Games. I’m personally having trouble wrapping my mind around how any console manufacturer (yes, even Sony) could find a way to get their systems to screw up in such a manner.
Initially, Sony mentioned that they were aware of the problems and were “looking into it.” It’s been determined that the 120/250GB Slim models have been working just fine, but if you happen to own a “Fat” PS3 consider yourself warned.
—–
[Update] – In an unsurprising twist, Sony’s little PSN drama is also effecting debug PS3s. Meaning the systems game developers use to make the games (that we can’t play at the moment) we all know and love can’t actually work on them. F-ing brilliant, Sony.
At least they’ve finally updated their Twitter, linking back to a post in their blog in which they say they believe the problem has to do with the system’s internal clock settings. They advise owners of non-Slim PS3s to avoid using the system, as it could result in a plethora of errors that a clock really shouldn’t be able cause. It’s good to know they haven’t decided to ignore the issue, but the fact that something as ridiculous as this could keep people from playing games offline fills me with a special kind of rage.
Seriously, Sony… Learn from this.
[Update 2] – According to both their Twitter and their blog, PSN is fixed. Let’s hope something like this Never. Happens. Again.
I miss my N64 and SNES…
I hope Sony learns something from this. However I’m fairly pissed off because I know they won’t.
Between this, the YLoD I got two years ago, the RRoD and E74 errors, I’m thinking that maybe this console generation just suuuucks.
Apparently they still haven’t figured out a solution, and now it’s been revealed that even debug systems are failing. Way to go, Sony…
Maybe it’s just an aggressive marketing ploy to maximize new console sales in time for God of War 3…
The sad thing is, I could see Sony trying something like that.
*facepalm*
It
Only
Does
Self Resurrection
Lol, apparently this was all caused by Sony neglecting to realize 2010 is a leap year. This makes it so much more epic.
No it was the PS3 thinking it was a leap year when infact it was not. The next leap year is 2012
Thanks Raymond. I guess I should know that, especially since my grandfather was born on February 29th.
Either way, the notion that a clock error brought down the majority of PS3s is staggering.
I still can’t get over the fact that it screwed up single player games. :P