Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I don't understand why people think this is a "leap year" issue. 2010 is not a leap year and I never heard of anyone experiencing this back in 2008 (which was a leap year).

Pretty much every Zune in the world crapped out from a leap year bug. A bug can be related to leap year and pop up any other time depending on how they coded the calendar.
 
That update is garbage. For one, my clock set itself to December 31, 1999 (not January 1, 2000). Secondly, the error message I received did not say, “Failed to install trophies. Please exit your game.” It says, "Registration of Trophy Information could not be completed. The game must quit."
I don't think that status update was meant to be a comprehensive list of all the possible effects and errors one might encounter, though.
 
Pretty much every Zune in the world crapped out from a leap year bug. A bug can be related to leap year and pop up any other time depending on how they coded the calendar.

Okay. Weird. Leap day has only been around for about 2,000 years, so it makes sense that so many tech companies would overlook it. :rolleyes:

I don't think that status update was meant to be a comprehensive list of all the possible effects and errors one might encounter, though.

True, but it just seems like they are trying to gloss over the effect this problem is actually having by saying the PS3 nicely suggests you quit the game, rather than forcing you to quit on the first loading screen. Perhaps I'm just reading too much into it, though.
 
That update is garbage. For one, my clock set itself to December 31, 1999 (not January 1, 2000). Secondly, the error message I received did not say, “Failed to install trophies. Please exit your game.” It says, "Registration of Trophy Information could not be completed. The game must quit."

At least they got the error code right. :rolleyes:



I don't understand why people think this is a "leap year" issue. 2010 is not a leap year and I never heard of anyone experiencing this back in 2008 (which was a leap year).

The theory is that 2010 was INCORRECTLY marked as a leap year. Which would be why 2008, which WAS a leap year, would have been safe.

Not sure what logic they used in their calendar to determine leap years... it's literally 1 line of code

Code:
isLeapYear(int year){
[INDENT]return ((year % 4 == 0 && year % 100 != 0) || year % 400 == 0)[/INDENT]
}

Also... how they evidently thought to correct this issue on the PS3 Slim but it slipped their mind to do anything about it on the PS3 FatBoy is beyond me.
 
The theory is that 2010 was INCORRECTLY marked as a leap year. Which would be why 2008, which WAS a leap year, would have been safe.

Not sure what logic they used in their calendar to determine leap years... it's literally 1 line of code

Code:
isLeapYear(int year){
[INDENT]return ((year % 4 == 0 && year % 100 != 0) || year % 400 == 0)[/INDENT]
}

Also... how they evidently thought to correct this issue on the PS3 Slim but it slipped their mind to do anything about it on the PS3 FatBoy is beyond me.

Speculation is that they might have done it by two instead... that would explain why, given this is the first even numbered non-leap year since launch, it's failed.

Means that unless it was patched the same would happen in 2014 too...

PHazer
 
Speculation is that they might have done it by two instead... that would explain why, given this is the first even numbered non-leap year since launch, it's failed.

Means that unless it was patched the same would happen in 2014 too...

PHazer

That could make sense... I guess with a November release in 2006 that would be possible. Although I'd imagine they had the system up and running for at least a year in testing before release...
 
The theory is that 2010 was INCORRECTLY marked as a leap year. Which would be why 2008, which WAS a leap year, would have been safe.

Not sure what logic they used in their calendar to determine leap years... it's literally 1 line of code

Code:
isLeapYear(int year){
[INDENT]return ((year % 4 == 0 && year % 100 != 0) || year % 400 == 0)[/INDENT]
}

Also... how they evidently thought to correct this issue on the PS3 Slim but it slipped their mind to do anything about it on the PS3 FatBoy is beyond me.

Speculation is that they might have done it by two instead... that would explain why, given this is the first even numbered non-leap year since launch, it's failed.

Means that unless it was patched the same would happen in 2014 too...

PHazer

Very interesting. Thanks for the info.

Sony sucks.
 
I wonder if we will see the head of playstation 3 design team commit Hari Kare after this total utter balls up.

I have three ps3's and I dare not turn two of them on, even to watch a blu-ray. Utter joke. :rolleyes:
 
I wonder if we will see the head of playstation 3 design team commit Hari Kare after this total utter balls up.

I have three ps3's and I dare not turn two of them on, even to watch a blu-ray. Utter joke. :rolleyes:

What do you use 3 for? Do you have a cluster going in OtherOS or do you play games on all 3?

I have 2 Xbox 360's so I'm not one to judge :p
 
Okay. Weird. Leap day has only been around for about 2,000 years, so it makes sense that so many tech companies would overlook it. :rolleyes:

Bugs happen, sometimes in the weirdest places. Finding a bug in an OS is a huge task because it could be one of a million lines of code that thinks Feb 29th exists.

I'm willing to bet it will be fixed in 20 minutes when GMT hits March 2, then the fat ps3s will roll over to March 1st (a day that thankfully does exist) and will be able to connect to PSN and sync time correctly.

In case that doesnt happen i already have my shoes off so i can shove my foot in my mouth pretty quickly ;)
 
Bugs happen, sometimes in the weirdest places. Finding a bug in an OS is a huge task because it could be one of a million lines of code that thinks Feb 29th exists.

I understand, but the fact that the newer PS3s are not affected by the "bug" means (to me) that they fixed the bug somewhere along the line but never bothered to send it out to all the people who already paid their money to Sony.
 
Well now its over and reports are saying everything is back to normal with no corruption of save data and trophies are still syncing.

These types of bugs happens with complex OS/Tech all the time..it happen to MS twice and sure enough its Sonys turn to get beat with the ugly stick. Hopefully Sony will push out an update to prevent this from happening again and upsetting its users.


I'm hoping Sony finds a way for trophies/PSN service to not interfere with single player games.


Bless
 
I'm hoping Sony finds a way for trophies/PSN service to not interfere with single player games.

I don't doubt that the system is actaully syncing important game data, but I also get the feeling it's a cover for an authentication system. I wonder what happens when the PS3 becomes retro?
On another note all my save data from beating Final Fantasy XIII is in tact, but all of my trophies for that game are gone.
 
I understand, but the fact that the newer PS3s are not affected by the "bug" means (to me) that they fixed the bug somewhere along the line but never bothered to send it out to all the people who already paid their money to Sony.

They may have different teams working on Slim firmware than Fat firmware since they do use slightly different firmwares. I'm willing to bet the RTC chip in the Slim isnt the same as the Fat, so shared code bases wouldnt help the fatties either.

Now im no economy master, but im pretty sure the people who have Slims that arent affected by the issue have also already paid Sony. Unless Sony is giving them Slims for nothing. Then i'd like to sign up for that.

I seriously doubt the Sony board members told the engineers to intentionally put a bug in the fat firmware that will cause it to stop working for 24 hours then (essentially) fix itself, causing nothing more than 1 day of down time.

Regardless, its all over now. You can take off your tinfoil helmet.
 
Now im no economy master, but im pretty sure the people who have Slims that arent affected by the issue have also already paid Sony. Unless Sony is giving them Slims for nothing. Then i'd like to sign up for that.

I seriously doubt the Sony board members told the engineers to intentionally put a bug in the fat firmware that will cause it to stop working for 24 hours then (essentially) fix itself, causing nothing more than 1 day of down time.

That's not what I was saying. Just pointing out that companies often stop supporting older hardware, sometimes to the point of worrying about things like bad code that can brick a system.
 
Now im no economy master, but im pretty sure the people who have Slims that arent affected by the issue have also already paid Sony. Unless Sony is giving them Slims for nothing. Then i'd like to sign up for that.

In a way, they have. Sony doesn't make any profit on their individual console sales - I think they still lose $40 or so per unit. Sony makes most of its PS3 money on licensing. So we can all rejoice in that we all bought our PS3s at cost - hooray!
 
When i got my PS3 (80gb motorstorm bundle) they were selling at much more of a loss than the current Slims. Take that Sony!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.