Number one through nine obviously didn’t pan out. All died from either disc read errors or the Red Ring of Death. Number 9, a Falcon, suffered the dreaded RRoD a little over a week ago. Finally, I have a replacement Elite. It’s obviously a Falcon, so I can only hope this one works out better than the last Falcon that crapped the bed on me.
Everyone keep their fingers crossed that Xbox 360 stops hating me. I really don’t want to have to replace it again.
This is just very very annoying. While playing some Super Street Fighter II Turbo HD Remix Beta yesterday, my Xbox 360 went all RRoD on me. I made a sad face. I have the Best Buy warranty for a reason, but come on. I had such confidence in this one after Max’s marathon Halo 3 sessions.
I let the poor sick console sit overnight and tried to fire it up today, hoping it was just a fluke. Nope, she’s gone. Unfortunately, my Best Buy is out of Elites right now, so I have to wait until the end of the week when they hopefully get more in stock. You won’t be seeing me online for the next few days on Xbox Live. She was a Falcon, too. She’ll be sorely missed. To quote my article the last time a console died:
It’s not like I treat it like crap. It’s babied. My Xbox 360 has it’s own shelf in the entertainment center, with full ventilation from the front and rear. The power brick also sits on the shelf fully ventilated. The console is never moved when playing (in fact, it’s only moved a tiny bit once a week to dust). The console is kept perfectly clean, as are my other systems. I haven’t had any problems with my PS3 (save long install times) or my Wii. Never had problems with my PS2, Xbox, or Gamecube before that.
For the record, I’m tired of taking pictures of the Red Ring of Death when this happens. So you guys get to look an old RRoD from one of the Loot Ninja consoles.
It’s been a full 24 hours since the new firmware 2.40 was pulled from the update servers. We heard from Sony yesterday that they were looking into the issue, but that’s about it. A post on PlayStation.Blog saying the same was put up yesterday around 7:30pm ET. Nothing else has been said. What’s the deal?
We contacted Sony and have yet to hear back. It seems that they don’t want to comment on just what’s going on here, which leads me to believe they really aren’t sure what’s causing the issues. While a huge majority of people had no problems when installing v2.40, a few got bricked consoles (wouldn’t turn on, gave errors, etc.). It seems the problem lies somewhere in the install process.
Hopefully Sony drops word soon. I have a feeling the internet will go into an uproar when they release the PlayStation Store update and still don’t have a fix or any word about the firmware. We’ll keep you posted.
[Update] I just spoke with Jeff Rubenstein at Sony. He confirmed they are still working on the firmware.
We’re still examining the cause of the problem. We’ll announce as soon as we are ready to resume the system version update.
[Update 2] We received a link to the exact file that the PS3 checks for updates. This file still indicates version 2.36 as the current version. Check it out.
I just spoke with Jeff Rubenstein over at Sony. Apparently the issues with firmware 2.40 are more widespread than we originally thought. Jeff wouldn’t confirm any numbers to me, but gave me this official statement:
Looking into it right now and will work with those customers directly to address any issues they may be experiencing.
I’m trying to get more information from him, but he’s not sharing. I think Sony is in lockdown mode trying to figure this one out. More as it develops…
[Update] I asked Jeff if a new firmware version would be issued and he didn’t want to comment. So even if 2.40 is working for you, a new update may be in store.
The SSFIITHDR Beta launched today on the Xbox 360 and some people are pissed off. Buy some people, I mean pretty much everyone playing the game. The Beta is locking up hardcore to the point where you have to power down your 360. Yikes. Worst part? Capcom has no plans to fix it.
“We will not be patching the beta… resubmissions would cost a fortune and not go live for weeks even if we had (MS would have to reapprove every submission). This isn’t like the PC where a developer can make changes daily (for good or ill). All feedback and bugs will be factored into the final code.”
So if you bought Wolf of the Battlefield for no reason other than to get into the Street Fighter Beta, you got screwed. Hard. With no lube. I haven’t attempted the play the Beta yet, but I’m not expecting much given the major problems being reported.
It seems the good folks over at Sony and Idol Minds just can’t release an update to PAIN without something breaking. Last time, the update didn’t come out for 2 days and the game was wonky. This time, network connectivity has been disabled in the game, meaning you can’t access community features or buy new characters in-game. According to developer comments on the official site:
there has been a power outage in Europe that affected the staging of content for our European brothers and sisters. This is being worked on at the moment, and as soon as it is resolved (9-10am London time is the estimate we were given), we will get the update out to Europe.
Now, they’re saying that because the update got borked in Europe, the US gamers who got the update can’t connect online. Yeah, crazy, I know. Since they plan on releasing another update for the game next week (and still more content is coming), I seriously hope this gets resolved ASAP. People can only take so much broken stuff.
Yeah, I went there. If you haven’t heard “like whoa” in a few years, welcome back.
If you’re over in Europe and have GRID already for Xbox 360, you might be screwed. The game is suffering from some horrible pausing and freezing issues. GRID is scheduled for release in the US this week and no fix is out yet. Codemasters says a fix is coming in “the next few weeks.” You can check out a video of the issues after the jump.
You know, this type of thing is totally unacceptable. The game is virtually unplayable for most people. Where is the QA? There are entirely too many games shipping broken thee days. It’s sad and it’s a big problem that needs to be addressed.
We’re trying to get a handle on just how widespread the issues are with Grand Theft Auto IV. Reports are flooding our tip box of freezing issues on both consoles, online issues on the PS3, bugs in the game, etc. We’re not turning this into any kind of fanboy fest, so this is a blanket poll. No 360 or PS3 choices, it’s just yes or no. Personally, I’m about 3 hours into single player on PS3 (haven’t tried multiplayer yet) and haven’t experienced any issues.
So, let us know how your time in Liberty City is going. Is it smooth sailing or are there a lot of bumps in the road?
[Update] We’re going to put together the results and send them over to Rockstar. See if we can’t help them out in seeing how widespread the problem may be.
Loading ...
You’ve undoubtedly heard about the server issues with the Konami ID website for the Metal Gear Online Beta. Basically, you need to sign up to use the Konami tracking system for stats and collecting other data for the beta test. Problem is, the servers have been getting so hammered, the site has been up and down, making it difficult to register or login.
It took me the better part of 4 days trying to setup an account before I was finally able to get through. Even after the servers came back up, I got error messages trying to do anything on the site.
This has me very concerned about how the beta will actually work. If you can’t log in to the Konami servers to setup or connect to your account, how are you supposed to play online? The whole Komani ID debacle is just as bad as friend codes and shouldn’t even be used. If it has to be, they need to make sure those servers are up and lightning fast, which they aren’t. Once Monday comes around and everyone tries to log on and play the Beta, I’m sure it’s going to bring their servers down even further. We’ll keep you posted, but it doesn’t look good.
You might have noticed a bit of downtime the past two days here at Loot Ninja. On Wednesday, we got hit with a DDoS attack. Yeah, hackers are oh so much fun.
Yesterday, however, was a hardware issue. One of our memory chips went bad and caused the server to lock up. All is well now, so don’t fret.
To those of you sending me IM’s and emails to pay my server bills… don’t worry, that’s well taken care of.
