Performance issues?

[NatanTechofNY]

Any reason why the game lags so bad and why frame drops?
Also, the game does not align the mouth correctly.

[stanchiang]

What device are you using? I need to optimize the video feed to boost fps. It works fine on my 6+. If I document the app more would you be interested in helping fix it with a pull request?

The mouth alignment functionality might be off if your not on a 6+. If you go to the game gallery.swift there is a bool called debugmode. Turning that on will load a debugging UI. You access it by swiping left on the camera. From there you can adjust the one called PPI up or down to get the mouth aligned. The problem comes from a buggy conversion between pixels and cgpoints. I have a constant set by that PPI debug var to compensate for the bug and it's tuned to each device. I had it working at one point but maybe it got messed up down the road.

[NatanTechofNY]

I am running on a 7+. If you document the app I can help you out. Just let me know when you do. Also make sure that the API calls to Segment do not interfere with the frames or performance. I would hold off on Segment Analytics till you have a steady working application.

[stanchiang]

There's also a difference in how the tracking works between the app store version and the one in master. This new one can track the face at more angles, but does more calculations so that also impacts performance. I just haven't been able to test the most up to date version on any devices other than my own.

[stanchiang]

Ok I'll let you know when I have more documentation. Good idea about the segment calls.

[stanchiang]

Instead of documenting everything, I stripped out all the unnecessary code into a boilerplate version for just the augmented reality functionality. http://git.io/fluidAR

In that app, if you go to the DebugView.swift you should see a getAdjustedPPI which is returning a constant based on the devices height. This was to compensate for my buggy pixel to point converter in my file CVFFaceDetect.mm called pixelToPoints.

You can try to debug root cause at the pixelToPoints function or tweak the getAdjustedPPI constants to fix the issue