How to clearly communicate visual anomalies
This section introduces how to clearly communicate visual anomaly issues to provide effective evidence for problem localization.
Describe device information
The core purpose of providing device information is to troubleshoot hardware compatibility issues.
Since AR positioning performance is highly dependent on device hardware configuration (e.g., camera, sensors) and system version, it is essential to accurately provide the mobile device model and system version information used.
Check content placement
The core purpose is to confirm whether deviation issues are caused by improper content placement. When AR digital content appears with positional deviations, the cause is often not a failure in the AR positioning algorithm, but rather imprecise placement of virtual content, such as deviations in model coordinate settings. Therefore, before submitting related feedback, it is necessary to verify whether the digital content aligns precisely with the positioning reference.
❌ Bad example: The placement of the cube does not follow a clear, specific position, making it impossible to serve as an effective reference for judging visual errors during actual experience.
Verify environmental changes
Verify environmental changes to determine whether positioning anomalies are affected by environmental factors. AR positioning performance relies on the physical environment. Differences between the testing environment and the image-capturing environment can easily cause positioning deviations or poor performance. Therefore, ensure that both environments are fundamentally consistent to avoid positioning failures caused by environmental discrepancies.
Precisely describe the issue
First clarify the expected presentation effect, then describe the actual presentation effect, and accurately annotate specific details of positional deviations. Simultaneously, provide a detailed explanation of the actual positioning anomalies of the AR digital content, emphasizing the exact time points when deviations occur in the video.
✅ Example: The expected effect is for the panda to move along the road path; in the actual effect, at the 55-second mark, the panda's movement path deviates, and its trajectory leads toward the grassy area.
❌ Bad example: The panda is off course.
Note
Capture anomalies from the video and mark the time and phenomenon to help others quickly locate the issue.
Provide reproduction data
When submitting an issue, simultaneously provide reproduction data. To confirm whether the data can effectively reproduce the issue, refer to this article: Confirm recorded data can reproduce your issue.
The core of this step is to ensure that the data you provide can precisely reproduce the described anomaly. It is recommended to self-verify before submission, confirming that the recorded data can fully reproduce the issue encountered.
Related topics
Collect mobile screenshots and screen recording data