skeleton height from FAAST?

[Jeff]

What is the version number of FAAST that you are using?

I'm wondering if all the other tracked objects are off by the same amount. If so, you could do an initial calibration where the user's highest tracked object (head) and the lowest tracked object (foot) are visible to FAAST, and then figure out the difference. That should provide a loose approximation of the user's height. I'm not sure whether or not this would be accurate enough for your application.

[fivel_lab]

Thanks again, Jeff.

We're currently using v1.2 but I've tried all of the above with v1.0 and get the same problem.

I'm not sure whether your method will work but we will try it out.

Stupid question: your suggestion implies that both the head and foot needs to be visible to (tracked by) FAAST -- am I reading that correctly? We were assuming it didn't matter which points were visible to FAAST because the error was present whether or not the feet were being tracked. Also, if this is the way it works, would it help to set FAAST to track only the upper body?

[Jeff]

your suggestion implies that both the head and foot needs to be visible to (tracked by) FAAST -- am I reading that correctly?

I meant this for the initial calibration to calculate the user's height.

If you set FAAST to track just the upper body are you getting different readings for the head height?