Start a new topic
Solved

Poor performance on Instant Tracking

I am really excited about your new Instant-Tracking feature. The Demo Videos on Youtube look very awesome and the tracking seems very robust.

But I tried the feature now on two phones (nexus5X + Samsung A3) and couldn't get a good tracking result. I use the Instant-Tracking sample scene in Unity 5.5 without any modifications, I testet the sample app both outdoors and indoors, with good lightning conditions. When I initialize Tracking and just rotate the phone, it works really good. But when I start moving and doing some translational movement, the tracking is lost very quickly. It also seems that tracking is lost immediately when the 3D-content leaves the viewport.

Is there anything I might do wrong or is there any way to improve tracking perfomance? Is there a difference in accuracy between Unity and native APIs?
E.g. the floating turtle example seems so accurate, even though the tar road shouldn't be the ideal texture to track on..

I uploaded a video on vimeo (pw: wikitude) to demonstrate this issue.


Hello Christoph,

Thank you for your feedback. Could you please share a public video with us, so that I can see what your issue is, since the one you shared with us is a private one? Did you refer to the documentation here regarding Instant Tracking?

Thanks
Eva

 

Hi Eva,

thanks for your fast response.
Sorry, I edited the video settings so it's no available for everyone. 
I also uploaded a second video with an outdoor example.

thanks alot
Christoph

Hi,


One of the main reasons for the performance difference is that Unity doesn't currently allow 64 bit libraries to be used on Android, so we need to use 32 bit, even when the device is capable of running 64 bit instead. The Nexus 5X in particular seems to have a big performance drop because of this. The turtle video was shot on an iPhone 7 Plus, as mentioned in the description, and on iOS we have no restriction in using 64 bit with Unity. We will also investigate further to see if there are other issues specific to the 5X.


Best regards,

Alexandru.

Hi Alexandru,

thanks for your reply. Would that mean using your native Android SDK or the JavaScript SDK could boost the performance on 64bit devices (e.g. Nexus5x)? 
I tried the Unity scene on an Samsung A3 as well and perfomance was almost the same as on my Nexus.

Hi,


Yes, I would expect that the other SDKs would work better on the 5X. I don't have an A3 to test on right now, but on the S6 and S7 the performance is much better, compared to the 5X, even if they too are 64 bit devices.


Best regards,

Alexandru

alright, I will try and test the android SDK then and see how this works.

Thanks alot
Christoph



Hi there,


I have also noticed that the Instant Tracking has poor performance - especially in comparison to market competitor Kudan which appears to track items much better with their SLAM implementation.


I am using the Unity SDK with a Samsung Galaxy S6 and have tried various different environments. The phone also gets extremely hot whilst using the application too - so much so that after a 5 minutes or so the phone has to close all applications (Even though the app running Wikitude is the only application open) as the phone is in danger of overheating.

Is there anything that I can do to improve the Instant Tracking performance, and SLAM behaviour.

Thanks,
Sam

Hello Samuel,

Thank you for your feedback. Could you please share a public video with us, so that I can see what your issue is? Did you read the reply provided by our technical member above, where he explains in details the issue?

Eva

Yeah, same problem. Kudan AR have much better instant tracking of wikitude. Wikitude instant tracking lost very quickly the tracking when user move close to virtual object.

Hello Vincenzo,

First of all, are you using our latest SDK version? In addition, could you please share with us a video demonstrating the issues you are facing with Instant Tracking so that we can further investigate?

Thanks
Eva

 

Login or Signup to post a comment