Mega tracking anomaly troubleshooting guide

Mega employs end-cloud fusion technology, combining cloud-based positioning with device SLAM to maintain continuous tracking, ensuring AR content is precisely anchored in the real world. The ideal tracking state should exhibit no drift, low jitter, and high smoothness. This document focuses on tracking anomalies during Mega positioning, helping you understand correct expectations, common error classifications, device differences' impact, and when to contact EasyAR technical support.

Expected effect

Tracking anomalies often stem from mapping data quality, environmental factors, or device compatibility. You can use MegaToolbox for troubleshooting. If the issue involves runtime application performance, you can also directly experience it with your application.

With high-quality Mega Blocks and a good environment, the tracking performance should meet the following standards:

• Stable anchoring: After successful positioning, virtual content remains fixed in world coordinates without noticeable drift.
• Robust recovery: Tracking automatically resumes after brief occlusion, rapid rotation, or lighting changes.
• Smooth performance: Content renders normally without significant jitter.
• Environmental limitations: Tracking performance may degrade near plain-colored walls, open floors, glass, or highly reflective surfaces.

If your experience aligns with the above description, the tracking performance is generally normal.

Normal phenomena: Minor jitter or brief loss is acceptable, especially during the verification phase of the creation process. If stability is maintained over time, it is considered normal.

Self-diagnosis using mega toolbox

Tracking anomalies usually appear after successful positioning. If tracking anomalies occur in the application you are developing, you need to check the positioning status in Mega Toolbox (see Mega Toolbox Operation Manual - On-site Positioning Test and Positioning Issue Feedback Data Recording Tool). If the tracking effects are inconsistent, first check whether there is an issue with the program implementation.

Operation steps

1. Install Mega Toolbox on your test phone.
2. Open Toolbox, go to On-site location test & location issue feedback data recording, and log in with your account credentials.
3. Select the SLAM method and choose the location library.
4. Bring the phone to the exact location where the issue occurs and observe the display on the Toolbox interface.

For details on how to configure the location library and how to conduct on-site testing, please refer to On-site real-time performance preview.

Judging based on the toolbox display results

Mega Toolbox is one of the most important diagnostic tools. It is a standalone mobile app that can help you determine whether the issue originates from Mega or your application.

• Localization exception

  If the Toolbox interface displays statuses other than Found and NotFound, you can refer to the localization failure handling guide for resolution.

• Localization success

  The Toolbox interface shows the status as Found, and the placed content is displayed normally.

  Normal scenarios include:

  • The content fits the scene well and may move slowly over time
  • If the virtual content exceeds a certain range from the scene, it will be corrected directly

  Abnormal scenarios include:

  • The content in the scene continuously drifts in one direction
  • The content drifts in one direction and then pulls back, repeating this pattern
  • The content keeps growing larger or smaller
  • The content jumps between several locations

Error classification and troubleshooting

Use Toolbox for testing. Based on the abnormal phenomena, you can check the corresponding suggestions.

Error classification	Possible causes	Suggested actions
Device status always shows NotTracking	Environment lacks distinct features, poor lighting, or suboptimal phone model	Determine if it's caused by the environment or the phone model. You can try changing the test area or phone model
Content in the scene keeps drifting in one direction	Suboptimal phone model, SLAM drift	Try a better phone model
Content drifts in one direction, then pulls back, repeats	Suboptimal phone model, SLAM drift	Try a better phone model
Content keeps getting larger or smaller, etc.	Suboptimal phone model, SLAM drift	Try a better phone model
Content jumps between several locations	There may be several similar areas in the scene. When you start positioning from these areas, interference may occur	Start positioning from other unique areas or use Bluetooth assistance

Further testing

To better identify the issue, you can perform further testing as described below. If you are a developer, you can refer to Mega-supported devices and platform applications.

Test with better devices

Different devices may vary in tracking performance, mainly due to differences in camera quality, sensor accuracy, and processor performance. When validating the creation process, it is recommended to test on several different device models to ensure compatibility. If tracking works normally on ARKit or ARCore devices, the issue is likely due to the performance limitations of the problematic device. For weaker-performing devices, try testing with different SLAM methods.

Choose different SLAM methods

For some lower-end devices, the SLAM accuracy is relatively poor due to the precision of the phone's sensors and computing power. On the On-site positioning test page in Toolbox, try selecting different SLAM methods for testing. You can choose to use FiveDof, ThreeDof, or ZeroDof to experience different tracking effects.

Cases requiring feedback

Most tracking anomalies during the creation process are due to device issues, but the following situations may involve Block algorithms or service problems. It is recommended to report them to EasyAR support:

• Frequent drift persists after testing on multiple device models and regions
• Toolbox fails to locate or exhibits abnormal positioning
• The same Block shows drastically different effects under varying weather or lighting conditions, and the issue cannot be resolved through supplemental updates

If problems persist, provide on-site problem descriptions, device information, screen recordings during runtime, EIF files, and Mega service information to EasyAR staff. Before reporting the issue, ensure the EIF can reproduce the problem in Mega Studio.

With this guide, you can quickly troubleshoot tracking anomalies during the creation phase and improve the overall quality of Mega Blocks.