05-30-2022 04:01 PM
Hand controls work as expected inside the native Quest 2 environment, but as soon as I connect to my pc via airlink it stops functioning, preventing me from playing a lot of games.
Pressing the buttons works as expected, just none of the capacitive functionality.
Everything was working fine just a week or so ago. I replaced the batteries in the controllers with fresh ones and unplugged any other controller devices connected to the pc just in case.
05-30-2022 05:37 PM
Hi there! We understand that you are having issues with your hand controls when connected to your Airlink. There's no fun in having the most essential part of your device not working properly. Can we have you try the following troubleshooting steps:
Let us know if this was helpful or not, and we will continue to troubleshoot with you.
05-30-2022 08:06 PM
I tried all of the above, and the problem still persists.
I have noticed that everything works fine while in steam vr and apps ran through it while using airlink, so the problem is exclusive to the oculus home environment and applications ran through the oculus app.
05-31-2022 11:08 AM
Hi DaggerJaydo! Thank you for trying out those troubleshooting steps. Since you're mainly having issues with the Oculus App, we'll have you try running a repair.
To Run a repair:
If you continue to have issues, please feel free to reach out and make a ticket here, with Meta Support.
06-04-2022 02:08 AM - edited 06-04-2022 04:06 AM
Same issue since update with Meta branding. Capacative finger pointing etc works as intended in native Quest 2 app and Steam VR. Finger pointing does not work with the Oculus PC application. I have tried Cable Link and Air Link. Software install repair as per above and nothing has changed.
EDIT - I resolved by manually checking software version on the Quest 2 headset. There was an update available. I went from v38 to v40 and this resolved the issue.
Please advise.
Please note that we will be upgrading the community on July 9, 2025. The community will be down for a few hours while we perform this upgrade. For more information, please see Community Upgrade & Downtime