Skip to main content
Surfingpuppy
Participant
November 20, 2023
Solved

Quest 3 controller : Trigger sensor is very sensitive since firmware update 1.9.2

Hello

I had this problem happen to me since the Quest 3 touch plus controller firmware update to 1.9.2 I did on November 12. Before that, I didn't notice a problem with them.

Since the update the presence of my fingers are not tracked properly on the trigger especially if I move my finger up or down across the button. It will think I am not touching the trigger while my finger is still resting on it. I have to almost be perfectly centered on the button and try my best not to move it while doing my hand gestures or it will think my finger is not touching it.

 

I already contacted the support team and they sent me replacement controllers with the same issue.

I hope Meta is reading this so they can notice the regression since 1.9.2 and make an update soon.

    TheAntiSocializer
    TheAntiSocializerAnswer
    Honored Contributor
    December 13, 2023

    I managed to get an update from our internal team, and it looks like the best course of action here would be to submit a bug report so that they can get a more in-depth look. Along with that, I'd suggest testing out the below troubleshooting:

    1. Clean the controller
      • You can also use compressed air to remove any debris inside the controller
    2. Remove any unsupported third-party accessories that may affect button movement or controller detection (such as controller covers, controller attachments, etc.) 
    3. Remove the battery from the controller for at least 30 seconds
    4. Unpair and pair again the controller to the headset

    Apart from this, I'd recommend keeping in touch with the support team. If you're having some trouble with the email team, you can always reach out to MetaStoreHelp through PM for them to look into your support ticket. 

    Sometimes it's okay to be a little Bing Chilling
    View in thread

    78 replies

    Show previous replies
    QuickMind
    Participant
    December 18, 2023

    This a strange bug to not have been fixed before you release a hand tracking VR/MR app showcasing the hand tracking feature called "First Hand". I suggest you work on getting this fixed ASAP as this is confirmed to be a widespread issue according to the replies on Reddit, along with the other open post for the issue with the Pro touch controller experiencing the same thing that I have replied on. The weeks of no communication is confusing at best.

      SukiYuki22
      New Participant
      December 18, 2023

      Hi everyone. Has anyone tried disabling "Movement Tracking - Hand Tracking" from Settings and re-enabling it?

      Meta Quest 3: How to Activate Hand Tracking - https://www.youtube.com/watch?v=jiEyeVnXPc8

      Edit: Well, it actually did nothing :S

       

       

        SurfingpuppyAuthor
        Participant
        December 19, 2023

        Hi again,

        First of all, i'm happy to know i'm not the only one finding this ridiculous coming from a company like that.

        As stated by everyone, this is very embarrassing for Meta that they still haven't fixed their controller problems. I guess I'll enter a bug report since apparently no one can help here.

         

        Just so you know, i got my whole Quest 3 kit replaced and when I first booted the new headset and tested the remote before the Controller updated. It was perfectly working, no random finger tracking happening on the trigger (AKA no 3d finger trying to track where the tip is, still don't know what's the point of this. IT'S NOT USEFUL AND IT'S BROKEN)

         

        Right after the forced update, that "finger tip tracking" appeared and all the exact same problems were back.

         

        Can this be taken seriously please ?

        Can't your engineer see its related to the controller update like I said since the first post of this thread ? Just remove that finger tracking thing !

        I'm not convinced any efforts are being put into this. How can we know this problem is just not put into a backlog of issue to be addressed later instead of now? 

          SurfingpuppyAuthor
          Participant
          December 19, 2023

          Also, to specify, you're troubleshooting are so basics it's shameful that this is the response we get after A MONTH of waiting.

          I've already tried all of those, and this happens with 3 brand new pair of controllers + the quest pro controllers i tried.

            SurfingpuppyAuthor
            Participant
            December 20, 2023

            TheAntiSocializer FYI, this is something the people looking into this issue needs to know and check. I hope you can provide this information to the engineering team:

             

            The question that keeps rummaging in my mind and that I keep asking is what's the point of the tracking of the tip of the finger on the trigger (the 3d model trying to imitate the finger bending) ?

            Because I'm convinced this feature is what makes the sensor act unreliably. Its introduced in the controller update that is forced when we setup a new headset.

            I can tell you because I got a replacement headset yesterday and the first thing i checked is the tracking of the sensor on the controllers when I booted it the first time. To repeat myself, they were completely fine before the update, I tested it a lot. The 3d model of the hand did not have that finger bending feature at all and it was perfectly tracking my index on the trigger. it would only lift up and go back on the trigger, no random bending or anything weird like that on the 3d hand. Just like the PCVR 3d model does when we're linked.

            Then the update of the controller happened. Immediately, the 3d model's index started bending into a close motion and became unreliable. It would randomly bend and lift off the trigger when i would just slide my finger across the button or move it off the center a little bit. Just to tell you, my 3 years old Rift S as way better tracking then the Quest 3 since that update. I've included a picture to showcase this.

             

            I'm baffled because the regression here seems easy to notice. Ask your engineers to compare the tracking of the trigger sensor before and after the update. I don't know what more other information you must need from us to make them understand.

             

            The whole Update of the controller does not have to be reverted, we are just asking for trigger sensor to be to how it was before that update. I don't understand what could even take so long when the source of the problem is so apparent. Hell, if you even put an option to deactivate it or a public test channel to test how the controllers are without that feature I'll test it and offer all the feedback you want. I'm sure everyone involved would appreciate the cooperation too.

             

            Your help is appreciated in this TheAntiSocializer, i know you're just relaying the messages for us but, like i said, I'm not sure the engineering team is taking this seriously so thank you in advance for relaying all this information.

            Cheers,

              TheAntiSocializer
              TheAntiSocializer
              Honored Contributor
              December 21, 2023

              Thanks for the photo and for letting me know this, I'll go ahead and pass it along to them.

              Sometimes it's okay to be a little Bing Chilling
                TheAntiSocializer
                TheAntiSocializer
                Honored Contributor
                December 21, 2023

                [NOT A SOLUTION] - Just marking this as the solution for visibility, this is not resolved.

                Hey everyone, thanks for reaching back out. I'd be happy to get this re-flagged with our internal team for them to get a bit of a further review. 

                To make sure I have the most up to date information after the update, could everyone please let me know all of the following:

                1. What's the full version of your headset? (60.0.0.####### or likewise)
                  1. Quick Settings > System > Software Update
                2. What's the current firmware version of your controllers?
                3. What version is your Meta Quest app running?
                4. Are you enrolled in the Quest PTC?
                5. Any potential workarounds found?
                6. What all has been attempted already? 

                This will be a big help for getting some eyes on this. 

                Sometimes it's okay to be a little Bing Chilling
                  Zythoxic
                  Zythoxic
                  Participant
                  December 24, 2023

                  I'm gonna drop into this conversation as well, since it felt like this exact issue has been getting worse after every update to the point where it's almost spazzing out now when i just normally rest my finger on the button and even try to touch as much mass of the button as possible and it still sometimes just doesn't recognize it's actually on it...
                  (It was fine with the firmware on release, but the next update the issue started)

                  1. Full Headset version: 60.0.0.193.366.548441753
                  2. Controller Firmware: 1.11.1 
                  3. Meta Quest App version: 60.0.0.162.352 (60.0.0.162.352 (same issue is happening with Virtual Desktop etc.)
                  4. Not in PTC
                  5. No workaround found
                  6. Tried to clean the buttons, tried to re-pair the controllers to the headset, tried to do a factory reset, tried changing the tracking frequency, nothing helped...

                  Would be great to have this issue fixed as soon as possible since it's quite annoying having the hand just constantly spazz between a resting position and the peace sign...

                    Flyinryan145
                    Participant
                    December 25, 2023

                    Thank goodness I've found more people with this issue...

                      S2Nsplatmaster
                      New Participant
                      January 1, 2024

                      Yeah I'm having the same problem. I was starting to think it was something to do with the trigger.

                        QuickMind
                        Participant
                        January 3, 2024

                        At this point after two more weeks of silence again from TheAntiSocializer, It seems to me that Meta has no intention of fixing this issue. I am concerned that there is a greater problem with the hardware itself and that they want to keep replying just to appease, along with keeping this under wraps as much as possible. They don't want either to receive a class action lawsuit or have to update and replace all the hardware out there causing this issue. It's possible there is a batch of early manufactured defective units that either fail or don't do well with the firmware/software released.

                        Show more replies
                        Terms & ConditionsAccessibility statement