Diagnosis and repair: content not displayed

This article provides systematic troubleshooting methods and improvement suggestions for common issues where virtual content fails to display in 3D object tracking, helping developers quickly locate and resolve problems.

Common causes and troubleshooting methods

Content not displaying usually involves object recognition failure, implementation errors, or permission restrictions. Below are the main causes and troubleshooting steps:

Object recognition failure

Phenomenon: Virtual content does not appear at all after the camera aligns with the target object.
Troubleshooting methods:

• Check model quality: Ensure the 3D model and object comply with file format, texture geometry, and other requirements in model preparation.
• Check target object: Ensure the target object’s surface has no reflective or mirror-like materials.
• Check logs: Review application logs to verify if the target model loaded successfully.

Improvement suggestions:

• Optimize the model: Ensure textures are sufficiently rich and the geometry has no holes.
• Check logic: Confirm the application correctly loaded the target model. If loading fails, refer to the target loading failure section for checks and fixes.

Function implementation error

Phenomenon: The object is recognized, but virtual content is not displayed or appears in abnormal positions.

• Unity
• Native

Troubleshooting methods:

• Check ObjectTarget configuration:
  • Verify the Source points to the correct file in the StreamingAssets folder based on its type.
  • Ensure Scale is modified according to the actual object’s dimensions (e.g., if the BoundingBox size calculated from the model file is 10x10x30, but the actual object size is 0.1m x 0.1m x 0.3m, set Scale to 0.01).
• Confirm prefab hierarchy:
  • Virtual content must be at the same level as the target 3D model, both as child nodes of ObjectTarget. Virtual content must not be disabled.
  • The target 3D model’s Rotation property must set the Y axis to 180.
  • Virtual content placement must fully surround the target 3D model’s position.

Improvement suggestions:

• Reset configuration: Delete and recreate the ObjectTarget in the scene, drag prefabs into the hierarchy following specifications, and bind the 3D model.
• Check logs: Search for ObjectTargetController errors, such as fail to load target data.

Permission issues

Phenomenon: Content disappears after functioning normally for a period.
Troubleshooting methods:
Confirm if you fall into one of these scenarios:

• Using XR headsets
• Using custom cameras
• Using AR Engine/ARFoundation on mobile devices

If in any of these scenarios, you may be using a trial license.

Improvement suggestions:

• Use a formal license.

Virtual content issues

Phenomenon: Content displays normally initially but becomes invisible when the camera is very close to or far from the target object.
Troubleshooting methods:

• Check near/far clipping settings: Ensure near and far clipping planes for rendering virtual content are within reasonable ranges.
• Check content model size: Excessively large content models may cause clipping when close to the target object; overly small models may render too tiny to see when distant.

Improvement suggestions:

• Set appropriate near/far clipping values.
• Ensure virtual content’s physical size is proportionate to the target object.

Summary and best practices

Content display issues typically stem from 3D object models, program implementation, permissions, or the content itself. Recommended troubleshooting sequence:

1. Check if the license is formal.
2. Verify if virtual content is appropriate.
3. Confirm target 3D model quality.
4. Identify program implementation or development configuration issues.

If problems persist, submit log files, screen recordings, etc., via the EasyAR official forum or technical support for further analysis.