Arcore-unity-sdk: Augmented Images: Dynamically added images not appearing as trackables

Created on 4 Apr 2019  路  6Comments  路  Source: google-ar/arcore-unity-sdk

SPECIFIC ISSUE ENCOUNTERED

I'm encountering an issue (possible bug?) with runtime image detection.

Using session.SessionConfig.AugmentedImageDatabase.AddImage() with my texture (RBG24bit with Read/Write enabled) returns the index of the new image and the database count goes up.

However, when using my phone to actually scan the real world image, it never appears as a trackable when calling Session.GetTrackables( tempAugmentedImages, TrackableQueryFilter.All ); during my Update()

If the image is added to the database via the Unity Editor, then it works. But I'm dependent on using dynamic textures for this project.

This issue occurs regardless of whether the image database was created from scratch at runtime, or linked to in the editor.

The AddImage() call happens on a different frame from when the session and AugmentedImageDatabase are created, I read that can cause issues.

Anyone have any advice or willing to send a link to a confirmed working demo scene using dynamic image targets?

VERSIONS USED

  • Unity: 2018.3.0f2
  • ARCore SDK for Unity: 1.8.0
  • Device manufacturer, model, and O/S: Samsung Galaxy S8 (SM-G950U1)
  • ARCore: 1.8.190311076

ADDITIONAL COMMENTS

Also, if anyone has an example of adding images via multithreading, that would be awesome to see, I've never messed with Unity's Multithreading features and ARCore recommends we use it for this task.

All 6 comments

I'd love to see this solved.
I also have the same requirements, even tried with the binary imgtool , but no luck.

@vjleo : I'm at least happy to see that I'm not crazy and that others are having the same issue. Do you know of any other methods for informing the Google ARCore developers about this bug so this can get expedited or noticed?

The devs look at the issues raised here.

Probably there's a backlog, priority on bugs, features, importance.

My guess is that people try to develop with more advanced usage of the target images with the SDK and get frustrated, don't comment here and go find another solution.

As I said in another comment, target image needs attention.

Spatial functionality has gone very far and is stable.

same problem here

Bump!
Any response from the dev team?

same problem here is there any progress yet with the devs or am i missing something ..... also add image is returning -1 on editor and on android build

Was this page helpful?
0 / 5 - 0 ratings