#magicleap2 — Public Fediverse posts

I just blogged: Cross-platform spatial QR code tracking for #HoloLens2 and #MagicLeap2 with a #RealityCollective #ServiceFramework Service, part 1 https://localjoost.github.io/Cross-platform-spatial-QR-code-tracking-for-HoloLens-2-and-Magic-Leap-2-with-a-ServiceFramework-Service,-part-1/ #XR #Crossplatform #MixedReality #AR

Two weeks ago I released my #MRTK3 based app Walk the World for #HoloLens2, a week later the exact same app for #MagicLeap2. I promised to blog how I so easily and quickly got that done, and here it is: my 'recipe' for getting MRTK3-based HoloLens 2 apps to run on Magic Leap 2. https://localjoost.github.io/Making-an-MRTK3-based-HoloLens-2-app-run-on-Magic-Leap-2/ #openxr #MixedReality

#MRTK3 has a subsystem implementation for speech commands that is supported by #HoloLens2. #MagicLeap2 supports voice commands as well, if only someone had taken the trouble of making a KeywordRecognitionSubsystem implementation of it, it would have had MRTK3 support for speech commands as well.

Well, guess what - someone just did. Me. So now you can have voice commands on *both* devices using the same API, and you only need to flip a checkbox in the MRTK3 settings.

https://localjoost.github.io/An-MRTK3-KeywordRecognitionSubsystem-for-Magic-Leap-2/

When debugging problems after-the-fact, you can always use UnityPlayer.log. On #HoloLens2, that is. On other devices - for instance #MagicLeap2 - that's not available. So I wrote a little #ServiceFramework service to dump #Unity logfiles in a file for an app running on a device. While I was at it, I included filtering on keywords and log type as well.

https://localjoost.github.io/A-cross-platform-Service-Framework-service-to-write-Unity-log-messages-into-files-on-device/

For my second blogpost of the day ;) one of my more infamous and far-fetched experiments encompasses the combination of #MachineLearning combined with a Spatial Map to recognize and locate objects in 3D space, using a #YoloV8 #computervision model. This worked pretty well on #HoloLens2. I got it to work on #MagicLeap2 as well, but it was quite a rocky road. The #RealityCollective #ServiceFramework to the rescue :). Explanation, sample and full code at: https://localjoost.github.io/Running-a-YoloV8-model-on-a-Magic-Leap-2-to-recognize-objects-in-3D-space/

I wanted to see if I could run one of my more far-fetched #MRTK3 #HoloLens2 samples on #MagicLeap2. Step one was getting a Spatial Map. It was dead easy on HoloLens 2, but less so on Magic Leap 2. I managed to make it work, but there were more challenges than I had anticipated. I blogged my findings to help others avoid the same pitfalls as me.

https://localjoost.github.io/Using-a-Spatial-Mesh-with-MRTK3-on-Magic-Leap-2/

After getting my app running with #MRTK3 on #HoloLens2, I of wanted to try it running on #MagicLeap2 as well. Turned out the Magic Leap MRTK package wasn't quite ready for that, so I hacked a bit around until it was. Or almost entirely was. And blogged about my findings, of course. https://localjoost.github.io/Using-MRTK3-GA-on-Magic-Leap-2/