Mega block Editor Tool Reference
Note
This tool only exists in versions >= 4003.
You can use the editor tool only after importing the com.easyar.mega package.
A screenshot of the tool under default conditions after it is successfully created.
A screenshot of the tool when a block has multiple sets of meshes.
Tip
A block may contain multiple sets of meshes. Blocks created using the Large Space Fusion or Incremental Update features may contain multiple sets of meshes. Each set of meshes can be loaded and unloaded independently. The overlapping areas of the boundaries of each set of meshes will not overlap perfectly. You can choose which mesh sets to load according to your actual needs.
| Name | Description |
|---|---|
| X | Delete the editor tool. |
| From | The App ID of the currently connected service. |
| Updated | The service connection time. |
| Reload | Reconnect to the service. If a block ID is specified and the block exists in the service, the Mega block editor tool interface will be displayed. Otherwise, the error interface will continue to be displayed. |
| [block name] (v) | Display the block name and version. Click the left button to expand/collapse the detailed block information. |
| Diagnosis Info | Export diagnostic information. |
| Job ID | The mapping task ID of this block. |
| [mesh group name] | Display the mesh group name. Click the checkbox to load/unload mesh data. |
| Retry | When mesh loading fails, click this button to reload. |
| Mesh | Show/hide the block mesh. |
| Export | Export the block mesh. |
| Panorama Preview Marker | Show/hide the panorama preview marker points. |
| Mesh Bounds Gizmo | Show/hide the mesh boundary gizmo. |
| Collider Mesh | Collision detection mesh configuration. Options:
|
Scene Nodes
The data of the editor tool is stored under the EasyAR.Mega.EditorTool node. Deleting this node is equivalent to deleting the data of the editor tool.
Caution
You cannot directly modify the content of the EasyAR.Mega.EditorTool node, especially the Transform of this node. Otherwise, the editor tool may not work properly or the content display position may be incorrect during tracking.
Basic Information
| Name | Description |
|---|---|
| Job ID | The mapping task ID of this block. |
| Block ID | The block ID. |
| Block Name | The block name. |
| Modified | The block modification time. |
| Version | The block mapping version. |
| GNSS Location | GNSS (GPS, Beidou, etc.) coordinates. The correct values are only displayed after the block mesh is loaded. |
| Latitude | The GNSS latitude coordinate. It is only displayed when the GNSS coordinates are generated in the block mapping data. |
| Longitude | The GNSS longitude coordinate. It is only displayed when the GNSS coordinates are generated in the block mapping data. |
| Altitude | The GNSS altitude coordinate. It is only displayed when the GNSS coordinates are generated in the block mapping data. |
| From Service | The service information used when obtaining the block. |
| Type | The service type. |
| App ID | The service App ID. |
Mesh
The block mesh is aligned with the block tracking target space, and 3D content can be directly placed on the model.
The block mesh data is stored under the tool node and only exists in the editor mode. It will not be packaged into the final application.
Loading
Click the selection box next to the mesh group name. This will start the loading process of this group of data. After loading, you can see the mesh of the current group in the Scene window.
Deselecting the selection box will unload this group of data.
During the loading process, a loading animation will be displayed in the lower left corner of the Scene window.
The block mesh will switch LOD according to the camera position. You need to stay connected to the network during use to avoid LOD switching failures.
When the loading or LOD switching fails, the boundaries of the meshes that failed to load in the Scene window will display warm-colored gizmos. Detailed error information will be displayed in the Console window.
After solving the problem, you can click the Retry button to reload.
After the mesh is loaded, it will be cached locally. The cache path is:
var cachePath = Path.Combine(Application.persistentDataPath, "MegaStudio/cache")
Show/Hide
Click the Mesh checkbox to show/hide the mesh of the current group. This option is selected by default after the mesh is loaded.
Showing/hiding the mesh will not affect the rendering position of the 3D content, nor will it affect the state of the block node.
Boundary Gizmo
Click the Mesh Bounds Gizmo checkbox to show/hide the mesh boundary gizmo of the current group. This option is disabled by default.
Gizmos of different colors represent different LODs. Cold colors represent meshes that have been loaded, and warm colors represent meshes that have not been loaded (including loading failures).
Collision Detection
If you need to use ray detection to interact with the mesh, you need to configure the Collider Mesh option. This option is set to None by default, which means ray detection is not supported.
Export
Click the Export button to export the mesh data of the current group.
| Name | Description |
|---|---|
| Export LODs | Select the LOD precision of the model to be exported. The smaller the number, the lower the clarity. Multiple selections are available when Merge mesh is not checked. Only single selection is available when Merge mesh is checked. |
| Export Raw Data | Whether to export the raw data. The raw data may not be loaded in some software (such as blender) because these software do not support some gltf extensions. |
| Export Textures | Whether to export the textures. If you only need to export the model for occlusion or collision detection, you can not export the textures. |
| Format | Whether the format of the exported single file is glb or gltf. |
| Merge mesh | Whether to merge all meshes into one file for export. It is only available when a single LOD is selected. The merging process and the merged mesh require more video memory. |
| Export | Click to start exporting. |
During the export process, a progress bar will be displayed below the Mesh checkbox.
After the export is completed, you will see a pop-up window prompt of Completed.
Panorama
The panorama markers and panorama data are stored under the tool node and only exist in the editor mode. They will not be packaged into the final application.
Basic Information
The panorama clarity information will be displayed next to the Panorama Preview Marker, including SD (standard clarity) and HD (high clarity). Generally, the services that are opened by default provide panoramas with SD clarity. Panoramas with high clarity need to be obtained by contacting the business.
Some data does not support panoramas. In this case, Data not supported will be displayed next to the Panorama Preview Marker.
Marker Points
Click the Panorama Preview Marker checkbox to show/hide the panorama preview marker points. This option is disabled by default after the mesh is loaded.
The panorama preview marker points will be displayed in the Scene window.
After clicking a marker point, the MegaPanorama window will be opened. After clicking different marker points, the content of the MegaPanorama window will immediately switch to the corresponding panorama.
Panorama Window
After clicking a marker point, the MegaPanorama window will be opened, and the panorama corresponding to this marker point will be displayed.
The MegaPanorama window is also a kind of Scene window. You can use the right mouse button to drag to rotate the view. Other controls such as zooming and moving are disabled in this window.
When the Mesh is opened, the display effect of the MegaPanorama window will maintain the occlusion based on the mesh spatial model.
Tip
- After the editor enters the play mode, this function is still available, but the accuracy of the occlusion based on the mesh spatial model is affected by the disabled LOD switching.
You can also click other marker points in the MegaPanorama window, and the content will immediately switch to the corresponding panorama.
Diagnostic Information
Click the Diagnosis Info button to export diagnostic information. The diagnostic information includes the basic information of the current block, the service information where the block is located, etc.
Important
When submitting a problem to EasyAR, it is recommended to attach the diagnostic information to quickly locate the problem.