[Philippe]

Hi.

We get some troubles using lookat. We originally thought that after calling lookat with some parameters, when calling to lookat with new parameters, the new position will be immediately updated.

But when we used a sequence of the type:

{method with lookat}
{method with walkTo}
{method with lookat}
{method with walkTo}
{method with lookat}
{method with walkTo}

we obtained some kind of strange behavior, where the direction of the head came later than the change in the walkTo, even though all the methods above were in one <vizact>.sequence. The head was totally distorted in a very strange manner, no matter how we chose the lookat x,y,z point. We finally succeeded to find a workaround by splitting one of the walkTo path in two, in order to have the Avatar smoothly moving its head (and not having it looking completely backwards as it happened). In other words, not the change of the lookat x,y,z made the change in the head movement, but splitting the walkTo in sub paths (it seems like the lookat was not immediately updated and was stuck in the previous x,y,z definition).
This leads me to another (more general) question: when a thread (like lookat or walkTo) is launched, is there a way to know whether it is still active and what is its status ?

Thanks.