Attached is Vuforia’s version of the app-level fix scripts provided by @adrianj (many thanks!) in the following forum thread. This can be used immediately with SDK 6.5 (Unity 2017.2), SDK 7.0 (Unity 2017.3) and SDK 7.1 (Unity 2018.1).
Here are the recommended steps for installing and enabling:
- Back up your project
- Import the attached DelayedVuforiaInitialization.unitypackage
- In the first scene that uses Vuforia, attach the VuforiaInitialization.cs script to any active game object, e.g. the ARCamera
- In the Vuforia configuration (Menu: Window -> Vuforia Configuration) and check “Delayed Initialization”
IMPORTANT: In case your application logic relies on Vuforia being initialized and started at scene startup, you may have to adapt that code. The best way to do this is to listen for the VuforiaStarted callback using: VuforiaARController.Instance.RegisterVuforiaStartedCallback(…);
We are also working on rolling out a similar fix via patch releases for SDK 7.0 and 7.1. Note that for 7.0 patch availability, we are reliant upon Unity's timing for releasing updates. Patching Vuforia 7.1 SDK will be done via installer functionality built into the Editor.
Lastly, contrary to previous Vuforia communications, we *will not* be providing patch releases for SDK 6.2 and 6.5. This is due to multiple factors, including Unity not providing long-term support for Unity 2017.2 (SDK 6.5) and earlier versions. We recommend that if you're still using Vuforia 6.2, you follow similar app-level logic in the attached scripts.