3 ms·

HoloLens 2 is a difficult one. It has a lot going for it. But, the poor FoV, coupled with only really being able to use your index finger for typing have really

HoloLens 2 is a difficult one. It has a lot going for it. But, the poor FoV, coupled with only really being able to use your index finger for typing have really made my experience worse. The worse of it is developing for the thing. Just a complete asinine workflow. Quest is so much better to develop on, it's insane. Props to Valve on that regard as well.

verdverm 3y ago
fun fact, there is a group maintaining the MRTKv3-Unity stack (https://github.com/MixedRealityToolkit/MixedRealityToolkit-Unity https://github.com/MixedRealityToolkit/MixedRealityToolkit-U...) The FOV in real AR glasses has not improved since. Even the newly released are still 50deg or less. I thought programming for HL2 with MRTK was a nice experience, at least not bad. Most of the rough edges were Unity, which I still have for Oculus, and deploying to HL2, which required the Visual Studio step. I still think MRTK is an awesome library by design, tons of good research went into it, plus it was a whole package with tons of the extras you want in an AR app. Super bummed MS killed both projects.