Unity-Technologies / arfoundation-samples

Example content for Unity projects based on AR Foundation
Other
2.98k stars 1.11k forks source link

[Question] One of the devices can't locate image targets, why? #1077

Closed AytoMaximo closed 9 months ago

AytoMaximo commented 1 year ago

I have 5 "iPad Pro 11" devices. I've installed the same Unity game app with ARFoundation module on all of them. All of the iPads work fine and are capable of image tracking, however, one of them can't see the image target at all.

All of the iPads were tested on the same target and in the same environment.

Does anyone have any hypotheses as to why this might be happening?

tdmowrer commented 1 year ago

Are they all running the same version of iOS?

AytoMaximo commented 1 year ago

Are they all running the same version of iOS?

Hi! All are iOS 15.1

andyb-unity commented 1 year ago

This sounds like a hardware failure. You could verify at runtime that the TrackedImageManager in your scene has a non-null subsystem: https://docs.unity3d.com/Packages/com.unity.xr.arfoundation@5.0/api/UnityEngine.XR.ARFoundation.SubsystemLifecycleManager-3.html#UnityEngine_XR_ARFoundation_SubsystemLifecycleManager_3_subsystem

If so, at that point image detection is handled by iOS directly.

AytoMaximo commented 1 year ago

This sounds like a hardware failure. You could verify at runtime that the TrackedImageManager in your scene has a non-null subsystem: https://docs.unity3d.com/Packages/com.unity.xr.arfoundation@5.0/api/UnityEngine.XR.ARFoundation.SubsystemLifecycleManager-3.html#UnityEngine_XR_ARFoundation_SubsystemLifecycleManager_3_subsystem

If so, at that point image detection is handled by iOS directly.

Apologies for the delayed response. I initially thought it was a phantom hardware failure, but the problem recurred when more iPads were purchased. The TrackedImageManager certainly has a non-null subsystem: I've checked the logs.

However, I captured a screenshot and noticed that the camera feed is unfocused. Interestingly, it's also unfocused even in the native app. Therefore, in any case, it appears to be a technical defect.

image

andyb-unity commented 9 months ago

Closing this issue as a third-party defect. Feel free to re-open it if you have further questions.