10 réponses à ce sujet

[Dr_Rent]

Well, I just have to report what may be the strangest bug I've ever encountered in a console game...a bug which causes 360 wireless controllers to disconnect. I'm not even sure how this is possible, but...here's the description:

I've played through the game just fine so far. Sure, I've had the occasional controller disconnect, but every time I've attributed it to low batteries. I've gotten pretty far into the game, past Horizon, and I'm working on loyalty missions at the moment. This bug I've only encountered on Jack's loyalty mission. Basically, every time I enter combat, I get about two seconds before my controller disconnects. It's reliable, it's repeatable, it's crazy. I must've died to that first varren attack 5 or 6 times before I noticed that it always disconnected at exactly the same time.

Getting the obvious stuff out of the way: yes, I swapped the batteries. I had a fresh rechargeable ready to go, and when it still disconnected at the battle, I used fresh AAs. Same disconnect problem. Swapped wireless controllers twice, same problem. Turned off all nearby devices that used Bluetooth, same problem. I reloaded an old save, and I was able to play just fine for a good 20 minutes. I went back to Jack's loyalty mission, and sure enough it disconnected again at the varren attack. After saving the game just before the attack, I tried to discover if it was a timing thing, but that doesn't seem to be the case. If I charge into the attack right away, it disconnects the usual two seconds into the fight. If I dawdle, wander around, or just do nothing, no problems, but as soon as I trigger the attack I get the same two seconds before the controller disconnects.

Another strange detail: if I hold the right or left shoulder button to bring up the power wheel and pause the action, that doesn't seem to count against the two-second "timer." I can sit there indefinitely with the action paused, and the controller is happy to remain connected. When I release it to continue the battle, sure enough it disconnects.

When I reconnect, I get about another second or two before it disconnects again! And if I reconnect again, it disconnects again right away, until I die. This makes it very hard to survive even this easy first attack of the mission. Dying seems to free the controller to reconnect as normal. What started out as an awfully strange bug--a curiosity more than anything else--quickly became very frustrating as I found myself unable to get past the fight after many tries. So, yes, I repeatedly reproduced the bug about 25-30 times before finishing the battle, and as soon as I finally managed to win, I seemed to be free of the disconnect curse. Thinking it was just related to that one spot in the map, I moved on, and the controller worked as normal...but the very next fight I encountered exactly the same problem.

I'm not sure how or why, but this bug seems to be triggered by combat on this one particular mission. It's quickly becoming a game-breaking bug for me. I'd love to hear if anyone else experienced anything similar (though I'd love more for Bioware to patch it or for someone to come up with a workaround). I'm not holding my breath, though. This seems like a bug that's so strange it's easier to ignore than to try to fix...especially since I haven't found anything on Google like this problem.

[BitBasher]

Ok, here's a shot in the dark...

I had one controller that would disconnect. Long story short, it wasn't the batteries themselves, but the BATTERY PACK (that little plastic thing that holds the batteries). If you look closely at the battery pack, there's a little metal tab in it. I'm not 100% sure why it's there, but that tab MUST be pressed in firmly by another little plastic tab that's on the controller itself - it's like a switch. The battery circuit is disconnected until the battery pack is firmly plugged into the controller.

On my battery pack, the metal tab was NOT making good contact, so I was getting intermittent disconnects. SOLUTION? I stuffed a very tiny piece of paper in the hole by the metal tab so that better contact could be made. It so far has seemed to work.

Ok, with that in mind, could this be the cause of your disconnect? And why only at that particular spot in the battle?
Well, I'm wondering of in that battle if the RUMBLE pack in the controller just happens to SHAKE your controller in just the right way to lose connection? Perhaps other battles don't rattle your controller enough to disconnect.

Also, if you can, borrow another controller and try at least one DIFFERENT one. This would really help rule out if it is a game bug or if there's something fishy with just that one bad controller!

Update: Hmm, re-read your post, and you did try swapping the controllers.  Well it's possible but VERY unlikey you have two different controllers with bad battery packs.  *boggle*

Modifié par BitBasher, 03 février 2010 - 11:03 .

[Dr_Rent]

I thought I had effectively ruled out non-software issues, but of course I knew this was rather unbelievable...hell, I probably wouldn't have believed it myself if I weren't experiencing it.



Look, I tried different battery packs AND different controllers. A total of 3 battery packs (two rechargeable, one original) and 3 controllers (of varying ages...most recent only a few months old). But, look, if it were a hardware issue, the problem wouldn't happen with such regularity at predictable times. I am confident that this is a bug with the game; I have done everything I could think of to rule out any other option.

[BitBasher]

Ok, one more idea - it can't hurt. Try turning off the vibration option in the game settings (so the Xbox isn't trying to transmit a lot of rumble data to the controller). I wonder if that might help. Maybe, just maybe, all the rumble data is being corrupted (noise?) and it's causing the controller to shut off.

A few interweb searches seems to indicate you've got an isolated issue - haven't seen anyone else with this issue.

Perhaps (unfortunately) you've got some corrupted save game data.  I can never remember how to do this, or if it is safe, but did you try clearing the xbox 360 game cache?

Modifié par BitBasher, 03 février 2010 - 11:24 .

[Dr_Rent]

The vibration idea was good thinking on your part; it looks like turning it off corrects the problem. Just to reassure myself that it wasn't a hardware problem, I triple-checked everything and made sure that the pack was securely attached, shook the controller forcefully, and swapped games to check whether vibration disconnected me there. Nope, the issue seems specifically related to vibration in this one area of Mass Effect 2. I even tried firing my gun outside of battle to get the vibration to happen, and if vibration is enabled, I get disconnected. If it is not, I'm fine. Turns out I was wrong all along about the two-second timing...seems that timing just so happened to roughly coincide with when the battles began.

Well, at the very least I have my workaround. Honestly, I'm not terribly bothered by the thought of playing through this mission without vibration, but...this is still very odd! What could cause such a specific problem? I'd love for someone at Bioware to pop in and offer their insight on this problem.

Modifié par Dr_Rent, 03 février 2010 - 11:54 .

[xODD7BALLx]

This happened to me as well, and it wouldnt let me re-sync the controller to my 360, I had to shut the 360 off to fix it. I even tried connecting with a play and charge cable prior to shutdown and still wouldnt sync up.

[HiggenBoom]

Same here! I've also tried 2 different controllers, and when i turn vibration off the controllers work perfectly. Except, in my situation It only started happening when I first fought the collectors, I can even turn the vibration on in the middle of a fight and then roughly 3 seconds later it will get disconnected. I guess, its from a corrupted vibration signal? Oh, and I just joined today to add to this conversation, I googled "Mass Effect 2 controller disconnect" and it led me here. I guess i just got lucky that this happened to someone else 15 days ago and you posted a quick solution. Still, its going to suck playing without vibration. =(

[HiggenBoom]

Just noticed something, all of the last played dates on my saves, say 22/11/2005. I don't know if this is related,but I remember, you mentioning corrupted game saves.

[ElementalStorm]

 From what i tried, i fear that is just an hardware problem not related to some particular broken controller, but every controller.

I just tried to do this: turn on your controller, start the game, and then bump it on a table (or everywhere it's hard enough) using the bottom. 

What I see, is that the controller ALWAYS turn off.

It seems to be an hardware problem of the controller, not a problem related to the game, alas...

I'm trying to figure out what is EXACTLY the part that fail to mantain the contact, let's see f I find out.

[Shockwave81]

HiggenBoom wrote...

Just noticed something, all of the last played dates on my saves, say 22/11/2005. I don't know if this is related,but I remember, you mentioning corrupted game saves.

OK, so I'm a bit of a necromancer as well, but I've noticed this on a couple of my save games as well recently.  In addition to this, my characters don't move as smoothly as they once did - if I try to turn left when running, my Sheps seem to move in a really choppy way.  I've also noticed major frame rate dips in LoTSB.

I've been playing the game since it was released, but the problems have only started in the last week or two. 

Weird. 

[joshuam168]

I have this same problem when playing Mass effect 1. every time I am in the mako and a rocket hits me or I fire a rocket my xbox contoller will disconnect. when i reconnect it it will shut off again. I found the 2nd time that if I hit the guide button it wont shut off.