 |
Fixing this in 2.03 because it was exposed by the 2.03 fix to bug 0003882. |
|
|
The fix for bug 0003882 exposed this problem. When StopMove() runs, it resets the move accuracy to default. If AI are using a larger move accuracy than the default, this screws up checking whether the AI has arrived where he wants to go. This (so far) only affected door handling, where running AI are given a larger move accuracy so they can hit their mark. A running AI trying to get to the front opening position of a closed door can get caught in a loop, where he thinks he hasn’t arrived at the position, but he has. He keeps trying to move to the position again, but he’s already there. The root cause is MoveToPosition() using a ‘true’ return value when the AI has arrived or hasn’t, and the position is reachable. Don’t want to make any changes to MoveToPosition() at this point. Rev. 6451: AI.cpp AI.h HandleDoorTask.cpp |
- Anonymous
