 |
getTurnRate() exists so perhaps this is mostly implemented. As of 2.03 is has been reported that "anim_rate_x" args aren't functioning as expected. |
|
|
Probably AI.h: ID_INLINE float GetAnimRate() { return m_animRates; } ID_INLINE void SetAnimRate(float newAnimRate) { m_animRates = newAnimRate; } |
|
|
and AI_events.cpp const idEventDef AI_SetAnimRate( "setAnimRate", EventArgs(), 'f', "Gets the animation rate of the AI."); const idEventDef AI_SetAnimRate( "setAnimRate", EventArgs('f', "rate", ""), EV_RETURNS_VOID, "Set the animation rate of the AI"); |
|
|
Yep, m_animRates is an Entity property in Entity.h should work as expected. |
|
|
Hmm... Seems to be a bit bigger task than just copying GetTurnRate. Probably need to add an animRate property to AI. |
 |
got it to work basically need to make a few adjustments |
|
|
Three script functions were added to idActor with rev. 9968: float getAnimRate(int channel, string animName) get the speed for the animation called animName for the respective channel, returns -1 if none-existent float setAnimRate(int channel, string animName, float rate) sets the speed for the animation on the channel to rate. Returns 1 if successful, otherwise -1. Negative rates are not allowed, but they can be 0. string getAnimList(int channel) lists all animation names for the respective channel, useful to get the names needed for the above two functions. channel is usually one of the following - ANIMCHANNEL_LEGS - ANIMCHANNEL_TORSO - ANIMCHANNEL_HEAD |
 |
1) Why does setAnimRate returns 1 or -1? Isn't usually bool value 1 for true and 0 for false? The same holds for scripts. 2) How can getAnimList be useful? It returns a single string, how can script do anything with it? Are there some parsing functions for scripting language? 3) How is "animator" different from "GetAnimatorForChannel(channel)" ? You use both interchangeably... |
|
|
1.) I wanted it to be consistent with getAnimRate, which can return zero (anim on hold). As it is explicitely stated in the description and the return value will most probably not be needed anyways I don't see an issue here, even if it is non-standard. 2.) I added that for getting the necessary information that I needed to work on this issue. I thought it might be useful for mappers, too. It is not intented to be used on the fly but to receive the informations needed for the mapper to do the manipulations he wants to make. So it should be used during the creation of a FM, not in the released version. 3.) The GetAnim functions in getAnimRate and setAnimRate perform null-pointer checks. In getAnimList I needed to add it myself, hence the reference. The different channels can have different amounts of animations. I don't know whether it is really necessary, but it doesn't hurt. |
- Anonymous
