Table of Contents

Enum MotionTrackerCameraDeviceTrackingMode

Namespace
easyar

Fields

VIO = 0

Only supports tracking and hit testing against point clouds, with low CPU and memory usage, but does not support plane detection, relocation, and anchors.

SLAM = 1

Simultaneously tracks and maps, supports relocation after loss, hit testing against point clouds, and plane detection, but has no anchors, does not support real-time pose correction, and has slightly higher CPU and memory usage.

Anchor = 2

Simultaneously tracks and maps, supports relocation after loss, hit testing against point clouds, plane detection, and anchors, but has the highest CPU and memory usage. When calling hitTestAgainstPointCloud, anchors are automatically saved, and pose is corrected in real-time through anchors.

LargeScale = 3

Suitable for large scenes, simultaneously tracks and maps, supports relocation after loss, hit testing against point clouds, plane detection, and anchors. Tracking is more stable in large depth of field, and when calling hitTestAgainstPointCloud, anchors are automatically saved, and pose is corrected in real-time through anchors.