@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:
@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:
@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).
@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.
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 ![]()
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.
@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. ![]()
OMG!
Sounds not so incredible as I thought.
But I don't understand why the controller works better playing on the PC with Chrome
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.
Im experiencing the same problem with dragon ball i think it's the controller
Same problem here with multiple games...sent Stadia email stating problem, will write back with their solution