localavatar hands not appearing in new oculus integration update

The AvatarGrab sample problem was a missing Controller Shader from the LocalAvatarWithGrab prefab:

This shader is set to OvrAvatar/AvatarSurfaceShaderPBSV2 in the LocalAvatar prefab so setting that on the LocalAvatarWithGrab prefab fixes the problem where the missing shader makes Unity regenerate part of the skinned mesh constantly which causes the slowdown and tracking problems:

I'd be interested to see if you can get the LocalAvatarWithGrab sample to work in your example code now.

I am running into this issue, but not with Avatars. I'm using 2019.1.13f1 and have tried 1.38, 1.39 and 1.40 and in none of them do my Oculus controllers show up. It's pretty clear my controllers are tracking properly, since I have visible on pointer enter effects that give away where the controllers are pointing and they show up against the guardian boundary, but none of the GameObjects and Components attached to the HandAnchors are appearing. I have an updated manifest with <uses-feature android:name="android.hardware.vr.headtracking" android:version="1" android:required="true" /> for the Oculus 1.38/1.39? changes to run Go apps on quest and I have added an app ID and neither of these solutions are working for me -- I am just using a controller mesh and a line renderer. I'm using LWRP, but I've upgraded all materials that I'm using to LWRP ones.  Any ideas on how to fix this?

Hello,

I got the issue too.
As soon as you add the "LocalAvatar" prefab to the Unity scene, if you build and launch the application on your Quest and press any button on the controller, the app crash.

Even the "LocalAvatar" sample scene provide by Oculus does not work. I have already tried to delete and recreate an AndroidManifest with the Oculus tool but nothing works...

I use Unity 2017.4.31f1 and I got this issue with Oculus Integration v1.39 and v1.40 too.

@NinjaGG  Is there any solution for this ?

Running unity 2019.2.6f1 v1.40, i will see if it works for me tomorrow, it is really weird how bad the oculus integration is for how much they enforce even using it... i've literally been busy the entire week just trying to port stuff over from steamVR since we want a oculus quest version...

so it doesn't work for me either is the short story, couldn't get it fixed in a reasonable amount of time...

I think almost everyone has reported these bugs; still waiting for them to fix it ?

UP

How do I report this bug?

AGTDigital said:

Indeed @Corysia , in your project we can see the hands, thank you for your investment by the way, except as you say in the description of your project, it's on Unity 2019.1.4f1.

Yes, I didn't test it with older versions of Unity and I'm reluctant to spend the time on Alpha or Beta versions, too.

It's only my opinion, but I doubt Oculus is going to go back and test in 2017 and probably not even 2018.  If they do, I'd only expect they would look at the LTS releases.  Yet, they clearly state that it's compatible with 2017.4.11 or higher.  Either they need to actually test it, or change what they say it's compatible with.