Creating Vuforia Engine Drivers
Developers are able to define their own Vuforia Engine Driver to provide external data to the Vuforia Engine. For instance, manufacturers that want to provide access to a USB or a Bluetooth camera can create their own Driver so that Vuforia Engine developers can take advantage of their hardware. The Vuforia Engine Driver framework also allows developers to pull image frames from other locations such as video or image files stored locally or remotely.
The Vuforia Engine Driver must be written in C/C++ and must be implemented as a standalone dynamic library (dll or so file) which Vuforia Engine will load at runtime. For more information on how to create a driver, please refer to Creating a Custom Driver.
Using Vuforia Engine Drivers
Developers that want to access external systems through a Driver needs to specify the Driver before initializing Vuforia Engine. Once Vuforia Engine is initialized with a Driver, Vuforia Engine will continue to behave in similar ways as when it’s using a built-in camera. Authoring applications and experiences are similar to when authoring an application using the built-in camera.
IMPORTANT: When using the Vuforia Engine Driver Framework, it is strongly recommended that developers use a license key generated after April 10, 2018. Refer to the Vuforia Engine developer portal to generate new keys.
The Vuforia Engine Driver Framework currently supports Android and UWP (Universal Windows Platform) hand-held devices. In addition to traditional phones and tablets, the Vuforia Engine Driver Framework also supports Qualcomm’s Dragonboard 410c running Android.
Developers can take advantage of Vuforia Engine Driver framework through Native platforms (Java for Android and C++ for UWP) or they can create applications using C# in Unity (NOTE: Play mode does not load Vuforia Drivers).