-
Notifications
You must be signed in to change notification settings - Fork 92
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
Not able to get tracking to work on HL1, VS2017 #54
Comments
more data from the v0.2 release tag with unity 5.6, VS2017v15.0, on HL1: Looking in the debug logs, I'm getting
but I do have the .dll file in plugins/x86. The app does ask me for camera permissions, but after accepting, the white light associated with the frontfacing camera is not on. I have tried both |
Are you using .NET backend or IL2CPP? |
IL2CPP when I was using v0.3. I can't select the .NET backend in v2019.2.21f1 |
Hi Peter. Glad to see your post. I'm having the same issue as well. Can I know if you manage to solve it or any potential trouble-shooting? Thanks! |
Hello! Thanks for publishing this toolkit.
I am having issues getting it to track any marker (printed or on my computer screen). I have tried both the single (with both the kanji and hiro tags) and the multi.
I see no errors during build or deploy, and I can see the render fps stats. I can also see the rainbow cube, but it is just rendering in its static location just behind the starting camera coordinates. Do you have any tips on debugging this?
As some additional detail, I am using unity v2019.2.21f1, but I needed to manually change my min platform version from 10.0.18362.0 to 10.0.17763.1518 to get it to deploy (and change build tools from v142 to v141). I'm not sure if that would cause my issue, but I believe I have to set those parameters that way to get it to deploy on HL1.
Update:
I also tried the v0.2 release tag of this repo with unity 5.6.0f3 and VS2017 15.2, and also cannot recognize the markers there.
Thanks a bunch!
The text was updated successfully, but these errors were encountered: