Log in or register to post comments

Another bug with GetTrackableBehaviours()

January 26, 2013 - 7:55am #1

Vuforia SDK Version: vuforia-unity-android-ios-2-0-30.unitypackage -

Description with steps to reproduce: Create frame markers at runtime using the code snippet here:
https://developer.vuforia.com/resources/dev-guide/trackable-details-unity

In this case, this doesn't work:
StateManager stateManager = TrackerManager.Instance.GetStateManager();
foreach(TrackableBehaviour tb in stateManager.GetTrackableBehaviours()){

So the marker state (tracked or lost) cannot be read. If frame markers are added in the Unity editor instead, it does work. -

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

Mobile OS and Version: NA -

Mobile Device Manufacturer and Model name: NA -

Do the Vuforia Sample Applications show the same behavior?:

Another bug with GetTrackableBehaviours()

March 2, 2013 - 3:44am #10

Thanks. It works now.

Another bug with GetTrackableBehaviours()

March 1, 2013 - 2:17am #9

Hi Elecman,

quick update: Vuforia 2.0.31 is out. It should include the fix for your issue.

 

Another bug with GetTrackableBehaviours()

February 1, 2013 - 5:15pm #8

Thanks. 

David send me a temporary fix for this. With the example here
https://developer.vuforia.com/resources/dev-guide/trackable-details-unity

Add these lines at the end where the code generated marker is generated. These only have to be called once if multiple markers are generated.

StateManagerImpl stateManager = (StateManagerImpl)TrackerManager.Instance.GetStateManager();
stateManager.AssociateMarkerBehaviours();

 

Another bug with GetTrackableBehaviours()

January 30, 2013 - 1:50am #7

Just a quick update: I've got confirmation that the issue has been addressed and the fix should be included in next maintenance release (expected relatively soon).

 

Another bug with GetTrackableBehaviours()

January 29, 2013 - 12:47am #6

Correct.

Another bug with GetTrackableBehaviours()

January 28, 2013 - 11:38pm #5

And with ImageTargets this would be ImageTargetBehaviour I presume?

Another bug with GetTrackableBehaviours()

January 28, 2013 - 8:30am #4

Hi, you should use MarkerBehaviour if you need information that are specific to the Marker (such as the MarkerID for instance), while you can simple use TrackableBehaviour for more general (less specialized) info, like the trackable ID, etc.

 

Another bug with GetTrackableBehaviours()

January 28, 2013 - 8:09am #3

Ok, great. In any case, I am not sure whether I should use TrackableBehaviours or MarkerBehaviours to get information (ID, tracking or not) from frame markers when I create them in code. So far I have been unable to get code generated frame markers to work in Vuforia. If you can provide a working example, that would be great.

Thanks

Another bug with GetTrackableBehaviours()

January 28, 2013 - 6:20am #2

This issue is being tracked and we are looking into it, thanks for the report.

Log in or register to post comments