Hello everyone,
There are some post related with this issues like:
https://community.stadia.com/t5/The-Stadia-Controller/L2-button-triggers-far-too-easy/m-p/8978#M377
BUT I decided to create a new one because I am not sure if this problem is becoming from our controller or a game set-up. Let me explain. I face this problem only in Mortal Kombat 11. Others game like NBA2K20 or RDR runs perfect. That's make sense? Should I reach Google support for a re-found or a new Stadia controller?
Thanks for your support.
I've experienced the same problem today, after playing MK11 for 3 months already.
I believe to know the reason though...
In my case only the Founders Edition Controller has an issue with the R2 trigger. Now MK11 detects even the slightest analog inputs and has no dead zone for triggers and sticks. So as soon as you move them by 1% the input is detected and the command will be executed.
The problem are the controllers themselves... after useing the Founders Edition Controller for only 3 months, the R2 trigger doesn't fully retract again after pressing it. So it's constantly stuck at like 2-5% input and this causes the MK11 menus to go wild sometimes... ![]()
If you have GRID and want to check out if you have the same problem... go to the control settings in this game. It shows you exactly by how many % the anolog triggers or sticks are out of their standard position. In my case it's up to 10% for R2. Only if i push the back of the button upwards it goes back to 0% = no input.
I hope this clarifies the situation. No game bug, just a bad built quality on the controllers.
My boyfriend and me couldn't figure this issue out with our controllers when playing Mortal Kombat 11. We're using a Founder's controller and a white one and both work fine so far.
Therefore I think it might be worth for you to reach out the Google support and figure out if you can either do some troubleshooting steps or need a replacement.
I've experienced the same problem today, after playing MK11 for 3 months already.
I believe to know the reason though...
In my case only the Founders Edition Controller has an issue with the R2 trigger. Now MK11 detects even the slightest analog inputs and has no dead zone for triggers and sticks. So as soon as you move them by 1% the input is detected and the command will be executed.
The problem are the controllers themselves... after useing the Founders Edition Controller for only 3 months, the R2 trigger doesn't fully retract again after pressing it. So it's constantly stuck at like 2-5% input and this causes the MK11 menus to go wild sometimes... ![]()
If you have GRID and want to check out if you have the same problem... go to the control settings in this game. It shows you exactly by how many % the anolog triggers or sticks are out of their standard position. In my case it's up to 10% for R2. Only if i push the back of the button upwards it goes back to 0% = no input.
I hope this clarifies the situation. No game bug, just a bad built quality on the controllers.
I have an issue with my controller when playing grid the R2 button works initially then somehow the input stops when I’m holding it down, so I start decelerating even though I should be going full speed. Haven’t contactEd Stadia support team yet but will do as I suspect it needs to be replaced.... my brother in law just had one replaced for an R2 issue and it was some laborious process so not looking forward to it....!
The triggers are super sensitive, when hovering finger over Left one as ADS in a shooting game it is so easy to accidentally ADS frequently, a little deadzone would fix it.
Of course the return is tedious. They will give you a refund because they are required by law.
They have hundreds of thousands of controllers in warehouses because Stadia users are very few compared to forecasts.
They have had mass returns from the controller, so when a problem becomes habitual, from the noble zone they think that their connections are too permissive and that they are harder before changing a product, they do not want losses.
They are aware of the problem and are aware that a new eventual controller will fail again, because it is a manufacturing problem.
Surely it is the controller that gives most of the errors that Stadia now has such as latency, audio problems and disconnections.
For this reason I have not made a change and still without buying a new one until it becomes completely dysfunctional.
When necessary, I see what I do. Nintendo suffered this with the Joy-Con
Where you manufactured the controller? Google?