Log in or register to post comments

Trackable Astronaut NO_POSE -- UNKNOWN

November 24, 2019 - 9:11am #1

Vuforia SDK Version: 8.5.9 -

Description with steps to reproduce: Hi, after uprading from 8.1.12 to 8.5.9 I can no longer track image targets in the unity editor. I get the following message:

Trackable Astronaut NO_POSE -- UNKNOWN
DefaultTrackableEventHandler:OnTrackableStateChanged(Status, Status) (at Library/PackageCache/com.ptc.vuforia.engine@8.5.9/Vuforia/Scripts/DefaultTrackableEventHandler.cs:58)
DefaultTrackableEventHandler:Start() (at Library/PackageCache/com.ptc.vuforia.engine@8.5.9/Vuforia/Scripts/DefaultTrackableEventHandler.cs:34)

However running it on my Android device works. Using Unity 2019.3.0b11
Any ideas how I could debug this? Found nothing with google. -

Development OS (Mac OS X, Windows, Linux): Windows 10 -

Mobile OS and Version: Android 9 -

Mobile Device Manufacturer and Model name: Huawei Mate 20 Pro -

Do the Vuforia Sample Applications show the same behavior?: Yes, I tested it with the sample files from the unity asset store.

Trackable Astronaut NO_POSE -- UNKNOWN

November 25, 2019 - 5:19am #2


I could be related to your print-out of the Image Target, are you using the print-out when testing the image target from the Editor?

Below some hints:

There are a few things to keep in mind if your image will not detect:

1. Import the dataset into Unity: Assets->Import Package->Custom Package...

2. Select the dataset in the ImageTarget prefab: ImageTarget->Image Target Behaviour (Script)->Type = Predefined, select Database and Image Target you want to be detected/tracked

3. Be sure that when building your app, you have selected the scene with the ARCamera+ImageTarget prefab

4. Always print the image that was uploaded to the portal to the exact same aspect ratio. Any stretching or altering of the image will cause it not to be detected. Some printers default to "stretch to fit", which can change the aspect ratio.

5. Check the size values you are using when uploading Targets to the Vuforia Target Manager. Note there is specific language used in the dialogue box that says Vuforia uses meters as the default unit scale. Incorrect target sizes could affect either our detection/tracking algorithm, or the augmentation in that it so large that it cannot be viewed because it extends beyond the clipping plane.

6. Review ADB logs to see if Vuforia detects and tracks the target. If the target is being tracked but the augmentation cannot be seen, this could indicate an issue with the clipping plane.

Note that the console message "trackable lost" does not indicate that something is wrong.

Thank you.

Vuforia Engine Support

Log in or register to post comments