If you use a Leap Motion, update your Leap Motion software to V5.2 or newer! Just make sure to uninstall any older versions of the Leap Motion software first.

If VSeeFace does not start for you, this may be caused by the NVIDIA driver version 526. To update VSeeFace, just delete the old folder or overwrite it when unpacking the new version. For those, please check out VTube Studio or PrprLive. Please note that Live2D models are not supported. If that doesn’t help, feel free to contact me, Emiliana_vt! If you have any questions or suggestions, please first check the FAQ. Running four face tracking programs (OpenSeeFaceDemo, Luppet, Wakaru, Hitogata) at once with the same camera input. In this comparison, VSeeFace is still listed under its former name OpenSeeFaceDemo. You can see a comparison of the face tracking performance compared to other popular vtuber applications here. For the optional hand tracking, a Leap Motion device is required. Capturing with native transparency is supported through OBS’s game capture, Spout2 and a virtual camera.įace tracking, including eye gaze, blink, eyebrow and mouth tracking, is done through a regular webcam. VSeeFace can send, receive and combine tracking data using the VMC protocol, which also allows support for tracking through Virtual Motion Capture, Tracking World, Waidayo and more. Perfect sync is supported through iFacialMocap/ FaceMotion3D/ VTube Studio/ MeowFace. VSeeFace runs on Windows 8 and above (64 bit only).

VSeeFace offers functionality similar to Luppet, 3tene, Wakaru and similar programs. The upshot is that if you asymmetrically scale an object (as opposed to its vertices) in Blender, then Blender and Unity will come to different conclusions about the normals that should accompany that shape.VSeeFace is a free, highly configurable face and hand tracking VRM and VSFAvatar avatar puppeteering program for virtual youtubers with a focus on robust tracking and high image quality. All Blender did was bake that distortion into the bones. In short, Blender hadn't distorted the mesh at all - I had, right at the start.

However, it seems that at some stage in the Blender->FBX->Unity workflow, the ability to cope with asymmetrically scaled normals is lost. This obliged Blender to similarly apply an asymmetric scale to the bones of the armature when parenting the rig to the mesh, in order to preserve its appearance. I tracked down the cause: in the very first edit I had made when sculpting the model (after adding and subdividing a cylinder primitive) I had accidentally scaled the object rather than the vertices to make the shape longer and narrower. I'm only accepting this answer rather than Aster17's because this answer explains what happened in this specific case in more detail. EDIT: The video posted by Aster17 includes a step correcting for object scale prior to export, along with many other steps, so refer to that for your exporting needs.

Fbx export unity