# Issue  

When using ImageTracking, if we attempt to recognize the same marker multiple times, the recognition rate significantly drops from the second attempt onward.  

Keeping the ImageTracking feature constantly enabled causes the app to slow down, so we turn it ON/OFF only when recognition is needed.  

1. App is launched  
2. When marker recognition is needed, we set `ARTrackedImageManager.enabled = true` to enable the ImageTracking feature  
3. When the marker is recognized, and `ARTrackedImagesChangedEventArgs.added` is triggered in the `ARTrackedImageManager.trackedImagesChanged` event, we set `ARTrackedImageManager.enabled = false` to disable the ImageTracking feature  
4. Steps 2 and 3 are repeated  

Using this method, the first marker recognition works smoothly, but from the second time onward, the marker is almost never recognized.  

If we change the position of the marker, it can be recognized again, which suggests that some internal caching might be the cause.  

We have tried various ways to clear this cache, but the issue has not been resolved.  

As a workaround, if we wait for `ARTrackedImagesChangedEventArgs.removed` before setting `ARTrackedImageManager.enabled = false`, the marker continues to be recognized properly even after the second time.  

However, to trigger `ARTrackedImagesChangedEventArgs.removed`, the user has to significantly move their gaze away from the marker, which is quite unreasonable to expect from users.  

Is there a way to set `ARTrackedImageManager.enabled = false` when `ARTrackedImagesChangedEventArgs.added` is triggered, **without** causing a drop in recognition rate from the second time onward?

# Environment

Device: NTT QONOQ, MiRZA

Spaces AR SDK 1.0.1 

Dual Render Fusion

Dear Andriy,

Thank you for your prompt response.

I would appreciate it if you could provide additional details or further guidance about the steps I should take next, as I need more information to proceed.

Best regards,

Kei Nomoto