If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite
It's checked in under the official google github account and there are already commits merging "internal" branches. I think in this context "not official" means "expect no support"/"we're not responsible if it causes your daughter to start dating that disreputable rooted phone down the street".
Lullaby does not provide a platform-indirection layer. The responsibility of creating the necessary windows and graphics context and setting up the main event loop is left to the users of the library. Similarly, Lullaby does not provide I/O abstractions, networking libraries, power management, etc. The focus of Lullaby is purely on the simulation of the VR/AR "world".
So, when they say it's cross-platform, don't think it solves the problem of supporting multiple HMDs on multiple OSes. It seems to be cross-platform in the sense that it doesn't solve any of the platform-specific problems.
Hopefully, some projects will be forthcoming (or already exist) for running it on different HMDs and OSes.
Yeah, exactly my analysis. Panic in Google and quick conference: "What can we do IMMEDIATELY to look like we have a response?"
First, developing this wasn't immediate. Releasing it might've been.
Second, how is Tango not their answer to ARKit? Rather, how is it not the other way around, with ARKit being an answer to Tango? Likewise, ARToolKit seems like a lower-level of a subset of what Tango does, albeit on generic hardware.
Lullaby seems complementary to Tango and potentially ARToolKit. Releasing it might be some sort of reaction to ARKit, but it clearly dates back further and has a scope well beyond what I can see of ARKit's functionality.
Comment