-
Notifications
You must be signed in to change notification settings - Fork 787
Facemesh v2
#1437
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
Facemesh v2
#1437
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 7531949:
|
cbe751f to
cf89b6e
Compare
Facemesh v2
883bf3d to
9e85de5
Compare
d983eff to
9e85de5
Compare
krispya
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's better to stick all these vectors into a useState callback. But also, instead of putting each in their own useState callback you can put them in one like this:
const [store] = useState(() => ({ vecA: new Vector3(), vecB: new Vector3(), vecC: new Vector3() }))
store.vecA.set(1,1,1)
I leave it with multiple states for now, but great technique to "pack" them together ;) |
|
🎉 This PR is included in version 9.67.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Why / What
<Facemesh>is now looking in some direction:We can for example gets the direction with the ref-api:
facemeshv2.mov
Checklist