-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
current platform (OSXeditor) not supported by wikitude unity plugin #15
Comments
Hi @samshool , the "current platform (OSXeditor) not supported by wikitude" error is to be expected! Wikitude tracking does not work in the editor, it only works once you build, and that's why we created the Live Preview App: https://developer.mirareality.com/docs/mira-live-preview If you're having issues tracking when building to a phone, make sure you have the correct bundle ID: "com.mirareality.example" |
I pulled down the latest code off GitHub and it appeared to resolve my issues of getting the Wikitude tracking to work. I think it was a Wikitude Api license. ... Download the latest code and recheck your project settings... or download it fresh as a zip file... it will work then. |
by latest code u mean the same one im using 0.7.1 release on jan3? i tried again with the right project settings...im expecting it to show me a rectangle to locate the tracking image, and then once i place it over the tracking image my object should appear....instead my object appears right away , never prompts me for tracking like in the demo scenes. And it attached to camera no 6DOF..i even tried copying pasting the correct license... |
It appears the issue was resolved for my issue. I also got Vuforia running with the front facing camera. Thanks, |
Brief description of issue:
___on building i get this warning message "current platform (OSXeditor) not supported by wikitude unity plugin"....im using unity 2018.1.0f2 on mac OS 10.13.4...so basically on building the app to the iphone i see my asset already floating in space....anyone else had this issue?!
This issue was found on:
*Mac OS used 10.13.4 High Sierra
How to reproduce the issue:
Additional comments:
Error messages or logs
The text was updated successfully, but these errors were encountered: