|
|
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Banjo Hero
BurgezzE.T.F
Orion Empire
66
   |
Posted - 2013.03.30 15:44:00 -
[1] - Quote
I thought the [L1] = Neocom one was a software bug, but I'm not so sure anymore; since performing the below-linked fix, I don't think I've seen this once. Of course, this might just be me not really noting the occurence of it, or might be that it's been, if not fixed outright, "partly fixed" in some way that reduced its frequency. But, I do think that it is probably the same issue, only instead of [up], it's sending [start]. Whatever. Moving on...
The thing where [L3] triggers a D-pad (or other) button is usually a result of the connection between the controller's board and the ribbon cable from the buttons themselves being wonky. You press [L3] or [R3], and it shifts the board a bit, and the connection on one or more of the contacts breaks and connects again, and the controller sends the wrong signals to the PS3.
This might help you fix it.
The problem can also be triggered by gripping the controller tightly, or twisting it a bit between your hands, (this is why some people have noticed that, e.g. "it always seems to happen when I'm getting shot at") and will get worse with time. I had one that would just send all sorts of garbage phantom presses of the D-pad, [X], [circle] etc buttons, even the PS button, JUST FROM PICKING IT UP! 
I did pretty much exactly what the guy in the video shows, and that controller is now as good as new.
I hope this helps. Good luck! |
Banjo Hero
BurgezzE.T.F
Orion Empire
71
|
Posted - 2013.03.30 22:55:00 -
[2] - Quote
Banjo Hero wrote:I thought the [L1] = Neocom one was a software bug, but I'm not so sure anymore; since performing the below-linked fix, I don't think I've seen this once. [. . .] But, I do think that it is probably the same issue, only instead of [up], it's sending [start].
[. . .]
I hope this helps. Good luck!
Oooo-kay. So, this part is me lying, apparently. 
I was playing earlier this afternoon, and got my ass killed because of the player list popping up (apparently I need to fix my newer controller, too. sheesh.) and had one or two other little indications of the same phantom-button-press thing. So I shut that controller off, and grab the older one, which I fixed a few weeks or maybe a month ago as in the video I linked, and keep playing.
I think it was in the next game, I got the [L1] Neocom bug. So, yeah, I'm calling bullshit on myself. :P That's totally a real software bug. My apologies for spreading scurrilous lies.
The player list or OMS menu thing really is from this poor design aspect of the DS3 controller, though.
The "hope it helps, good luck" part was sincere.
Oh, and I think JJ's onto something ^ there, about the control sensitivity. Completely making up numbers, if Dust is registering the button-press at 1% when most other games have a threshold of 10% or something, it could explain how the controller could be at fault when the behavior isn't seen in other games. |
Banjo Hero
BurgezzE.T.F
Orion Empire
71
|
Posted - 2013.03.30 23:11:00 -
[3] - Quote
gbghg wrote:yeah i've had this too, normally when i'm running for cover
Exactly, my unpronouncable friend! Y'see, when you're hauling clone-ass to get out of the way of that HMG or whatever, you're more likely to be tense and gripping your controller very tightly, and it can shift the bits inside a little, enough to cause this obnoxious behavior. I really suggest at least looking at that video. It's not a particularly difficult "surgery" to perform, and it honestly did help me with a completely unusable DualShock3.
[shrug]
I figure that five minutes and couple of inches of e-tape saved me $50. |
|
|
| |
|