Closed ZephyrSterling closed 11 months ago
We are sorry that you are encountering this issue. We are currently looking into the problem and will report back on this once we find a solution.
Hi @sohailshafiiWk , despite pulling the latest changes to this repository, the issue seems to persist. I'm using Oculus Integration v56 (though I've tried 50-55 as well) and the headset is on v57, Unity v2021.3.29. None of the sample scenes run, issuing the similar warning message from OP (attached screenshot). Interestingly, when opening a scene from Oculus Integrations, say Hands Interactables, the hand tracking works fine. However, for any scene from the Movement SDK, none of the body parts track.
Is there any way I can help further isolate this issue? Last we chatted, you mentioned utilizing OculusLogGather to collect errors. If that would be of help, I'm happy to do so. When I first experienced this issue a month ago, I suspected it was the OS (v56 at the time and Oculus Integrations v55). However, it seems that despite OS and SDK updates, the Movement SDK might be the culprit in some capacity.
Hello. To make sure we understand, are these problems only being encountered over Link? Do they occur if you build and load an APK? After going through https://developer.oculus.com/documentation/unity/unity-link/#settings-for-development-over-link-and-troubleshooting-steps, does the editor render anything into the HMD over link?
Hey, so yes it renders all scenes over Air Link in the headset. However, it doesn't track any body parts. Further, it fails on every build, which is partly why I've focused on in-editor for now. Apologies for not being more specific there.
Regarding the link, in the oculus PC software there is no longer a section to toggle movement tracking in the Settings. Beyond that, I've followed all other specifications.
Please try the OculusLogGather tool as specified in https://developer.oculus.com/documentation/unity/unity-link/#link-log-gathering-from-unity-editor-and-oculusloggather-tool to gather information. Perhaps upload to Google Drive if that works.
@sohailshafiiWk , thank you for your patience and help. I uploaded the log files here
over Air Link in the headset. However, it doesn't track any body parts. Further, it fails on every build, which is partly why I've focused on in-editor for now. Apologies for not being more specific there.
Regarding the link, in the oculus PC software there is no longer a section to toggle movement tracking in the Settings. Beyond that, I've followed all other specifications.
Have you tried signing up as a developer? In case you have not, please see https://developer.oculus.com/sign-up/. Also you'll need to create an org as seen in https://developer.oculus.com/documentation/native/android/mobile-device-setup/
Hey, I already have a developer account and an organization associated with my account. I just double checked. Further, I know its not an issue with my hardware, because all apps that utilize facial tracking continue to work. Are there any other steps we can troubleshoot here? Is there a specific version of Unity and the associated SDKs that is tested and verified to work?
It turns out that the Oculus software was signed into my Oculus account instead of my Facebook account. I factory reset my Quest Pro, signed into Facebook, and then there was a mismatch between my headset account and PC software account. Thank you for helping me get to the bottom of this!
We are glad that you were able to resolve the issue. Please let us know if anything else comes up.
The original assertion failure should be mitigated in the v57 SDK available here: https://developer.oculus.com/downloads/package/unity-integration. We are closing this issue for now. Please let us know if the same error re-appears.
Hi,
I've the same issue with Unity2022.3.13f (also Unity2022.3.20f) and Unity Meta Packages v60.0.0
Got it. My link was not properly configured: https://developer.oculus.com/documentation/unity/unity-link/
Hello, we are glad that you were able to resolve the issue. If you run into any additional problems, please create a new issue with detailed information.
Hi! I have used Movement for a few days. Most of the time all the scenes worked well. But sometimes i got this error: I try to find what's wrong, and it seems that the boneid is always Invalid. But the error can be eliminated by restarting Unity and Quest link. My relevant settings:
Could you plz help me?