With the old system, I could move a character towards the player like this:

What is the equivalent way of doing this with the new AI? Being able to control speed with the new fpe speed setting is pretty useful, as there was a pretty low limit with speed with the old system.
Also, does the MoveWithAnimation function do anything?

you have to think of the characters as having 2 "bodies" now, 1 is the visual body the player sees (this is controlled with MoveForward etc) and the other is the physical body that is moved in the background by the engine to determine pathing and collision (this is controlled with the AI commands).

so firstly you move the AI (same as before still works fine).
then you move the visual body with MoveForward() etc (the actual speed value you use is best as the variable that returns the 'speed' setting in the properties, you can find this is the AI scripts).
then finally there's a new command to sync the 2 together (i can't remember exactly but again you can find it at the bottom of the ai modules)
if you look at the last page in my thread i have a few new AI scripts that will demo it better

MoveWithAnimation does work apparently though i've not got any models that need it so i'm not speaking from experience - however to use it you need a model that actually moves forward while animating (i.e. the model actually moves away from it's origin point while animating without any other input from GG, thinking about it i believe you actually have some fish that do it?)
i believe you use it like
MoveWithAnimation(e,animation_number)

sorry it's a bit vague but i dont have GG here but i know you're quite capable so i hope it helps

OK, I misunderstood MoveWithAnimation, I thought it would be useful . I'll have a look at your thread.

So it seems to be working for me, using this code (if anyone's interested).


I'm still not convinced about the use for the MoveWIthAnimation command - to do what I did with the fish you just need to play the animation. To be able to move an entity while playing an animation using a single command would be much more useful.
Thanks for your help again, smallg.

the difference is that with the way Lee has it set up is that you could still avoid obstacles and such even with models that move during their animation whereas without it you will clip through obstacles and then port back to the "hidden" ai's position on looping the animation, so it is a nice feature if you have models that really must move with their animations.

you could always build the process in your script into 1 function/command and call it with the one line if you wanted anyway... something like this

MoveForwardWhileAnimating(e,g_PlayerPosX,g_PlayerPosZ,5) --call this line in your script (5 is the animation number to play)

then in the global have the function (or at the bottom -outside- of any scripts that need it)

untested but should work fine.

Yep, works fine. Another useful function, thanks.