-
Notifications
You must be signed in to change notification settings - Fork 114
FAQ & Troubleshooting
In this page are posted the more repeated questions by the users. If you have any problem/question, it could be already awnsered here!
Check both AITrack and Opentrack are running. Check that 1) there are pink points over your face and 2) check if the pink octopus is moving. If so, check in Opentrack you hace "Output" = "freetrack 2.0 Enhanced". If it's still not working, stop all the programs, restart the game and try again.
Check you have Input=UDP over network and Opentrack is using port 4242. If it is any other, you should 1) set it to 4242 (the default one) or 2)set AITrack to send data to the specific port you have in Opentrack (AITrack>Configuration>Use remote Opentrack client>Port =<YOUR PORT>).
Try other tracking model (AITrack>Configuration>Model type). Also check your lightning, you maybe are in a too dark/bright environment. Also, make sure your head rotation angle is not very extreme as it could confuse AITrack (you can solve it by adjusting your curves).
If that happens, that means your camera (or camera drivers) doesn't support setting custom FPS/Brightness/Exposure.
The most common reason of this could be due to having too much Smoothing on the Opentrack's Acella fitlering. If lowering it doesn't work, try disabling "Landmark stabilization" in AITrack.
Also, there have been some reports of Windows Game mode adding an artificial delay to AITrack or Opentrack. The root of the cause has not been found yet.
In order to access webcams the "WINDOWS MEDIA FEATURE PACK" is necessary. As some Windows don't come with it installed, maybe that's the cause of your problem. You can download it HERE.
Yes! There are lots of apps which let you use your phone as a webcam. One which works pretty well is DroidCam. However, their devs (and also I) encourage you to use it over USB because, even with perfect WiFi connection the video feed gets delayed from time to time.
Anything with more resolution than 224x224 should work well. The quality difference in the experience is given by the FPS. A camera with 60FPS support is ideal. I personally recommend the PS3 Eye cameras, as they are cheap and can reach up to 75FPS (also, AITrack has been developed mainly using one, so you can expect less bugs).
Well, FacetrackNoIR it's a great program, but it has a drawback: its age. It has been lying around for years and it's technology is getting obsolete. One of the main reasons I started AITrack development was because FacetrackNoIR didn't work in slightly low light conditions (thing that AITrack can do). If you have this problem, then you should check out AITrack.
You probably shouldn't. The main reason you could want to test this is that setting up your TrackIR can be a mess, even more if you have cables. Also, it's fragile, so you have a chance of breaking it. AITrack has not reached TrackIR's quality yet, but it's more than enough for casual use if you already have a TrackIR.
Those names refer to the three types of neural networks avilable to do the facial tracking. Roughly, Fast=Simpler and Heavy=More complex. The more complexity a neural network has, the more CPU it consumes, but also, the more resilient to low light/extreme head angles it can handle. Most users should be using the Fast one. You should only try Medium/Heavy if the pink points over your face are not being placed correctly