Posts

As of 6:20PM CST, we can confirm that our PS3’s are working as expected on the PlayStation Network.  All DRM/DLC, trophies and saved data is present and accounted for.  We first got word of this from Izmeiah Brown, our Lead Designer, when it broke on Gizmodo.  Still no official word from Sony, but that’s typical and to be expected.  This ability to login, however, does not mean that it won’t happen again.  Scary how they can push an update like this and shut almost 40 million systems down without no one really noticing, isn’t it.

This is a use at your own risk deal since there has been no official word from Sony yet.  We’ll let you know as soon as they start making apologies.

== UPDATE ==

Sony releases the following statement on their blog:

We are aware that the internal clock functionality in the PS3 units other than the slim model, recognized the year 2010 as a leap year. Having the internal clock date change from February 29 to March 1 (both GMT), we have verified that the symptoms are now resolved and that users are able to use their PS3 normally.

If the time displayed on the XMB is still incorrect, users are able to adjust time settings manually or via the internet. If we have new information, we will update you through the PlayStation.Blog or PlayStation.com.

We apologize for any inconvenience this may have caused.

And that’s that.  They “apologize”, but fail to state exactly what they’re going to do for breaking the trust of all of the gamers WORLDWIDE.  Sure the PSN is free, but come on; The trade off is quite obvious at this point – monitoring.  We should be able to play Single Player games like Heavy Rain regardless if the PSN is online or not.  We should also be able to use our games that we downloaded without being told we stole it (basically what the error message implied).  These are the things that they should be focusing on and making Next-Gen actually Next-Gen. 

As one comment we read earlier today, you could pop in a Nintendo cartridge, and BAM you were playing the game.  Why doesn’t this work the same way today for the PS3?  And what about the people without access to the Internet?  Are they still affected?  We’ll never know because they’re completely out of touch with the rest of the living world.  Trust us, if this happens again, we’re going to make sure they answer these questions that all gamers of the PS3 deserve.

PlayStation Network Down

As we had reported last night, the Sony PlayStation Network was (and still is) down because of an unexplained technical issue.  The issue causes an error code of 8001050F to appear upon launching any PS3 Blu-Ray Game, setting the clock back to 12/31/1999 (sounds a lot like a Y2K bug), trophy sync problems and downloaded content (DLC) to show that there are invalid copyright permissions.  This has caused a lot of headache among hundreds of thousands of gamers globally and still no update from Sony on their blog or their Twitter feed.

So, what is this? A PS3 Y2K bug? Possibly.  The error code “8001050F” is referenced to mean “Hardware failure. Cannot update firmware or connect to internet.” However, upon launching most games, players are getting a message stating “Registration of the trophy information could not be completed. The game will quit. (8001050F)”. Why would this be? Shouldn’t the PS3 work offline too? That’s what we thought. All of our offline DLC, such as Final Fantasy VII and Final Fantasy VIII (PS1/PSP Playable) does not work at all. We can’t play single player games that shouldn’t rely on the Internet or not such as Heavy Rain. All we have to say is we hope that this is fixed today, and for sure before the 9th of this month, when Final Fantasy XIII releases.

Usually by this point, Sony would/should have replied…but what’s to be expected from a free network?  Our advice: If you haven’t turned on your PS3 yet, don’t. It’s tragic enough to read about and even worse to see for yourself. Last night, the topic of “playstation network crash” hit the #5 hottest trend on Google and now currently sits at #40. Wait until Sony updates their Blog or Twitter with “we’ve fixed the error”. We will keep you posted as well, so stay tuned.