"We offer new support options and therefor the forums are now in read-only mode! Please check out our Support Center for more information." - Vuforia Engine Team

Vuforia Initialization Time

Since upgrading to Vuforia 1.5.9, we've experienced extended initialization times, mainly the first time the app loads. As I understand it, based on research here, this is due to Vuforia downloading information about the device / camera to provide better performance. This makes sense, and it is acceptable to have a bit of a load time the first run, for a better overall experience. However, in some cases, it'd be helpful to speed this process up, or disable it altogether. For example, when doing rapid prototyping / development, we'll often build and run an app dozens of times per day. However, using the sample ImageTargets, without any modifications, devices we've tested take anywhere from 21 seconds to 52 seconds to initialize. Within our app, the time is even longer, sometimes taking up to 2 minutes to initialize (this appeared to be loosely coupled to the number of trackables, but I haven't done extensive testing to verify that). This initialization time really puts a hamper on rapid development, because every minor code change requires a long initialization time, cutting into dev and testing time pretty significantly. So is there a way to disable this to aid speeding up development? Thanks!

That's surprising, I don't typically see an initialization time of more than a few seconds. Are you behind a particularly slow internet connection? I recommend WiFi during development rather than the cell network. One option is to develop with your phone in Airplane mode.

dbburgess

Tue, 04/17/2012 - 20:52

Thanks for the reply. I've got a pretty good internet connection, and have actually tried it on 3G, 4G, and different WiFi connections. All have similarly slow times.

I have a Galaxy Nexus 4.0.2 here. ImageTargets 1.5.9 takes about 3 seconds to start up. I'm building and running directly from Eclipse, but not debugging. Ah, but perhaps that's the issue! I just ran again with the debugger, and indeed it took longer to start up.

dbburgess

Wed, 04/18/2012 - 17:54

That is indeed the differentiation. Running without debugging does speed it up dramatically. It never even occurred to me to try that, but in hindsight, it makes sense.