yep... my example in my post above was not intended to show real commands... just the concept of the 15 frames per second animation that you'd need to apply to routines to make them smooth.
I use the "t amount of time" parameter when it works... however, a significant number of commands don't seem to be affected by the "T" parameter.
I guess the bottom line to what I'm ranting about here is that, if you want to have your character do more movement, there are many built-in commands that execute a sequence of movements, such as "the finger", "shake boobs", "sexy walk", etc., But then you get what is available in that command, some have a little adjustment, some seem to be "as is". If you want the character to do specific things, at a specific rate, you have to do it line by line in an animated format, similar to a 15 frames per second thing.
But wait... there's more... add to all of that, that the interface seems to be less dependable the more you throw at it, so I've also found that I have better luck by keeping the routines small and for one purpose, then link the ones that I want in sequence. An example of this is the built in command "The Finger" does not work on some of the full body haptars I have, but someone built a NEW "The Finger" and did it line by line, move the arm, wrist fingers, etc., to get the motion, and it works on ALL my haptars with arms.
Actually... because the Haptek documentation seems to be such a closely guarded secret, like HAL, I'm considering just going another way.
