 |
The guard having the problem is Stevens. There's an elevator nearby. Maybe it's causing the problem. |
|
|
I saw this again while testing the picked pocket code. An elevator was present on the other side of an open door. After re-dmapping, the problem stopped. Might have something to do with a bad AAS outcome of a damp. Or it might have something to do with an elevator being somewhere on the path. Edit: Leaving the door between the AI and the elevator closed allowed the AI to path properly. Opening the door caused the AI to start circling. So opening the door exposes the AI to the elevator. Something's wrong with the goal that the pathing routine gives back to the AI under these conditions. |
 |
Don't know if this is actually relevant to this issue, but while testing my map I had a guard who was alerted by an alarm in the basement while he was on the main floor, and I found him running in circles in the room he started in. There were no elevators in the map, just stairs and two doors between him and the location of the alarm. If I see it again I'll save a copy of the map. |
|
|
Okay, thanks. I've only seen permanent circling these days in two maps: Home Again (until I changed the path corners so it stopped happening) and the pickpocket test map I'm working with atm. Both incidents happened near elevators. Closing in on the bug. Is there a path_corner for the circling guard somewhere directly above or below him? |
|
|
No. He was a sitting character who had an alert_only pathnode outside the building. But at the time of circling he was fully alert trying to respond to an alarm that had sounded in the basement. |
|
|
Perhaps he was just stuck in a tight area? |
|
|
Found the problem. Having both an elevator and an open door on a long path exposed a problem where the AI wasn't being given a goal near the door in order to go through it. He was continually being given the final goal, which messed up getting through the door. |
|
|
Aaaand found another problem. A small window between pushing a task and actually starting it allows other tasks to sneak in. This was disturbing the relationship between handling a door and handling an elevator. |
|
|
Two spots in the door handling task needed to give the AI somewhere to go. Needed better coordination between the door handling and elevator handling tasks. In the 4 frames between killing an elevator task and starting a door task, another elevator task was allowed onto the task queue. This extra task was causing problems when the door task finished. Added a PopMove() variant that doesn’t restore the popped move. This prevents unnecessary pathfinding. Fixed a problem that happens when you hit an AI on an elevator with a moveable. He reacts to the hit, flushes the elevator task, and has pathing problems when he goes back to pathing and he’s on the moving elevator between floors, where there are no AAS areas. Needed to add a pause to the pathing task in that situation, to give the elevator time to reach the next floor and get the AI back on an AAS area. Rev. 5945: State.cpp HandleDoorTask.cpp HandleElevatorTask.cpp PathCornerTask.cpp PathCornerTask.h ResolveMovementBlockTask.cpp AI.cpp AI.h MovementSubsystem.cpp MovementSubsystem.h |
- Anonymous
