{"action":"created","issue":{"url":"https://api.github.com/repos/artoolkit/arunity5/issues/34","labels_url":"https://api.github.com/repos/artoolkit/arunity5/issues/34/labels{/name}","comments_url":"https://api.github.com/repos/artoolkit/arunity5/issues/34/comments","events_url":"https://api.github.com/repos/artoolkit/arunity5/issues/34/events","html_url":"https://github.com/artoolkit/arunity5/issues/34","id":121040250,"number":34,"title":"Mobile tracking issues","user":{"login":"0bl1v1on","id":16210578,"avatar_url":"https://avatars.githubusercontent.com/u/16210578?v=3","gravatar_id":"","url":"https://api.github.com/users/0bl1v1on","html_url":"https://github.com/0bl1v1on","followers_url":"https://api.github.com/users/0bl1v1on/followers","following_url":"https://api.github.com/users/0bl1v1on/following{/other_user}","gists_url":"https://api.github.com/users/0bl1v1on/gists{/gist_id}","starred_url":"https://api.github.com/users/0bl1v1on/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/0bl1v1on/subscriptions","organizations_url":"https://api.github.com/users/0bl1v1on/orgs","repos_url":"https://api.github.com/users/0bl1v1on/repos","events_url":"https://api.github.com/users/0bl1v1on/events{/privacy}","received_events_url":"https://api.github.com/users/0bl1v1on/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-12-08T16:08:04Z","updated_at":"2015-12-08T16:13:29Z","closed_at":null,"body":"I have a problem with the Unity ARToolKit 5.3.1 plugin on mobile devices specifically. \r\n\r\nWhen running in OSX on a iMac, recognition and tracking is reliable using the built-in camera. (640x480) However, when building to a mobile device (tested on an iPad Air and a Sony Xperia Z) performance is terrible.\r\n\r\nGenerally, initial detection is difficult and usually requires isolating one marker against a plain background. After detection, tracking is unpredictable - it will usually track for some time before losing track, and requiring redetection (which is, as I said, unreliable).\r\n\r\nAs I said, running in Editor within Unity does not produce these problems, nor were these problems present in ARToolkit 5.2.2."},"comment":{"url":"https://api.github.com/repos/artoolkit/arunity5/issues/comments/162932028","html_url":"https://github.com/artoolkit/arunity5/issues/34#issuecomment-162932028","issue_url":"https://api.github.com/repos/artoolkit/arunity5/issues/34","id":162932028,"user":{"login":"wallywyyoung","id":407574,"avatar_url":"https://avatars.githubusercontent.com/u/407574?v=3","gravatar_id":"","url":"https://api.github.com/users/wallywyyoung","html_url":"https://github.com/wallywyyoung","followers_url":"https://api.github.com/users/wallywyyoung/followers","following_url":"https://api.github.com/users/wallywyyoung/following{/other_user}","gists_url":"https://api.github.com/users/wallywyyoung/gists{/gist_id}","starred_url":"https://api.github.com/users/wallywyyoung/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wallywyyoung/subscriptions","organizations_url":"https://api.github.com/users/wallywyyoung/orgs","repos_url":"https://api.github.com/users/wallywyyoung/repos","events_url":"https://api.github.com/users/wallywyyoung/events{/privacy}","received_events_url":"https://api.github.com/users/wallywyyoung/received_events","type":"User","site_admin":false},"created_at":"2015-12-08T16:13:29Z","updated_at":"2015-12-08T16:13:29Z","body":"Are you using the same datasets from 5.2? Our data format was changed, which is why there is no FSET2, but now there is an FSET3."}}