HoloLens 2 long-range tracking test (outdoors v2, fewer trees)

[@ChopLabalagun]

very nice test, i wonder what the ML1 would d. that is a hell of a big mesh. You also have to consider that you were recording while doing this. Last time i tried an intense game in ML1 plus recording the devices restarted XD after 30min. after some dev testing with ML1 i notice that we have some sort of control over what we want from the mesh so not sure if possible with H2 but it would be cool to see if you can mesh that using the built-in from the OS. you know like when you setup a new room. the ML1 seems to cut the mesh sometimes when i scan the house.

[@nickllodeon]

It sounds like you're talking about the environment mesh itself rather than the drawn lines I'm talking about in the video. In either case, it seems like some kind of limitation with far clip range... probably a small amount of VRAM that forces it to offload parts of the mesh (it may be dependent on the underlying environment mesh rather than the drawn lines). It just seems like that process could be done more efficiently/continuously than the sudden corrections we see in the video. I don't have an ML1 on hand (they're generally not very useful for research) but I can't imagine that it will do better than the HL2 given that the ML1 is only slightly stronger than the HL1...

[@ChopLabalagun]

@@nickllodeon could you please expand why is not useful for research?

[@nickllodeon]

Off the top of my head: 1. ML is a small company with a device with a unique API. Research involving really niche, unreliable companies like this often ends up in disappointment when the company gets bought out or bankrupt. There are tons of AR/VR companies that made headsets that were already barely usable, then the company failed and the API is suddenly no longer supported as game engines update. AR/VR researchers are more hesitant to spend money on small companies like this for that reason. Since MS is a big company dedicated to expanding AR, they're a more reliable choice for research that might go on for a few years. If we are going to spend a couple thousand $$$ on an HMD, it better have guaranteed support for a few years. 2. The HL API is more standardized across other MS devices and services. MRTK works with the Windows MR headsets and is very easily compatible with Azure, Kinect, etc. It makes it much easier to work with from a developer POV. It also means you can more easily write code that works the same way between AR and VR 3. The ML doesn't have nearly as good eye or hand tracking 4. The ML hardware is significantly weaker and the sensors are not as high-res (in particular, depth) 5. The battery pack makes the ML much more annoying to work with, ergonomically 6. The ML needs special lenses; you can't wear normal glasses while using it 7. The ML uses a custom version of Android that does not necessarily have any ARCore support. Most mobile AR devs who want to use an Android device really want ARCore b/c its support is more reliable, it has tons of example code, it can track almost better than the ML even without depth sensors, etc. 8. HL2 FOV and picture quality is a lot better, which matters a lot for any kind if UI/UX research we want to do 9. The ML1 user interface is not as friendly (I constantly ran into bugs with it when I was using it ~2 years ago). The remote thing that the ML1 uses is not as easy to use as the HL2 (or even HL1) gestures. It also crashed a lot

[@ChopLabalagun]

@@nickllodeon thanks for the info 😊

[@ChopLabalagun]

I have experience alot of the ones you mentioned myself and that explains why I found the device for 4rd of the price. And HL1 super expensive at least I have something to play with and stuff to consider for the next time.

[@julesmohammed2504]

How is my Hololens 2 not this clear. I keep getting some pinkish screen :(

[@nickllodeon]

this is from the built-in recording software which doesn't show the HL2's lens distortions. I have other videos on the HL2 lens problems which I guess haven't been fixed yet (e.g. kzbin.info/www/bejne/sGebd6WDi7Glers)

[@1HololensfansOfNaruto]

It's not bad... But it could improve by miles

[@nickllodeon]

Yeah, but it's all about managing expectations. The HL1 and HL2 were designed with rooms in mind... and this is obviously a much bigger tracking task than a room. In an enclosed space, these devices are much more reliable. I do think they could fix the tracking system to work with more general tracking tasks like ARCore, but I'm guessing that's not really their focus right now.