Unity Editor version: 2022.3.49
ML2 OS version: 1.10.0
Unity SDK version: Unity Package 2.4.0
Host OS: Windows 11
Created a basic grab interactable app in Unity but if I exit to Home and then resume the display glitches out as shown:
WARNING: Video contains a glitch that results in rapid flashing lights... photosensitivity warning.
https://www.youtube.com/watch?v=410P34zBpEw
Please advise if this is a bug or on how to fix. Also the colors on the YT tutorial seem to change randomly if I move the cube around quickly, any ideas why and how to fix?
The tutorial: https://www.youtube.com/watch?v=QnYDCRlnf0c
1 Like
It looks like a party simulator 
Are you able to reproduce this in the Unity Example Project?
We are tracking an issue that might be related to do this. Is your depth submission mode set to 16bit?
Regarding the multiple hover events, did you assign the color changes to the first hover and last hover events? Did you use the ML Rig from the samples or are you using the generic XR Rig from XRI.
Some updates:
10/6/24
Previous project used Universal 3D Project Template, tried Mixed Reality Project Template today. This seems to resolve the strobing issue to a certain extent, however it results in the following issues:
-
First resume- normal functions
-
Second resume - object position seems a bit unstable when I move around
-
Third and onwards- a bit more unstable, some screen tearing too
-
When I tried to record a video of this, the strobing issue reoccurs. Seems to happen consistently if the video capture is running when I resume the app
10/7/24
Tried testing the Unity Example Project, ran into several issues (note - using Unity 2022.3.49f1):
- Controller doesn't seem to connect/influence the pointer at all, neither do my hands so can't do anything in the app.
- Resuming the program initially works fine for the first few times but at ~5 times it totally crashes everything on the headset... one time it forced it to shutdown... second time everything went black and if I take off and put back on the headset I get a strobing pin entry which also sometimes appears red or magenta tinted that I can't interact with at all. Have to force shutdown device to fix.
Even weirder... I just tried to capture this using the ML Hub 3... the strobing issue occurs in the capture but not in the headset and the Example Project no longer crashes while capturing. For my cube app I see the cube strobing, not all the crazy pixels seen by the capture.
Where is this "depth submission mode" setting?
I used the "Hover Entered" and "Hover Exited" events not first hover and last hover as instructed in the tutorial, though I did later test with those and they did not fix the issue. Using ML Rig.
Video of the behavior: (would put a link here but it says I can't send links to this host? - Why was my last reply flagged?) Guess I'll just put the last part.
watch?v=-CeyvrR_LP8
@blenderenderer sorry about that, our spam filter is a little more aggressive with new users. I just approved the post.
Regarding the hover inputs, I'm not sure what might be causing a difference between the input events. I was not able to reproduce this issue myself. Here is the written tutorial that the video was based off of. (Note the ML Rig Prefab is different in this tutorial because it uses MLSDK )
The Depth Submission setting is under the XR Plug-in Management settings under OpenXR.
Although, I was able to reproduce the crash and blinking on the latest Unity Editor version which I have reported the bug to our Unity SDK team. Thank you for letting us know.
In the meantime: please use the 2022.3.11f1 Unity Editor and make sure that the depth submission is set to 16
Set the depth submission to 16 and that seemed to fix the tracking issues I had on the Mixed Reality project template one at least. So seems like the best path for 2022.349f1 is to use the Mixed Reality project template instead of Universal 3D and set the depth submission to 16. Might want to add that depth submission setting as a part of the ML Project Setup Tool unity asset so it's set to 16 automatically.
Will try with 20223.11f1 to see if I can get the example project working... I previously tried using older versions of the 2022.3 editor but got UnityException: Android SDK is missing build-tools. Android SDK Build-tools component is not found. Make sure all tools are installed in the SDK manager. error which prevented me from building, hence why I updated to the latest which seemed to fix this issue. Yes, I had all of the following components installed:
- Android Build Support
- Android SDK & NDK Tools
- OpenJDK
Updating to the latest stable 2022.3 editor solved it, will see if it occurs on 2022.3.11f1.
1 Like
So had to do the following to get 2022.3.11 to even build the Unity Example Project:
-
Download the engine without any Android modules, seems they install incorrectly if installed with the initial editor (Unity does not find the SDK).
-
Add the android modules after the editor installs.
-
Get error on build saying SDK does not support Android 29, navigate to cmdline-tools folder in the SDK path and use an Admin cmdline to run sdkmanager "platforms;android-29"
-
Get error saying SDK path is not writable... change permissions of that path so no longer Read Only
-
App finally builds and runs, seems stable after several exit to home+resume however I still have the issue where the controller and hand tracking do nothing in the app so I can't select a scene or do anything in the app. Would appreciate help getting that working since the example app looks pretty handy.
You may need to reach out on the Unity Forum for help with that error in the Unity Editor. Have you tried running the command that it lists?
Regarding the input :
Not sure what would cause your prefab to break 
given that other error, I wonder if your hard drive has enough storage or permissions to write certain files. It looks like maybe the Unity Android Tools and MLSDK example are not loading correctly. You may want to test building on another computer if possible.
In the meantime:
Can you verify that the OpenXR controller profile is included in the Open XR settings under the XR Plug-in Management project settings ?
If the input is specified, can you select the controller under the XR Rig and verify in the inspector that all of the input actions are specified.
Whoops, to be clear I resolved the errors and got the app to run by doing steps 1-5, by 3) I meant I got the error message "SDK does not support Android 29" and figured out how to solve it by running that command. Same with 4) I resolved the error by changing the SDK path permissions. Just documenting everything I had to do to get a successful build here in case others are trying to get this working in 2022.3.11 as well and running into similar issues.
I have 116GB remaining and resolved the permission error by simply changing the permissions of the path... note none of these issues (except 5) arise in 2022.3.49, only when I use older versions of Unity.
The ML Controller Interaction Profile is loaded here:
These are the actions assigned in the XR Controller component of the Controller under the ML Rig (using a fresh Unity Example Project 2.4.0 installed from ML Hub 3):
However as you can see here the pointer does not align with the controller rather it stays stuck in place pointed at the top of the menu:
Does your scene include an Input Action Manager? It might be located on the top most transform. Can you verify that it is present and that the Magic Leap Input action asset is being enabled ?
Alternatively you may want to try redownloading the examples as something might have unlinked when you were resolving the issues you mentioned above.
Thank you for describing your process in the thread. We haven’t had anyone run into this issue yet so documenting the troubleshooting steps is very helpful 
Yeah I was concerned about that too! I did a redownload right before my last post, completely deleting the /unity folder and reinstalling the Unity Examples and Unity Package from ML Hub 3, hence my statement "using a fresh Unity Example Project 2.4.0 installed from ML Hub 3." No modifications were made to the project other than changing the build setting to Android.
As for the Input Action Manager seems like it's a component on the ML Rig:
Hmm I am not sure what could be going on. I’m assuming the controller works in the home menu. It might be something with the build environment.
Do you mind sharing an apk with me to verify that it’s a build issue and not a device issue?
Yes, the controller works fine in the home menu and even in other Unity apps I made, some of the previous videos I posted on this thread can attest to that.
Sure, here's the .apk: MLExamples.apk - Google Drive
Interestingly enough, your apk works as expected on my device 
Does your home menu shift between close / far mode when you pick up the controller or do you see the menu following you pretty close at all times?
You may want to try re-updating your device to the latest version. You can try factory data resetting the device and re-installing the OS update.
If that doesn't work, or if you want to skip to skip that step, you may need to updating your device following the upgrade path documented here.
- Rollback device to 1.1.0 (factory data reset enabled)
- Update 1.1.0 to 1.2.0 (factory data reset disabled)
- Update 1.2.0 to 1.5.0 (factory data reset disabled)
- Update 1.5.0 to 1.9.0 (factory data reset disabled)
A future version of MLHub will help guide users through the update paths.
My mistake, I was using the 1.9.0 OS version instead
Ah, I'm currently following that update path, was going to ask whether I should go from 1.9.0 to 1.10.0? Since I was working on 1.10.0.
You could go to 1.9.0 for now ( I can verify that the controller works there) - I have reached out to the team regarding the controller issue when building the 2.4.0 examples and running 1.10.0
