cancel
Showing results for 
Search instead for 
Did you mean: 
lembas
Founder
Founder

Problem with the L2 button

Jump to Best Response
Hy guys, Playing Destiny 2, I have a problem with the L2 button. I can no longer disable the weapon's aiming mode. Even if you don't press and hold the button, the aim mode remains engaged. This problem doesn't occur if I play from Crhome using keyboard and mouse, so I think the problem is related to the controller. After resetting the controller (as per Google's guide), the aiming mode kept turning on and off very quickly. Pressing L2 locks fixed and stays on. At the moment I have solved the problem by changing the back button configuration from the game menu. (I reversed L2 with L1 and R2 with R1). In this way, the problem no longer occurs during the game but it appears in the various menus of the navigator. A similar problem happens in FInal Fantasy XV with the R2 button while driving the Regalia. R2 is used to accelerate, but it doesn't work. I don't see any problems with Tomb rider.
1 Kudo
Best Response
codesplice
Gold Stadia Guide
Gold Stadia Guide

@lembas I've seen a few similar reports, and it does seem to be a quality control issue with the controller. I'd suggest reaching out to Stadia support to see if they can help you with a replacement:

https://support.google.com/stadia/contactflow

View Best Response in original post

Tags (1)
4 Kudos
10 Replies
codesplice
Gold Stadia Guide
Gold Stadia Guide

@lembas I've seen a few similar reports, and it does seem to be a quality control issue with the controller. I'd suggest reaching out to Stadia support to see if they can help you with a replacement:

https://support.google.com/stadia/contactflow

Tags (1)
4 Kudos
lembas
Founder
Founder

@codesplice I've contacted the stadia support by phone and they suggested me to contact the software house of the game...
I've opened a similar thread in the Bungie forum and the only answer received was: try another controller...

Well... I don't have another controller, but I tried to use the stadia controller on PC: the problem with L2 button was always there, but much less obvious (only sporadic frenzy movments of the weapon sight).

0 Kudos
codesplice
Gold Stadia Guide
Gold Stadia Guide

@lembas That still sounds like a hardware problem to me. Maybe try Stadia support again? Sometimes getting a different rep can make all the difference. 

0 Kudos
Gamer_Guide
Community Member
I just reached out via the chat last night about this issue and the rep told me that they'll need video evidence of it happening to replace the controller! I felt insulted by the idea of waiting for this random event with my video recorder on standby to record and send as proof. Why not just offer to send a refurbished one? I'd be more than happy to send the old one back to get a controller that has less of a chance of breaking permanently after the warranty expires. Thought I'd get ahead of the issue by reaching out to see what my options were and apparently there aren't any unless the controller doesn't work at all. That's the only way I could see their policy of video proof requirements working. Hopefully there's a resolution for us if it's a widespread problem. Played yesterday and today without issue so maybe it'll stay that way. Don't like having to hope that my hardware doesn't fail though.
0 Kudos
lembas
Founder
Founder

I'm not sure the problem is related to the controller.

I've this problem only with Destiny 2 and some stuff of Final Fantasy XV.

For istance, in both the Tomb Raider included in Stadia Pro Account there are no problem.

@Gamer_Guide : You don't need to stay alert with your video recorder :slightly_smiling_face:

Just press the related button for recording video on the controller when the problem occours.

I'll try to do it me too next time and then I will try to contact again the support.

0 Kudos
codesplice
Gold Stadia Guide
Gold Stadia Guide

@lembas My hunch is that different games might use different activation thresholds for converting the L2/R2 analog values (0-100) in to digital values (on or off) for things like toggling the "aim down the sights" mode.

For example, the controller might report an incorrect 5/100 reading when there isn't any physical pressure applied to the trigger. Destiny (for example) sees a value that's greater than 0 and so sets it to "on"; Tomb Raider might instead see that 5 < 50 (or whatever) so leave the input "off". 

This could explain why you're seeing different behaviors in different games. Just a guess though. :slightly_smiling_face:

1 Kudo
lembas
Founder
Founder

OMG!

Sounds not so incredible as I thought.

But I don't understand why the controller works better playing on the PC with Chrome

0 Kudos
PelleKoolAid
Founder
Founder

I experienced the same issue with Tomb Raider ... I know the steps to bring the bell down, but the controller just keeps vibrating. The controller is not taking the commands.

Tags (1)
0 Kudos
RandomS
Stadia Player
Stadia Player

Im experiencing the same problem with dragon ball  i think it's the controller 

 

0 Kudos
JayJMis
Community Member

Same problem here with multiple games...sent Stadia email stating problem, will write back with their solution

2 Kudos