Veróse 😈🌹

The main difference I try to tell my clients is that VTS native tracking guestimates your mouth shape while vbridger actually knows it. VTS + iphone mouthshapes are estimated with how open your mouth (more so the jaw?) is on a scale of 0 to 1, how much youre frowning/smiling overall from a scale of -1 to 1, and mouth x (mouth swishing) on a scale of -1 to 1 -- some riggers may have additional expression modifiers, but thats all the input native tracking provides for the mouth (*minus lipsyncing params) This means if youre chewing food for example, it will open your mouth and move your jaw as if you're opening your mouth fully when it sees your jaw moving. The mouthsmile param also means mouth corners do not move independently, like some vbridger configs do. Vbridger actually looks for and tracks your individual mouth shapes. With perfectsync and more advanced methods, Vbridger actually can tell the left and right sides of the mouth apart, and reflect their smile/frown/opening independently. It can track mouth shapes such as funneling (oo sound), puckering, flattening, scrunching your mouth upwards, and more. With that, vbridger can accurately reflect your mouth being closed and jaw being open, as it is irl when you chew. Or you only opening or smiling on one side of your mouth, as in an IRL smirk for example. I'm pretty sure from my understanding any ARkit param (which there are many, this tech is used in Apples animoji, among other things) can be tracked and applied to a rig, so vbridger rigs can get very detailed and reflect the irl mouth significantly better than VTS on its own can - even if the VTS rig is extremely well made, it simply will never be 1:1 like you could hypothetically get Vbridger to be.