By using this site, you agree to our Privacy Policy and our Terms of Use. Close

Forums - Sony Discussion - Do you see any implications on PS3 sales, reputation, etc..because of...

I don't think so, how many times has XBL gone down, tons and you pay for that service, and everybody still loves XBL, PSN is very reliable, this is the first time I can remember it going down for reasons other then when they are maintaining the servers. Shit happens, it sucks but ounce its up and going again everybody will forget and be happy.



Around the Network
slowmo said:
theprof00 said:
slowmo said:
Random Canadian said:
slowmo said:
theprof00 said:
Nope. No backlash. xbl goes down all the time and they have plenty of other problems on top of that. This is very rare for PS and it will be fixed shortly, and it might even spark some momentum for a new update that fixes other things.
Who knows, maybe the ylod will be looked into as well. Now that Sony has some spare cash, maybe they'll do a line by line look at the coding.

XBL is rarely ever down, stop talking garbage damage control.  You don't even have a 360 so cannot comment on the XBL situaution at all.  PSN has as many problems as XBL but this isn't even a PSN issue which makes your comments even more silly.  You obviously don't understand what YLOD is either as it cannot be resolved by anything but hardware changes (which hopefully the slim will address to a degree).

Classic! When in doubt just make some shit up I guess. Ok here goes

 

Ylod is caused by heat stress on solder joints right. So if Sony goes through the code line by line, and hits delete.  Then the processor will stay always in an Idle state an not get hot enough to cause  YLOD.

I FIXED YLOD FOREVAR !!!

 

Just watch him troll the 360 for the next few days in a desperate effort to deflect some attention elsewhere.  What he fails to realise is this trolling will only lead to people really milking this current scenario for months.  Such a sad individual really, mind you its not like he can go and do something more productive like play a game is it?

why would I troll the 360? Don't be so defensive. You are wrong and I am right. There won't be backlash because it happens to all consoles from time to time, and specifically with 360 there have been much worse problems with relatively little impact. I'm sorry you cannot appreciate that.

Well you don't own a 360 now so stop talking crap.  I do own all three consoles and have only ever had one occasion when Live was down and I wanted to use it.  You're the one posting damage conrol being defensive, this is about the PS3, not the 360 but you had to have a dig because you're a troll.  I'm sorry you cannot appreciate how child like you're acting.

 

The Slim isn't affected because like the newer fat models, they use the latest board revision.

At least two other people mentioned 360 RROD...which I didn't, because RROD has nothing to do with this. I used a genuinely legitimate occurence which is both similar in nature and scope. I then refuted your rebuttal by posting 5 times it has been down in the last 3 years, not including even more regular maintenance and traffic issues.

This outage is exactly the same as one or two of those xbl outages. Unable to play games, offline, no online features available. No outcry from the 360 community (maybe some from trolls). This is the same exact thing. There's nothing wrong with comparing 2 things which have so much similarity.

 



Xbox Live downtime doesn't render your console unable to play the vast majority of the content or indeed DLC. They aren't comparable in the slightest, thats all I'm saying. Fair enough on RROD, the 360 has a shocking failure rate I will never exuse them for that mistake like you and others are doing now.

 

The Watchdog episode contained some very dodgy unofficial failure numbers but on the whole they highlight the cause of the issue quite nicely for the layman.  It was nowhere near as biased or bs as the disk scratching episode for the 360.



slowmo said:
theprof00 said:
I just think it's funny that I try to look at the bright side by mentioning that they may go through the coding line by line and people jump all over me.
You don't know either. YLOD could be caused by several processors going idle, leaving one processor to handle everything. You have no idea, yet you are comfortable enough to insult someone else.

Seriously guys, chill out. For all we know, YLOD could be caused by a line of code simply saying "F" and the cell being confused by it. If a simple date problem can cause all this, maybe a programmer typed "teh cell" instead of "the cell" and it makes 'teh cell' go into overdrive lol.

No, I do know what the YLOD is because we fix them all night long at work but I don't see the value in educating someone determind to be ignorant.   I suggest you watch the Watchdog program regarding the PS3, its rather basic in its explanation but will give you some idea of how wrong you are.

... wow why don't you work for Sony? You know the exact cause for YLOD, maybe you shoudl be on their repair team because YLOD refurbs tend to be recitivists, didn't you know? If they had your information they could put an end to it once and for all!

On a serious note, I'm aware that you probably know what the "direct cause" is. Which I don't. Maybe it's a joint that broke due to excessive heat or something. But you don't know what the indirect cause is. Nobody does. Why does the heat build up in some cases and not in others. Why is it that a team put the release ps3 in a sealed van of 100+ degrees for 24 hours and nothing happened?



theprof00 said:
slowmo said:
theprof00 said:
I just think it's funny that I try to look at the bright side by mentioning that they may go through the coding line by line and people jump all over me.
You don't know either. YLOD could be caused by several processors going idle, leaving one processor to handle everything. You have no idea, yet you are comfortable enough to insult someone else.

Seriously guys, chill out. For all we know, YLOD could be caused by a line of code simply saying "F" and the cell being confused by it. If a simple date problem can cause all this, maybe a programmer typed "teh cell" instead of "the cell" and it makes 'teh cell' go into overdrive lol.

No, I do know what the YLOD is because we fix them all night long at work but I don't see the value in educating someone determind to be ignorant.   I suggest you watch the Watchdog program regarding the PS3, its rather basic in its explanation but will give you some idea of how wrong you are.

... wow why don't you work for Sony? You know the exact cause for YLOD, maybe you shoudl be on their repair team because YLOD refurbs tend to be recitivists, didn't you know? If they had your information they could put an end to it once and for all!

On a serious note, I'm aware that you probably know what the "direct cause" is. Which I don't. Maybe it's a joint that broke due to excessive heat or something. But you don't know what the indirect cause is. Nobody does. Why does the heat build up in some cases and not in others. Why is it that a team put the release ps3 in a sealed van of 100+ degrees for 24 hours and nothing happened?

I will if you like write a basic explanation which covers both the 360 and PS3 for why it ocurs and why some models are affected and others aren't.  Ever heard of manufacturing tolerances?  I work in a repair centre that fixes all consoles so I see the worst of all of them, including handhelds.



Around the Network

Nah if this is fixed tomorrow or the day after its cool for Sony. The only way this could damage Sony is if the xbox fanboys act all rabid and emo and spam the internet with it just like the PS3 fanboys with RROD.



kowenicki said:
theprof00 said:
I just think it's funny that I try to look at the bright side by mentioning that they may go through the coding line by line and people jump all over me.
You don't know either. YLOD could be caused by several processors going idle, leaving one processor to handle everything. You have no idea, yet you are comfortable enough to insult someone else.

Seriously guys, chill out. For all we know, YLOD could be caused by a line of code simply saying "F" and the cell being confused by it. If a simple date problem can cause all this, maybe a programmer typed "teh cell" instead of "the cell" and it makes 'teh cell' go into overdrive lol.


there is a very big difference between some down time and this... stop with the damage limitation. its weak.

sony have already admitted that this could lead to some permanent data loss for instance.

I will stop when you stop calling this damage control. It's not. I'm just looking at the silver lining. I didn't know that suggesting potentialities was so looked down upon. What really confuses me is that while you condemn my hypothetical situation, you condone another hypothetical situation where Sony said

"as doing so may result in errors in some functionality, such as recording obtained trophies, and not being able to restore certain data."

MAY



JGarret said:

...this whole internal clock/8001050F problem?

I mean, depending on how quickly Sony solves the issue and other things, do you see any major negative impact on Sony and the PS3...or is that quite a stretch?

why would sales, which you must only mean as new retail sales, be affected when the PS3's at retail aren't affected by the issue?



strunge said:
JGarret said:

...this whole internal clock/8001050F problem?

I mean, depending on how quickly Sony solves the issue and other things, do you see any major negative impact on Sony and the PS3...or is that quite a stretch?

why would sales, which you must only mean as new retail sales, be affected when the PS3's at retail aren't affected by the issue?

If people are afraid to turn on their systems, chances are they aren't buying any games.



Anyone can guess. It takes no effort to throw out lots of predictions and have some of them be correct. You are not and wiser or better for having your guesses be right. Even a blind man can hit the bullseye.

slowmo said:
theprof00 said:
slowmo said:
theprof00 said:
I just think it's funny that I try to look at the bright side by mentioning that they may go through the coding line by line and people jump all over me.
You don't know either. YLOD could be caused by several processors going idle, leaving one processor to handle everything. You have no idea, yet you are comfortable enough to insult someone else.

Seriously guys, chill out. For all we know, YLOD could be caused by a line of code simply saying "F" and the cell being confused by it. If a simple date problem can cause all this, maybe a programmer typed "teh cell" instead of "the cell" and it makes 'teh cell' go into overdrive lol.

No, I do know what the YLOD is because we fix them all night long at work but I don't see the value in educating someone determind to be ignorant.   I suggest you watch the Watchdog program regarding the PS3, its rather basic in its explanation but will give you some idea of how wrong you are.

... wow why don't you work for Sony? You know the exact cause for YLOD, maybe you shoudl be on their repair team because YLOD refurbs tend to be recitivists, didn't you know? If they had your information they could put an end to it once and for all!

On a serious note, I'm aware that you probably know what the "direct cause" is. Which I don't. Maybe it's a joint that broke due to excessive heat or something. But you don't know what the indirect cause is. Nobody does. Why does the heat build up in some cases and not in others. Why is it that a team put the release ps3 in a sealed van of 100+ degrees for 24 hours and nothing happened?

I will if you like write a basic explanation which covers both the 360 and PS3 for why it ocurs and why some models are affected and others aren't.  Ever heard of manufacturing tolerances?  I work in a repair centre that fixes all consoles so I see the worst of all of them, including handhelds.

Yes I have, and am already writing under the assumption of that and other posibilities. The difference, though, is that I'm keeping an open mind about the causes. There is a reason the saying "You never know" exists. Look, I'm not trying to make a serious point about anything. I'm not saying anything with a definitive intent. I simply made an observation that this problem was a pretty stupid one. Really? An error in the calendar system? Even the millennium got through Y2K with no problems. If this is an issue, maybe YLOD is a tiny problem that someone simply glossed over too. *sigh*