 |
For # 3, a running AI will not close a door behind him, even if he opened it. |
 |
Good to know. For 2.01, I think I'll just look at speeding up the generic door open animation a bit. |
|
|
I've added the following lines to humanoid_newskel.def. Will have to test how this looks and whether it creates any problems. "anim_rate_use_righthand" "1.5" // speed up door opening slightly "anim_rate_use_lefthand" "1.5" // speed up door opening slightly "anim_rate_sit_up" "1.3" |
|
|
There's a delay in the code to wait for the door to open. I'll have to make that match the new animation. The only condition is that he's running? |
|
|
Oh, didn't realize that. I was thinking this would be a quick way of trimming a second or two off the procedure, but if it requires an additional adjustment to the code, maybe we'd better wait and look at more robust solutions for 2.02. |
|
|
Actually, there are several things happening. 1 - animation 2 - wait for animation to reach point where hand is near door (estimated time is 1.1s) 3 - door opens at a certain rate 4 - AI moves through opening when he fits (though there might be more timing control than this going on) I agree that this should move to 2.02. It's going to need testing with different types of doors, too. |
|
|
I've included the higher anim rates for using the hand. I've adjusted the door-opening delays accordingly, and I like the higher rates better than the old rates. They're still not fast enough for quick door handling, so I'll have to look at ways to get running AI through a closed door faster. Since I use the electric relight anims for door controllers, I also sped them up 1.5, and will need to test those to make sure they still look okay. The anims notify the code when it's time to do the relight, so I don't need to adjust any timing in the relight code to compensate for the faster rates. I need to test weapon and torch carrying AI, to see if I need separate higher anim rate defs for those replacement anims, or whether the faster rate is inherited automatically. |
|
|
The fixes submitted for issue 0003755 fix these problems. |
- Anonymous
