Hi there,
my colleagues created an application that recognizes multiple markers and shows an image on the screen based upon which marker is scanned. This works perfectly on Android, but with iOS we are experiencing a weird result.
Everything works fine if we run the camera view and then move in the marker from any side to the camera view. It is recognized almost instantly and the application show the correct image on the next view. If we then take away the marker, go back from the image view to the camera view and bring it back in front of the camera, the detection works again as it should, so no problem there.
However, if we keep the marker in place in front of the camera and then return from the image view back to the camera view, the SDK takes a bit longer to detect the marker and almost every time an incorrect marker is detected. This is only on iOS, on Android this works as it should.
Do you have any idea on what might be causing this? Is this a known problem?
Thank you in advance,
Andy
- Development OS (Mac OS X, Windows, Linux): iOS - Mobile OS and Version: iOS 6, 7 - Mobile Device Manufacturer and Model name: Apple iPad - Do the Vuforia Sample Applications show the same behavior?: unsure
Second scan detects wrong marker
Please try to replicate the problem using the original Vuforia samples, as this is the only way to be sure that there might be a problem, particularly with something as basic as Image Recognition.
Are you using Framemarkers or Image Targets?
N