home.social

#mrtk3 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #mrtk3, aggregated by home.social.

  1. I wanted to see what it took to set up a proper #MixedReality application that ticks all the boxes (viewing and interacting with reality, hand tracking, spatial sound, etc) on a #Quest3, using the latest version of #MRTK3. Because well, you need to be cross platform these days if you and your apps want to be relevant in the MR space. It took some tinkering, but I got it to work, and I am glad to see I will be able to carry over my MR investments to different platforms

    localjoost.github.io/CubeBounc

  2. 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. localjoost.github.io/Making-an #openxr #MixedReality

  3. Two weeks ago I released my based app Walk the World for , a week later the exact same app for . 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. localjoost.github.io/Making-an

  4. 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. localjoost.github.io/Making-an #openxr #MixedReality

  5. 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. localjoost.github.io/Making-an #openxr #MixedReality

  6. 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. localjoost.github.io/Making-an #openxr #MixedReality

  7. LocalJoost ((@)localjoost(@)mstdn.social: "Spent a weekend porting the #MRTK3 version of Walk the World to #MagicLeap2. In the end, not so difficult but the documentation leaves some things to be desired If you have a device, download the package at schaikweb.net/WalktheWorld/ML2. Feedback and suggestions welcome" #crossplat

    Jun 16, 2024, 04:11 PM

    mstdn.social/@localjoost/11262

  8. Spent a weekend porting the #MRTK3 version of Walk the World to #MagicLeap2. In the end, not so difficult but the documentation leaves some things to be desired If you have a device, download the package at schaikweb.net/WalktheWorld/ML2. Feedback and suggestions welcome #crossplat

  9. After I wrote about how you could get the hand *position* while doing an air tap with #MRTK3, two developers asked me simultaneously how you could get the end of the hand *ray*. Noblesse oblige, and I wrote localjoost.github.io/Getting-t

  10. #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.

    localjoost.github.io/An-MRTK3-

  11. has a subsystem implementation for speech commands that is supported by . 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.

    localjoost.github.io/An-MRTK3-

  12. #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.

    localjoost.github.io/An-MRTK3-

  13. #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.

    localjoost.github.io/An-MRTK3-

  14. #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.

    localjoost.github.io/An-MRTK3-

  15. I get a lot of questions from developers about #MixedReality in general and #MRTK3 in particular. One developer wanted to know how you could find the actual *position* of an air tap. I found out, and of course blogged it: localjoost.github.io/Getting-r

  16. After successfully updating #HoloATC to #MRTK3 GA, I felt confident I could upgrade the #Augmedit #Lumi #HoloLens app as well. I was successful indeed - but there were some more *interesting* things I ran into. I updated my blog post from September significantly with my new findings. localjoost.github.io/Upgrading

  17. 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.

    localjoost.github.io/Using-a-S

  18. I wanted to see if I could run one of my more far-fetched samples on . 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.

    localjoost.github.io/Using-a-S

  19. 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.

    localjoost.github.io/Using-a-S

  20. 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.

    localjoost.github.io/Using-a-S

  21. 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.

    localjoost.github.io/Using-a-S

  22. With the arrival of #MRTK3 GA, a fellow developer reported my #Quest passthrough sample appeared to be broken after upgrading. I did some investigation, and fixed it. localjoost.github.io/Full-unde

  23. To my surprise there is no Store for #MagicLeap2. So how do you alert users to new versions and help them update? I made a little #ServiceFramework Service and some #MRTK3 UI to do just that. localjoost.github.io/A-Service

  24. 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. localjoost.github.io/Using-MRT

  25. After getting my app running with on , I of wanted to try it running on 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. localjoost.github.io/Using-MRT

  26. 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. localjoost.github.io/Using-MRT

  27. 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. localjoost.github.io/Using-MRT

  28. Last Wednesday, the #MRTK3 became GA. An important milestone for the XR community. Today, I subjected my app HoloATC to an upgrade, using it as a guinea pig to get an idea of the issues involved (rather than using my employer's app for that :grin:). I got it to work, but it wasn't entirely smooth sailing. Upgrading from a pre-release requires two steps you would not expect outright, but... anyway, read about it in my blog localjoost.github.io/Upgrading

  29. I just finished the first full version of HoloATC based upon #MRTK3 for #MagicLeap2. They have no store, so I give a download link. Alternatively, you can use the QR code in this post to look at with the built-in QR code app

    schaikweb.net/ML2/HoloATC_Magi

    Cross-platform XR development FTW!

  30. I just blogged: "#MRTK3 #StatefulInteractable #gaze, hover and select events - and how to use them" #HoloLens2 localjoost.github.io/MRTK3-Sta

    There's a lot of events on StatefulInteractable, and it might not be abundantly clear how to use them and why. Therefore, I decided to make a simple sample that shows you which event is triggered by what, and allows you to experiment with those events

  31. The transition from MRTK2 to #MRTK3 leaves some people confused - how does Spatial Awareness work now? Don't worry, I got you covered localjoost.github.io/Using-ARM

  32. It turns out you can actually use an underlay for passthrough on Quest 2/Pro with #MRTK3. This is a minor addition to the previous article. However, there are some caveats.

    localjoost.github.io/Full-unde

  33. Apparently it's not clear to everyone how hand simulation actually is operated inside the #Unity editor when using #MRTK3, so I wrote a little post about it, including two handy reference tables for both left and right hand operation localjoost.github.io/Using-han

  34. To prove the point I made a few days ago: I submitted HoloATC to the #Meta #Quest #Applab.

    oculus.com/experiences/quest/5

    App runs unchanged on #HoloLens 2, #Quest 2 and Pro with pass-through VR. This is an #MRTK3 app. #MRTK2 apps also run on the Quest platform.

  35. To prove the point I made a few days ago: I submitted HoloATC to the .

    oculus.com/experiences/quest/5

    App runs unchanged on 2, 2 and Pro with pass-through VR. This is an app. apps also run on the Quest platform.

  36. To prove the point I made a few days ago: I submitted HoloATC to the #Meta #Quest #Applab.

    oculus.com/experiences/quest/5

    App runs unchanged on #HoloLens 2, #Quest 2 and Pro with pass-through VR. This is an #MRTK3 app. #MRTK2 apps also run on the Quest platform.

  37. To prove the point I made a few days ago: I submitted HoloATC to the #Meta #Quest #Applab.

    oculus.com/experiences/quest/5

    App runs unchanged on #HoloLens 2, #Quest 2 and Pro with pass-through VR. This is an #MRTK3 app. #MRTK2 apps also run on the Quest platform.

  38. To prove the point I made a few days ago: I submitted HoloATC to the #Meta #Quest #Applab.

    oculus.com/experiences/quest/5

    App runs unchanged on #HoloLens 2, #Quest 2 and Pro with pass-through VR. This is an #MRTK3 app. #MRTK2 apps also run on the Quest platform.

  39. I wanted to have instant cross-platform communication between devices. I stumbled upon the #Azure Web PubSub Service. TI found the documentation not very clear and could find *no* examples of how to use it from #Unity. #HoloLens #MRTK3
    So I made one myself
    localjoost.github.io/Using-Azu

  40. RT @WindowsDocs: Welcome back Grace Hsu - @its_graceh - as she talks about the 3 main goals of the latest Mixed Reality Toolkit - #MRTK3.

    Docs and Downloads at msft.it/6018eMwJ0

  41. I just almost spent 6 hours chasing a 'bug in #MRTK3' that turned out to be ONE CHECKMARK I forgot to set - and I bothered the MRTK team about it, too.
    I think I will now go sit in a corner, enjoying some deluxe imposter syndrome and mutter some curses.
    How is your day going?

  42. Passthrough with #OpenXR and #MRTK3 on #Quest2, sorta works, following the idea by @DavideZordan. Using a transparent *overlay* as underlays don't work. /cc @FNS_Developer. Background is kinda dark.