Table of Contents

Use PC camera to quickly run Mega (a fast but not recommended remote debugging method)

This document aims to guide developers on how to verify whether the Mega cloud positioning service can run successfully using a PC camera and on-site images without an EIF recording file.

Before you begin

  • Complete the Quickstart to learn how to run a Unity application with Mega features.

  • Connect a camera device to your PC and ensure it functions properly.

  • Expected functionality:

    This method is not our recommended approach for remote debugging. When recording is possible, using EIF files for debugging is the best practice we recommend.

    This method is only for debugging processes unrelated to tracking effects when no EIF file is available, such as verifying whether the Mega service is functioning properly.

    The effect seen using a camera on a PC is completely unrelated to the actual tracking performance on the device.

Operation steps

Complete the following steps to quickly run through the Mega service verification.

Get a site photo

Take a clear photo of the site, either by shooting on-site or by capturing an image using the panorama preview feature in the editor.

How to capture an image using the panorama preview feature

Click Mega Block Viewer(Dev) in the Hierarchy panel > Click Load on the right side of Panorama Marker in the Inspector panel.

Panorama load

Many yellow spheres representing Panorama Markers will appear in the scene:

Panorama markers

Click the panorama marker of the location you want to preview > Click Mega Block Viewer(Dev) in the Hierarchy panel > Click Hide on the left side of Panorama Marker in the Inspector panel.

Hide panorama markers

A site image will be displayed in the Mega Panorama window, which you can screenshot and save:

Site photo

Place some 3D content against the block dense model or panoramic placement

Place 3D content

Confirm the session verification tool is not enabled

Click on AR Session (EasyAR) in the scene > Ensure the Frame Player in its Inspector panel is turned off.

Confirm FramePlayer is off

Click on EasyAR.Mega.BlockViewer(Dev) in the scene > Ensure the verification tool in its Inspector panel is not Enabled (if dense models are not needed, you can also directly delete or hide EasyAR.Mega.BlockViewer(Dev)).

Confirm the verification tool is off

Click to run and test Mega with live images

  • Demonstration:

    Important

    Mega's localization service is relatively "forgiving" regarding input for localization, but this debugging method's results are only used to distinguish between "pass" and "fail" (i.e., a binary 0 or 1 outcome). It can prove that the Mega localization service is functioning but does not represent the actual tracking experience on a real device. To observe localization speed and tracking stability, be sure to debug using EIF files or test on a real device.

  • You can use a camera to run with images or videos. If localization succeeds, you will see 3D objects displayed on the screen and updated dynamically. Since the Block model is loaded in the scene, the Block model will also appear.

  • If you close the tool EasyAR.Mega.BlockViewer (Dev) (set active to false or delete the node), you will see the effect of virtual objects overlaid on the real-world scene.

  • The warning messages on the screen cannot be turned off. This usage method does not reflect the actual performance, so we restrict it to development purposes only. Developers should be aware of the implications of using it this way.

    Screen warning messages

  • You can determine if the system is running normally by checking the timestamp updates in the diagnostic information: If you see the timestamp in the diagnostic information on the screen updating continuously, it means the system is running normally.

    Judging by timestamp

    Important

    During use, you will inevitably notice the diagnostic text displayed on the screen or in front of your eyes. Carefully read the UI message output and consider the appropriate configurations for the development phase, testing phase, and post-launch, as well as which control switches to retain. Communication with EasyAR often requires providing this information, so it is recommended to utilize it rather than immediately turning it off.

Next steps