 |
It should be random each time the character starts the walk animation, not just once on map start. |
 |
Where does TDM decide which anim to play? Other than in the *.def files, I can find no reference to "walkN" anywhere in the TDM files, scripts, or the SDK. The scripts only set up the "walk" anim. I notice that some AI have "walk" and "walk1" defined. Others get "walk1" and "walk2", so I guess that gives them "walk, walk1, and walk2". But I can't figure out how TDM decides to randomly play one of the available walk anims. |
|
|
My understanding is that the number in an animation name is ignored by the code. A code reference to "walk" will accept "walk", "walk1", "walk03", etc. If there is more than one such animation, it will randomly pick from the list. My experiences have generally born this out. Where or how it decides which to pick I have no idea, but it should happen every time the animation is called. Which AI have "walk" rather than "walk1"? |
|
|
I just did a test in idle_animations where I substituted a clearly different walk animation for walk2 so it was clear which one they were using. I can't confirm the original issue. Everything worked as expected...AI randomly picked a different walk animation each time they reached the appropriate path_corner. |
|
|
For the normal 'walk' anims (not counting things like 'walk_blind', etc.) ... Rats - walk, walk2 Builder forger, Elite guard, Proguard, Beggar, Revenant - walk1, walk2 Everyone else - walk -------------- I found the randomization in the animation code. It looks for anim names ending in numbers to recognize there are multiple anims, so I'm wondering if the rat has a problem because it uses 'walk' and 'walk2' instead of 'walk1' and 'walk2'. Don't know w/o debugging. |
|
|
"Everyone else - walk" All humanoid characters with the new skeleton use walk1, walk2. "I'm wondering if the rat has a problem because it uses 'walk' and 'walk2' instead of 'walk1' and 'walk2'." No, there's no problem there. I recently tested play_lute_idle2 and play_lute_idle, and they get randomly selected properly. |
|
|
So can this issue be closed? |
|
|
I don't see why not. |
 |
The bug is not fixed. I uploaded test/walkcycle.map. All AIs play the same animation on startup, except priest. |
|
|
I switched anim walk1 to the blind walk animation so it was easier to see who was playing what. 1st run: 3 AI playing walk, rest playing walk1. 2nd run: All AI playing walk1 except for priest who plays walk 3rd run: All AI playing walk1 except for priest who plays walk 4th run: 3 AI playing walk1, rest playing walk |
|
|
Another round of testing: 1. all 'walk' but priest who uses walk1 2. same 3. elite, priest, inventor & archer use walk, rest use walk1 4. elite, priest, inventor & builder use walk, rest use walk1 5. ALL use walk 6. all 'walk' but priest who uses walk1 So the randomizing might not be perfect, but it is there. In the 10 tests, all AI played both walk animations at least once. Don't know why the priest seems to be the odd man out so often. |
|
|
After watching them for a while, I've also seen AI change their walk when they get to the end of their path and turn around. So the randomizing seems to be working there as well. Is there any reason to keep this open? |
|
|
Ok, I close it. |
- Anonymous
