I still have this error where every few launches the controller will not work in Unity (using your example project). It just starts frozen in its last position, I can see the ray but it no longer tracks. Exit Unity and the controller works fine on the menus, back into unity still jammed. Only restarting the whole headset brings it back. Once powering off the controller seemed to work, but I can’t reproduce that. How can I get to the bottom of this? Is there some kind of process I can kill instead of restarting? Can I do something to fix this before I demo to our users?
Thank you
Unity Editor version:
ML2 OS version:
Unity SDK version:
Host OS: (Windows/MacOS)
Error messages from logs (syntax-highlighting is supported via Markdown):
Any ideas on this ML support? It’s going to block shipment for us.
Thank you.
In the Unity Input Profiles in your XR Settings, can you try disabling the Hand Interaction profile? Do you get any errors or warnings in the logs. Are you building the Example project exactly as it comes from the Magic Leap Hub?
Yes building just your example project and still see the issue about 3-4 times a day. Sometimes randomly while I’m working sometimes when I come back from lunch say and pick it up after being idle for a while. The tracker always works on regular menus just broken in unity and restarting the unity app does not fix it. Are you talking about disabling hand tracking subsystem in openxr? I can try it but we do plan on using hand tracking for occlusion.