Log in or register to post comments

Vuforia initialisation state and DLL

January 16, 2017 - 5:04am #1

Hi All,

We have a project that has a unique requirement of integrating an old version of the GoogleVR SDK (1.9) with the latest vuforia, to do this we have successfully used 'method 2' from the integration guide here: https://library.vuforia.com/articles/Solution/Integrating-Cardboard-to-the-ARVR-Sample



We have a requirement to have Vuforia tracking, GoogleVR and a (Unity UI GUI 2D) menu enabled in different combinations for different scenes:

  • Scene 1 - only has a regular camera and a UGUI canvas - loads scene 2
  • Scene 2 - hasthe "regular" GoogleVR integration - loads scene 3
  • Scene 3 - has the "full" GoogleVR / Vuforia ARCamera integration running as normal

This seems to work but sometimes, it seems Vuforia gets into an inconsistent state - my feeling on this is that the DLL gets loaded into memory, something we are doing in play mode in the editor is leaving the DLL in an inconsistent initalisation state and then subsequently initialisation fails until you close both Unity and Monodevelop to flush the DLL.

Is this consistent with other peoples experience? Is there something about our setup above that is "bad /.Wrong" or causing issues ? Am I right in my assumption about the DLL ?

We are developing and testing in windows at the moment...

Log in or register to post comments