I can't reliably reproduce it, but in some cases the same marker is shown on two devices at the same time. This naturally leads to erratic behaviour. One device starts flickering and rapidly alternaties between two different states of the UI. The other one is blocked showing the ID without being recognized and does not react anymore. Closing the browser on the blocked device usually solves the problem and also stops the flickering on the other device.
I witnessed this most frequently when using the DocReader demo application and testing it with 3 tablets. It seems that this happens only for the very last marker in TagDefinitions.txt, i.e. with the highest ID, The shape of this marker does not seem to matter, it rather seems that there is a problem when the tracking reaches the end of TagDefinitions.txt. (Just thought that it could be an empty line at the end of that file).
I can't reliably reproduce it, but in some cases the same marker is shown on two devices at the same time. This naturally leads to erratic behaviour. One device starts flickering and rapidly alternaties between two different states of the UI. The other one is blocked showing the ID without being recognized and does not react anymore. Closing the browser on the blocked device usually solves the problem and also stops the flickering on the other device.
I witnessed this most frequently when using the DocReader demo application and testing it with 3 tablets. It seems that this happens only for the very last marker in TagDefinitions.txt, i.e. with the highest ID, The shape of this marker does not seem to matter, it rather seems that there is a problem when the tracking reaches the end of TagDefinitions.txt. (Just thought that it could be an empty line at the end of that file).