![]() Read more on ARCore release on Google Blog. Some of them (like the S8+) were previously only activable through this hack, but now are officially compatible. UPDATE: ARCore has been released in v1.0 and 13 phones are actually now compatible with it. If we would be able to remove such kind of check… we could install ARCore everywhere! The Zenfone is a Tango phone but can’t execute ARCore, that is a subset of Tango… this is absurd!įor sure Google is not blocking these phones based on features (otherwise the S8+ and Zenfone would be enabled) but by the phone model name. ![]() Developers would really love to try ARCore on these devices, even if the tracking is not perfect, to begin experimenting with this interesting framework, but they actually can not. The problem is that there are other phones that surely have the capability of performing AR, like for instance the Samsung S8+ or the Asus Zenfone AR, that are Daydream ready but are not ARCore ready. Another reason is surely to incentivize people to buy its flagship phones or the ones of its partners, but I don’t want to talk about this, now. So it has imposed these constraints to offer an optimal AR experience. Furthermore, we’re talking about very recent devices, that have the computational power to handle AR tracking and rendering at the same time without the application becoming sloppy. This means that the tracking is very stable and effective. The most important of them is that on these devices it has managed to find all the calibration parameters of the phone IMU sensors and the camera. ![]() Google has locked ARCore installation only to certain devices for various reasons. The problem Google ARCore (Image by Google) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |