Simulate AR projects using Mega capabilities with the session validation tool
This article guides developers on how to use the session validation tool to load recorded EIF data and simulate AR projects using Mega capabilities in the Unity Editor.
Before you begin
- Complete the Quickstart to learn how to run Unity applications with Mega features.
- Understand what EIF is.
- Learn how to capture simulation data.
Why using the session validation tool for simulation is a good approach
Remote development: No need to endure harsh weather conditions on-site. With EIF data, you can develop large-scale geospatial AR applications right from your office.
Cross-platform debugging: Avoid frequent connections to various mobile devices. Simulate positioning and tracking effects for different terminals like phones and headsets directly on a Windows PC.
The "gold standard" for issue reporting: A reproducible EIF file is the key evidence for the EasyAR team to resolve positioning and tracking issues for you.
Note
Although EIF data is recorded with high precision, simulated results may still differ from actual usage.
Additionally, simulated data has limited coverage of real-world environments. Field testing is essential before final release.
Operation steps
Follow these steps to simulate using the session validation tool.
Prepare the on-site recorded EIF file
Depending on the recording format, the recorded EIF data should be a .mkveif file (or both .eif and .eif.json files, which are inseparable).
.eif and .eif.json:
.mkveif:
Place some 3D content relative to the Block dense model or panorama
Enable the Session Validation Tool
Click AR Session (EasyAR) in the scene > Ensure Frame Player is enabled in its Inspector panel.
Run
Click the toolbar button or the run button on the Session Validation Tool to start running the project in the Unity Editor.
A pop-up will appear after running—This is normal. It simply indicates that Frame Player is active.
Click the tool's button to open the EIF file.
Once successfully opened, playback starts automatically. Use toolbar controls for pause/play. Some newer EIF formats support progress bar scrubbing.
Simulation effect:
If a Block dense model is loaded in the EasyAR.Mega.BlockViewer (Dev) tool, it remains visible. This is useful for position comparison or checking positioning accuracy in unmodeled areas.
Typically, you can deactivate (set active to false or remove the scene node) the EasyAR.Mega.BlockViewer (Dev) tool. Then, during runtime, you'll see virtual objects overlaid on the real environment.
Important
During use, you'll notice diagnostic text displayed on screen or in your line of sight. Carefully review UI message output, and consider configuration strategies for development, testing, and post-launch phases. Communication with EasyAR often requires these logs—utilize them rather than disabling immediately.
By default, after startup and before the first Block is localized, the entire MegaBlocks and its child nodes have active set to false, so content remains hidden.
After successful localization, these nodes' active becomes true, and content appears with continuous position updates.
To modify this behavior or implement custom active state control, refer to BlockRootController component reference and BlockController component reference.