Hi,
after I send the billing team a mail and vuforia support once more outdone themself by giving me a generic message, which said I should write it into the forum, I have the following problem (I´ll send it to the production support as well, maybe I´m lucky) :
here is my original message:
"
Hello,
We are experiencing some odd behaviour, which is especially strong this month, even though it might have been the case in the last months, too.
Our Tracking-Numbers (Recos) seem to be much higher than possible. Therefor we got the 80% warning yesterday. We are currently checking our code to look for any holes, but I´d say we get at least every tracking double!
I didn´t see any posts in the forum which suggests, that this could be a common problem. Did you experience any similar problems in the past? If you check out the reco-times in your database (which I guess you have in more detail) do you see, that the trackings always come in pairs or bundles within 1 second or something like that?
We really need support on this and I write to you (even though you might redirect it to tech-support) in order to ask, if there can be made a exception this month concerning the extra-trackings which we probably will have, since the recos are gathered by a faulty behaviour.
Please get in contact with us about this matter.
Thanks in advance
"
Until now we didn´t find any point in the code which hints that there might be additional tracking querys. As soon as a tracker ist found (CloudRecoEventHandler-OnNewSearchResult) we disable the Tracking by: cloudRecoBehaviour.CloudRecoEnabled = false;
I checked the state of this field during the show and I dont get any double DebugLogs.
Is there somebody who has some kind of hint for me?
Best regards
Maik
Too many recos!
Hi
thanks for answering.
I call
mImageTracker.TargetFinder.ClearTrackables (false);
and
Too many recos!
By the way:
The new regulation, that ALL posts and replys have to be reviewed is absolutly not acceptable!
Too many recos!
I´m using version 4.2.3. Therefor it should already be filtered, if I understood you correctly. (Even if I´d use SDK5 I would have overwritten the default behaviour).