Facemesh v2

[abernier]

Note Merged
see <Facemesh> doc

Why / What

<Facemesh> is now looking in some direction:

We can for example gets the direction with the ref-api:

meshRef.current.localToWorld(new THREE.Vector3(0, 0, -1))

facemeshv2.mov

Checklist

• Documentation updated
• Storybook entry added
• Ready to be merged

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
drei	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 10, 2023 6:52pm

[codesandbox-ci]

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:

Sandbox	Source
musing-burnell-1urlby	Configuration
Ground reflections and video textures	Configuration
arc-x-pmndrs-colors	Configuration

[krispya]

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)

[abernier]

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 ;)

[github-actions]

🎉 This PR is included in version 9.67.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀