Using the Model Target Motion Hint

Vuforia provides a STATIC motion hint, ideal for tracking stationary objects, that improves Model Target tracking. Setting the Model Target to STATIC optimizes device performace. This is because the tracker does not need to update the trackable position on every frame.

A STATIC setting allows for longer AR experiences and for less powerful devices, especially eyewear, to more efficiently run the application. This setting, however, only provides power savings when device tracker is activated.

The behavior of STATIC differs from ADAPTIVE. STATIC works best with objects that are immobile, such as cars and large machinery. If you expect the object to be moved, select the ADAPTIVE motion hint. Moving an object set to STATIC will likely break the tracking, forcing the user to wait for the object to be recognized again.

In ADAPTIVE mode, Vuforia Engine automatically selects the optimal tracking behavior, depending on the current situation. However, ADAPTIVE does not permit the same power optimizations compared to STATIC mode. As in previous versions, ADAPTIVE still only allows limited motion of Model Targets.

All Model Targets generated before the 8.5 release default to STATIC mode when used in Vuforia Engine 8.5 or newer.

In the Model Target Generator (MTG), the motion hint can be set to STATIC or ADAPTIVE. During the creation of a Model Target database, the MTG stores the value in a .xml dataset file. The motion hint value can be changed later in Unity or native.

To adjust the motion hint value in Unity, change the value in the Model Target GameObject component. For native development, declare the value through an API call.

For each platform, the following articles contain more detail on how to set the motion hint:

Platform Article
Model Target Generator How to Create a Model Target
Unity Introduction to Model Targets in Unity
Native development Model Targets API Overview