All Model Targets Targets with motion hint STATIC are more sensitive to wrongly specified physical size in the dataset.

are more sensitive to wrongly specified physical size in the dataset. Model targets may switch to EXTENDED_TRACKED more often during very fast user motion when the motion hint is set to STATIC . We recommend using ADAPTIVE if robust tracking during very fast motions is required.

more often during very fast user motion when the motion hint is set to . We recommend using if robust tracking during very fast motions is required. When using Advanced Model Targets, recognition is not very reliable in closeup scenarios if the target fully covers the view. It is recommended to guide the user to use views where part of the silhouette of the model is visible and a part of the camera view is covered with background. See this Model Target Guide Views for more information.

The native Model Targets GuideView interface still uses the legacy y-down camera coordinate system convention in the getPose/setPose methods. Environments Mid-air anchors are now stabilized to the environment map when using Vuforia Sensor Fusion. Under some circumstances this can be still unreliable and cause drift in the mid-air anchor position over time.

Using multiple trackables simultaneously while Extended Tracking them on Vuforia Sensor Fusion provider may lead in edge-cases to degraded tracking quality.

Using User Defined Targets (UDT) in combination with Device Tracker and Fusion providers other than VUFORIA_VISION_ONLY is not supported and may lead to unstable tracking results.

is not supported and may lead to unstable tracking results. Device Tracker reset during Extended Tracking with Model Target might in some cases lead to unexpected relocalization issues. Deactivating/activating the Model Target improves the situation – but the user will have to start the experience again with detecting the Model Target.

The Ground Plane sample app does not allow re-positioning of the annotations into a new area after pause and resume. Going back to the original area and recovering the original annotation is necessary before it can be moved. As an alternative you can reset the experience after resume to use the app again.

VISLAM may fail on environments with predominantly edgy structures with fine lines w/o other texture.

PositionalDeviceTracker may show some tracking instability after pausing and resuming the application when VISLAM Fusion Provider is used. This can be mitigated by encouraging users to move the device around a bit to reinitialize tracking after resuming the AR session. In cases where applicable, it may be necessary to go back to a target and redetect it if extended tracking does not resume normally.

may show some tracking instability after pausing and resuming the application when VISLAM Fusion Provider is used. This can be mitigated by encouraging users to move the device around a bit to reinitialize tracking after resuming the AR session. In cases where applicable, it may be necessary to go back to a target and redetect it if extended tracking does not resume normally. Under certain conditions when doing fast motions during Extended Tracking using Fusion-provider VISLAM an apparent shift in augmentation might be observed. Approaching the original target and/or resetting Device Tracker will resolve the issue.

The manual rotation offset of the object in the Ground Plane sample does not reset after 'reset' is hit. Other The improvement to detect Image Targets at a greater distance introduced in SDK 7.5.20 does not apply for Cloud Targets.

Android Apps may experience long dataset loading times and/or run out of memory if Advanced Model Target databases with more than 10 trained models are used. The exact number of supported targets is dependent on model size and complexity as well as the device that is being used.

On the Vuzix M300, GameObjects need to be parented to a Target or Anchor in order to render in the correct orientation

need to be parented to a Target or Anchor in order to render in the correct orientation In some occasions, the sample UVC driver implementation may fail to start after the USB camera permission has been accepted on Android.

After Device Tracker loses tracking with ARCore, it may be necessary to direct the user to return to the target to recover extended tracking when using Advanced Model Targets.

On Vuzix M300, setting camera autofocus mode to continuous may impact performance of video background.

Some Snapdragon Android devices show rendering artifacts when sample video is played and stopped

For the Android native sample, if you upgrade the Android Gradle build plugin to version 4.0.0, as suggested by Android Studio, you will get the following build error: "More than one file was found with OS independent path 'lib/arm64-v8a/libVuforia.so'." . If you need to upgrade the plugin version, you can simply modify the app/build.gradle to remove the line "jniLibs.srcDirs "$VUFORIA_ENGINE/build/lib""

iOS Running (Advanced) Model Targets with Device Tracker on dual-core iOS devices (e.g. iPhone 6/6s) may result in noticeable video background lag.

A crash is observed on the iPad Pro 4th generation on application start in cases where the device is connected to debugging.

UWP Augmentations placed on Ground Planes may jitter more on UWP tablet devices than on other platforms.

On devices with outdated Intel AVStream camera drivers, the camera feed sometimes freezes.

On HoloLens, rapidly attempting to deactivate or activate a VuMark database within the Vuforia_onUpdate callback can lead to freezing.

callback can lead to freezing. Small or far away Image Targets may temporarily show increased jitter on HoloLens when only very limited head motion is performed.

Extended tracked targets may be reported with incorrect poses for one or two frames after pausing and resuming when using Vuforia Sensor Fusion provider.

On HoloLens, starting a Vuforia App when an existing Miracast session is active will terminate the Miracast session. It is possible to re-start the Miracast session and use it while Vuforia is tracking, however any camera start operation in Vuforia will again terminate the Miracast session.

Vuforia UWP apps may exhibit symptoms such as a black screen or frozen camera image when another app is also using the camera.

Lumin N/A

