Table of Contents

Enum MotionTrackerCameraDeviceTrackingMode

Namespace
easyar

Fields

VIO = 0

Only tracking and hit testing against point cloud are available. CPU and memory usage are low, but plane detection, relocalization, and anchors are not supported.

SLAM = 1

Tracks and maps at the same time. Supports relocalization after loss, hit testing against point cloud, and plane detection, but has no anchors, does not support real-time pose correction, and uses slightly more CPU and memory.

Anchor = 2

Tracks and maps at the same time. Supports relocalization after loss, hit testing against point cloud, plane detection, and anchors, but has the highest CPU and memory usage. Anchors are saved automatically when hitTestAgainstPointCloud is called, and pose is corrected in real time through anchors.

LargeScale = 3

Suitable for large scenes. Tracks and maps at the same time, and supports relocalization after loss, hit testing against point cloud, plane detection, and anchors. Tracking is more stable with a large depth of field. Anchors are saved automatically when hitTestAgainstPointCloud is called, and pose is corrected in real time through anchors.