Since both are being driven out of Microsoft, and we can even run Babylon.js on VR and AR (including Hololens2!) devices, it would make a lot of sense to have a version of MRTK that is implemented directly in Babylon. MRTK is MIT licensed as well.
The big challenge, of course, is that much of it would need to be rewritten, and once that happens, keeping it up-to-date feels like a full time job.
I suspect most of us are in the same boat; would love to see it, but can’t afford the time/resources. I mean, if I didn’t have anything else to do, I’d love to do it. but that’s a massive “if” …ha. I suspect this might be too much for students to do.
It would be interesting if we could divide and conquer the problem. Perhaps get different folks contributing different controls. Rather than putting a lot of work on one person, a bunch of people all do a small amount of work? Just an idea.
As with everyone else, the only thing I’m missing is time. You don’t have to convince me it’s needed, I totally agree
We have some implemented already. The bounding box, holographic buttons, slate, but we have different names for them (and maybe a slightly different design). They are also not only used for mixed reality, which made the interaction with them a bit different.
I think it’ll be the best of we decide which elements are the most important ones and which are optional, and most importantly which ones are missing and take it from there