@metabit

Thank you for the useful information. I understand now. 

Daverin

Hello @daverinnadesan18,

daverinnadesan18 wrote:

Why is it fetching the device profile on every application start? Why not fetch it only on first run?

The release for support of new devices using features driven by Vuforia VIO (not ARKit or ARCore) is not aligned with Vuforia Engine releases - we can release a new device at any time. As supporting a new device also requires an updated device profile, we enabled the option to synchronously check for this during Vuforia.init().

This was a convenience feature for developers who wanted to take advantage of newly supported devices as they became available.

daverinnadesan18 wrote:

How do I disable this feature and what would be the implications?

To disable it, please see the following article (under Vuforia Engine Initialization, about 2/3 down): https://library.vuforia.com/articles/Solution/how-migrate-vuforia-7_2.html

The implication is that if you are running features that use Vuforia VIO (Ground Plane, Model Targets, Extended Tracking), your device may not receive an updated device profile *before* camera start. This could cause tracker initialization failure (in the Ground Plane case), or a degraded user experience on first app run.

Thanks,

Vuforia Engine Support

Hi medabit.

I tried what you suggested and it worked. Why is it fetching the device profile on every application start? Why not fetch it only on first run?

How do I disable this feature and what would be the implications?

Thanks for your help

Daverin 

Hello,

daverinnadesan18 wrote:

This means that it is not to do with the "Vuforia Engine Initialization" mentioned.

Apologies, but I'm not following your logic. How did you come to this conclusion? Which other version of Vuforia are you comparing this to?

The new, synchronous initialization method means that Vuforia will not complete init until it can reach the device profile service, or time out. I would suggest you try running your app with the device in airplane mode. The Vuforia SDK should detect that there is no network connection and thus not attempt to contact the server. In theory, if the delay is related to the new synchronous initialization, it should be gone.

Thanks,

Vuforia Engine Support

Vuforia v7.2.24

Unity 2018.2.0f2

Hi I am experiencing the same problem after upgrading to v7.2.24 with my Samsung S9+. Initialization time used to be 0.5 seconds and is now 4-5 seconds on every application start (not just the first one).

This means that it is not to do with the "Vuforia Engine Initialization" mentioned.

I also deleted all datasets to ensure that they are not the issue.

I am not sure if this issue present only with samsungs. 

I wonder if the slow load time has something to do with the new auto load and activate databases in 7.1.  If you were manually loading and activating databases prior to 7.1+ , and your database had a decent number of trackables, you'd see a difference in load time after upgrading.  Refer to the migration docs if you need to know how to handle manually loading again.

This is also happening for me on Android. Noticed it using Unity 2018.2 and Vuforia 7.2.2. On Android, it takes at least 4-5 seconds to start up the app. Previous versions of Unity/Vuforia would only take a second or so to load.

iOS is unaffected as the same app with the same versions of Unity/Vuforia loads instantly and fine.

Hello,

It is unclear to me why you'd see such differences in the initialization time on either release.

Please note that in SDK 7.2, we have introduced some changes to the initialization process that may impact the flow of your application. Please see the "Vuforia Engine Initialization" section for more details: https://library.vuforia.com/articles/Solution/how-migrate-vuforia-7_2.html

Thanks,

Vuforia Engine Support