05-30-202309:58 AM - last edited on 03-16-202403:13 PM by Lowkey.Just.a.Bot
It detect to "touching" the trigger when my index finger just close to the trigger and not touch it.
When I push the trigger then leave, it don't leave immediately in unless I fully open my hand to keep my index finger really far away from trigger, it makes me hard to switch my gesture from fist/thumb to point/gun.
Is this caused by touch pro's index finger tracking?Can I turn this this feature off?I just want my trigger touch response works like quest2 controller works.
Please remove solved checkmark. This issue is still present 3 months after the original post date and nothing done has been effective in trying to resolve it.
Hey, just wanted to provide some clarification here! On the Forums, we typically will mark something as a solution for maximum visibility as it brings that response to the top of the thread. While it might not be a "solution" per se, for this issue in particular to be resolved, users will need to reach out to support, so we want to make sure everyone sees and knows that.
I know it isn't the most ideal way for this information to be relayed, but it's the best we have! If you're still having issues with your Pro controllers, definitely either reach out to @MetaQuestSupport in a private message, or open a support ticket yourself here.
That isn't a solution. And again, has done a disservice to EVERYONE ELSE waiting here for a response.
The issue isn't as simple as "contact support for an RMA request" when the issue is prevalent in SO MANY, if not ALL controllers.
All this does is give us all the run-around, and anyone else looking for that information for a "fix" (which doesn't seem to be any), are left in the dark.
We are ALL literally waiting for someone at quest to come up with a fix or find a solution to these buggy $400 controllers.
Telling us all to private message support or opening a support ticket has offered ZERO help to the issue, besides tricking some of us to file RMA requests only to have the same issue be happening.
Having the same issue with my Quest Pro triggers. I've done reboots on the controllers, use contact cleaner, but rarely they will "detect" my finger on it even tho it's not on it. Mashing on the trigger sometimes fixes it, but then goes back to being stuck eventually.
Software tweaking would be good to have on a PRO product!
This is what i am talking about. This should NOT be an issue for 300$ controllers. It's insanely frustrating to see this is still somehow NOT fixed by Meta and honestly unacceptable for the price point.
Looks like that information doesn't work either, because as you can see, users in this thread did proceed with that, and did a useless RMA, which the RMA STILL served to be the same issue, as (surprise surprise), it's a SOFTWARE ISSUE.
Maybe, again, you should get an engineer in here and discuss the issues and find a fix instead of marking information as a solution that does nothing but cause more problems, because now users are going to be sending out RMA's and getting the same problems in return.
The problem is that nobody (not even Meta) has been able to provide a viable solution. All Meta will do is replace your controllers with another set that has the same issue or blame your headset for being faulty when it is clear that this is happening to everyone. So PLEASE, will somebody from Meta post on here and tell us what is causing the issue and the course of correction? We need communication and transparency. Not some support agent telling us to send a private message only to get nowhere. And PLEASE uncheck this thread as solved because contacting support hasn't helped anyone.
Did this answer your question? If it didn’t, use our search to find other topics or create your own and other members of the community will help out.
If you need an agent to help with your Meta device, please contact our store support team here.
Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.
