Skip to main content
Anonymous
August 2, 2019

Why Does My Touch Controller Script Not Work in the Quest?

I use Unity and created a C sharp script to control first person camera movement using the Oculus Touch controllers.  It works fine in my Rift (Unity and exe builds) but doesn't work in a scene I sideloaded into my Quest.  It works in the Unity project from which I made the Android build for the Quest, but not in the Quest.  It doesn't look like Oculus has changed the Touch input mapping (Button.One is still Button.One, etc.).  Can anyone explain what's going on?

6 replies

EstebanGallardo
New Participant
August 3, 2019
Same problem here. All the apps I've developed the input stopped working all together. It was a really fun surprise to get just when I was going to have some holidays. Thanks for the Gift, Oculus  :(
colinlove1
Participant
August 4, 2019
Try Oculus menu -> Tools -> create store-compatible manifest.
I agree its an awful surprise. I was about to take my quest out to demo to some friends and now everythings borked.
Anonymous
August 5, 2019
Unfortunately, creating a store-compatible manifest didn't solve the problem.  I've submitted a support ticket to Oculus.
Anonymous
August 7, 2019
Oculus tech support recommended the same solution:  clicking on Oculus -> Tools -> Create store-compatible AndroidManifest.xml.  So I tried it again and it worked!
kojack
kojack
Honored Contributor
August 8, 2019
This is related to support for Go games on the Quest that changed recently. If you don't have a Quest app set up right (the manifest thing above) then the Quest will think its a Go app and will drop down to Go controller level support instead of Touch.
Author: Oculus Monitor , Auto Oculus Touch , Forum Dark Mode , Phantom Touch Remover , X-Plane Fixer Hardware: Threadripper 1950x, MSI Gaming Trio 2080TI, Asrock X399 Taich Headsets: Wrap 1200VR, DK1, DK2, CV1, Rift-S, GearVR, Go, Quest, Quest 2, Reverb G2, Quest 3
Anonymous
August 8, 2019
Thanks.  In light of kojack's comment it seems at least possible that the reason the manifest thing worked the second time but not the first is that I think between the two attempts I changed the Element 0 setting in the OVR camera rig's OVR Manager to "Quest" from "Gear VR or Go".
Terms & ConditionsAccessibility statement