ViewTracker 1.03 changelog:
ViewTracker 1.03 is here!! The performance improvements along with the more stable and responsive filtering combine to make tracking feel super smooth and natural.
Note to PS3 Eye users: an updated PS3 Eye driver has been posted.
The new camera configuration options allow you to specify a framerate and resolution. The default of 640x480 at 30 frames per second (fps) should be a good tradeoff in most situations. Higher resolutions use more system resources, and if your face occupies a region larger than 125x125 pixels ViewTracker scales it down internally anyway. Most cameras only allow up to 30 fps, but some cameras (I'm looking at you, PS3 Eye) allow up to 60 fps. That's wonderful because in good lighting conditions that can make for very responsive tracking, but higher frame rates do come with some tradeoffs. A higher frame rate means the camera has less time per frame to collect light, and this means noise levels will be higher. This makes for less accurate tracking that will require more smoothing. Another thing to keep in mind is ViewTracker uses a lot of CPU power per frame in order to make accurate predictions. It would be possible to reduce the accuracy and use less CPU power (therefor allowing a higher frame rate), but this would again just require more smoothing and defeat the purpose of having a higher frame rate to begin with. In order to have good accuracy at 60 fps, ViewTracker now makes use of up to 4 CPU cores. This can have a larger performance impact on your game, especially if your CPU has 4 cores or less. So long story short, I have found the better tradeoff is often to track at 30 fps. That said, if you have bright lighting and a powerful CPU, tracking at 60 fps is prettay nice.