Oculus quest thumbstick issue

The axis values of oculus thumbstick gives a a value for a frame and then again returns 0. Same is Happening with the oculus plugin as well. ovrplayercontroller does not move with thumbstick as it returns 0 continuosly after a frame

 

If you're using 1.39, try downgrading to 1.38. https://developer.oculus.com/downloads/package/unity-integration-archive/

 

yaa i am using 1.39 will try 1.38 now and share the results

 

I am using unity 2019.2.2f1
Oculus 1.38
I am still facing the same issue, thumstick just moves the character for a frame and stops again.
following are the settings being used.

 

You may find this useful: https://developer.oculus.com/blog/tech-note-unity-settings-for-mobile-vr/

You should be doing 'single pass' not 'multi-pass'.
API level needs to be 25 now, I think.
You should be using .NET 4.0

Your settings look a bit different, but I'm using 2019.1.14

I recently put together a super-simple project to show someone how I built a scene. I will upload it to github after I get home from work tonight.

 

thanks for the details! I will try it with the suggested settings...will be waiting for your git upload

 

I've started it. I won't have all the features in tonight, nor will I have it tested on a Rift yet. But you can find it at https://github.com/Corysia/Unity-Oculus-Example

 

is this tested on quest? I have tried with the suggested settings and the thumbstick issue still persists

 

Yes, I tested it on my Quest. I did see the same problem with the thumbsticks. I needed to delete and create the AndroidManifest file twice before it behaved correctly.

Once I finish the tutorial, I will upload an apk. After that, I will look in to ensuring the Rift instructions are correct.

 

I have downloaded your project on git and it worked on quest, so should I have to remove the manifest twice to make it work!?

 

I've seen inconsistent behavior. Some projects, I have to do the delete/re-create step twice. In others, it works fine the first time. I guess it's kind of like when you have to reboot something -- it's messed up and this fixes it. Once it works, you won't need to rebuild it again. So it's one of those things I like to address early on when making the project.

What I thought was odd was when I pulled the repo down in to a new scratch directory, I had to go thru these steps again. It makes sense when you think about it because I didn't check in the Oculus Integration package. Re-adding that and setting up the project for Android probably re-creates the manifest that needs to be deleted. So, repeating the step cleans it up again.

But that doesn't explain why I have needed to do this step twice in a local project I haven't put in to source control.

 

Thanks a Lot for your inputs and help!!
I was able to setup the stuff working on my project with changes in manifest file.
Adding up this line solved the issue <uses-feature android:required="true" android:version="1" android:name="android.hardware.vr.headtracking"/> along with the settings you have suggested.

Some other findings are:
It works well with multipass as well and all the assets loaded from asset bundles will look black if we use single pass.
When we do the axis mapping in lower versions of unity i.e below 2018.3 it wont work.
I have tested the mappings with 2019 and above version and the same code worked.

Thanks a ton! for the time you have spent on this

 

It may be that setting lighting to Gamma rather than Linear and going back to single-pass will work, too. VRTK has a problem with Linear. I'll be honest, I really don't know what the difference is under the hood. It was a suggestion I picked up off of https://developer.oculus.com/blog/tech-note-unity-settings-for-mobile-vr/

But I'm sure you want to try to get it working with Single-pass. That's discussed in that article, too.