Diagnose and fix: content not displayed

This article addresses common issues where virtual content cannot be displayed in 3D object tracking. It provides systematic troubleshooting methods and improvement suggestions to help developers quickly locate and resolve problems.

Common causes and troubleshooting methods

Content not being displayed usually involves object recognition failure, feature implementation errors, or permission restrictions. The following are the main causes and troubleshooting steps:

Object recognition failure

Symptom: after the camera points at the target object, virtual content does not appear at all. Troubleshooting:

• Check model quality: ensure that the 3D model and object meet the file format, texture, geometry, and other requirements in model preparation.
• Check the target object: ensure that the target object's surface has no reflective or mirror-like material.
• Check logs: check application logs and confirm whether the target model was loaded successfully.

Improvement suggestions:

• Optimize the model: ensure that textures are rich enough and the geometry has no holes.
• Check logic: ensure that the application has correctly loaded the target model. If loading fails, refer to target loading failure for inspection and repair.

Feature implementation errors

Symptom: the object has been recognized, but virtual content is not displayed or its position is abnormal.

• Unity
• Native

Troubleshooting:

• Check ObjectTarget configuration:
  • Check whether it points to the correct file in the StreamingAssets folder according to the Source type.
  • Check whether Scale has been modified according to the actual size of the object. For example, if the BoundingBox size calculated from the model file is 10 x 10 x 30, and the actual object size is 0.1m x 0.1m x 0.3m, then Scale should be set to 0.01.
• Confirm prefab hierarchy:
  • Virtual content must be at the same level as the target 3D model, and both must be child nodes of ObjectTarget. Virtual content must not be disabled.
  • The Rotation property of the target 3D model needs to set the Y direction to 180.
  • The placement of virtual content must be completely around the position of the target 3D model.

Improvement suggestions:

• Reset configuration: delete and recreate ObjectTarget in the scene, drag the prefab according to the specification, and bind the 3D model.
• Check logs: search for errors related to ObjectTargetController, such as fail to load target data.

Permission issues

Symptom: it worked normally at first, but content disappears after running for some time. Troubleshooting: Confirm whether you are in one of the following cases:

• Using an XR headset
• Using a custom camera
• Using AR Engine/ARFoundation on a phone

If you are in one of the above cases, you may be using a trial License.

Improvement suggestions:

• Use an official License.

Virtual content issues

Symptom: content is displayed normally at first, but cannot be seen when the camera is very close to or far away from the target object. Troubleshooting:

• Check near and far clipping settings: ensure that the near and far clipping settings used when rendering virtual content are within a reasonable range.
• Check content model size: when the content model is too large, getting close to the target object may cause clipping through the model and make the content invisible; when the content model is too small, moving away from the target object may make it too small to see clearly.

Improvement suggestions:

• Set appropriate near and far clipping.
• The physical size of virtual content should be appropriate compared with the target object.

Summary and best practices

Content not being displayed is usually caused by the object 3D model, program implementation, permissions, or the content itself. Troubleshooting is recommended in this order:

1. Check whether the License is an official version;
2. Check whether the virtual content itself is appropriate;
3. Confirm target 3D model quality;
4. Confirm whether there are issues in program implementation or development configuration.

If the problem persists, provide log files, screen recordings, and other materials through the EasyAR official forum or technical support for further analysis.