I have a full AR frame marker App under iOS. The App was fully tested and ready for the App store under SDK 2.0.30. But the App store rejected because that SDK version still used UDID which is disallowed by Apple. I then upgraded to SDK 2.5.7 to pass the UDID requirement of Apple. I retested my App, and while it works for most frame markers, some frame markers are not detected. Frame marker 62 and 45 simply are not recognized. We use nearly all 512 in our process and App so it is critical that all frame markers are detectable and this solution is reliable.
I can recreate the issue easily. I recompile my App using 2.0.30 and all frames are recognized, but then I recompile under 2.5.7 and these frames are no longer recognized.
Please help ASAP. I'll accept a viable workaround. Maybe until a permanent solution is found, I can get access to the SDK upgrade that just fixed the UDID issue.
I have a deadline to meet to get the product into the App store.
Thanks in advance,
Steve Sykes
- Development OS (Mac OS X, Windows, Linux): Mac OS X - Mobile OS and Version: iOS version 6+ - Mobile Device Manufacturer and Model name: Apple - Do the Vuforia Sample Applications show the same behavior?: Yes the results are the same with the Frame Marker sample App. Frame 062 does not get recognized. I put in a breakpoint in the sample code to show when trackable hit. The breakpoint was triggered for Frame 000, 001, but failed and never triggered for frame 62.
Poor Frame Marker Recognition under 2.5.7
Are you saying that 45 and 62 were recognised in the previous SDK in the Vuforia sample?
N
Poor Frame Marker Recognition under 2.5.7
Yes, they are recognized immediately under SDK 2.0.30... In my App. I will test now under the Frame Markers App and reply again.
Poor Frame Marker Recognition under 2.5.7
The problem persist, but my initial test with the Vufura sample was flawed... It appears that any frame above 003 is not recognized by the App in any SDK. If you can send me an App sample that recognizes at least the first 75 Frame Markers then I will perform the test in both SDKs.
Poor Frame Marker Recognition under 2.5.7
Hi Steve,
Since yesterday both David and Alessandro have tested FMs with the sample on 2.5.7 and found no problems, particularly with markers 45 & 62.
Could you send me a link to your markers so I can take a look?
N
Poor Frame Marker Recognition under 2.5.7
I have attached frame 062. Frame 45 has a vendor name so I sent the basic frame that also fails.
Also were the tests conducted in an iOS environment, and if so can you tell me the device, the iOS version, etc. And any specific settings in your App that may affect my outcome.
Poor Frame Marker Recognition under 2.5.7
Anything that can explain why I can compile under 2.0.30 and the recognition works perfectly, and then recompile under 2.5.7 and the recognition does not work
Well, this I cannot explain.
Poor Frame Marker Recognition under 2.5.7
Thanks,
I will make these changes to the Sample App and test.
In the mean time, 2 related questions:
1. What is the timestamp on the libQCAR.a that you are using.
2. Is it possible to get access to SDK 2.0.32 if I need a temporary work-around.
Steve
Poor Frame Marker Recognition under 2.5.7
Poor Frame Marker Recognition under 2.5.7
Thanks for the response... Our QCAR assemblies match. Unfortunately I was hit with another priority yesterday so i did not have a chance to change and test the Sample App. I will attempt to do today.
RESOLVED: Poor Frame Marker Recognition under 2.5.7
GREAT NEWS... IT WAS COMPLETELY MY ERROR!!!
Poor Frame Marker Recognition under 2.5.7
Thanks for the update.
I am pleased for you, though not surprised that there is no error in Vuforia.