Unity components that rely on 3D points now ignore tracking data for frames with high 3D fitting error.
This commit is contained in:
parent
ea735ffdde
commit
cf49ba5468
6 changed files with 13 additions and 6 deletions
|
|
@ -829,8 +829,11 @@ public class OpenSeeVRMDriver : MonoBehaviour {
|
|||
}
|
||||
|
||||
void RunUpdates() {
|
||||
if (openSeeExpression != null && openSeeExpression.openSee != null)
|
||||
if (openSeeExpression != null && openSeeExpression.openSee != null) {
|
||||
openSeeData = openSeeExpression.openSee.GetOpenSeeData(openSeeExpression.faceId);
|
||||
if (openSeeData.fit3DError > openSeeExpression.openSee.maxFit3DError)
|
||||
openSeeData = null;
|
||||
}
|
||||
if (initializeLipSync) {
|
||||
InitializeLipSync();
|
||||
initializeLipSync = false;
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue