 |
When a movement task begins, the current destination is saved on a movement stack. When the task finishes, the saved destination is restored and the AI returns to what it was doing. However, movement tasks can interrupt each other, with an interrupted task terminating. Unfortunately, aborting a task before it’s finished doesn’t properly handle the save/restore of destinations, leading to growth in the movement stack. This fix corrects that problem by disallowing interruptions if a task is performing a key operation, and by properly handling the movement stack. Now there should be no more than one saved move on the stack at any given time. These changes should also be made to the Interaction Task and Elevator Task, since those both use the movement stack. But that’s for the future, since these are used less frequently. rev 4722: MovementSubsystem.cpp HandleDoorTask.cpp HandleDoorTask.h State.cpp ResolveMovementBlockTask.cpp Task.h UserManager.cpp UserManager.h ai.cpp ai.h ai_pathing.cpp |
|
|
I saw this was targeted for 1.06, but greebo included it in the latest 1.05 RC, so I switched the target rev back to 1.05. |
- Anonymous
