-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
v3 Release: NFT + code cleaning + doc update #705
Conversation
…jsartoolkit5-NFT # Conflicts: # three.js/examples/test-runner.html
…jsartoolkit5-NFT # Conflicts: # three.js/experiments/deadreckoning.html
…ting-jsartoolkit5-NFT
Any ETA on this? When do you guys think image tracking will be available in arjs? |
Very difficult to say, but me and @nicolocarpignoli are very motivated that this happens. actually we have an issue testing on smartphone device: while on landscape mode it detect and track the NFT marker, instead in portrait mode this not happens. Probably an iusse with ratio or related thing, but hard to sort out for the Ar.js complexity. Anyway we hope to solve this soon !! 😄 🎉 |
If anyone is will to help is very welcome, to speed up the process |
# Conflicts: # aframe/build/aframe-ar.js # aframe/build/aframe-ar.min.js # three.js/build/ar.js # three.js/build/ar.lean.js # three.js/build/ar.lean.min.js # three.js/build/ar.min.js # three.js/examples/nft.html # three.js/src/threex/threex-armarkercontrols.js # three.js/vendor/jsartoolkit5/js/artoolkit.worker.js
It now works on aframe side and three.js side (after mergin v3-working branch). |
That's a great Progress indeed, let's improve it now! |
Can you please re-open this PR on the new dev branch? thank you |
sorry had to clean the dev branch |
From #674 (comment) #674
What kind of change does this PR introduce?
This PR want to test the new jsartoolkit5 from kalwalt/jsartoolkit5#1 with the new changes especially the NFT part.
🖼 This will eventually make AR.js capable of detect and track 2D images.
https://twitter.com/nicolocarp/status/1204841439160684549
Could be raise some bugs and incompatibilties between the code. It is more a test...
Can it be referenced to an Issue? If so what is the issue # ?
From jsartoolkit5 repo: PR kalwalt/jsartoolkit5#1
From AR.js issues:
also, a repo cleaning will help for: #433
How can we test it?
Just test the examples and tell us what happens...
Summary
Does this PR introduce a breaking change?
Nope, it will remove old code, but unnecessary. It will add NFT feature.
Please TEST your PR before proposing it. Specify here what device you have used for tests, version of OS and version of Browser
Other information
I uploaded the new jsartookit5 libs and build the AR.js libs with makefile.
Progress