 |
I can't reproduce this. I have myself at one end of a simple room with 64-wide monsterclip forming a corner in one of the room's corners behind me. At the other end of the room is a guard. He spots me and charges, pulling out his sword. If I step back against the wall behind me, into the monsterclip, the guard stops, sheathes his weapon, and starts throwing rocks. Step out, he comes for me again. Step back, he stops and starts throwing. Do you have a test map showing the problem? |
 |
It was occuring in my map during testing, but I fixed the monsterclip in the area. I'll see if I can get it to happen again. |
|
|
I haven't had it occur in a map yet, but I did notice it in a recent LP posted on Youtube. If you look at the following video and scroll to 14:23, you'll see that the alerted guard appears frozen, jittering one frame back and forth. The fact that he then attacks as soon as the player leans suggests to me that he's in the middle of switching to combat mode, but that the player's position is causing some kind of problem. The moment the player leans, the problem goes away and the AI attacks as normal. When I experienced it, the AI was already charging in combat mode, but the frozen posture and 'jittering' back and forth was the same as seen here. https://www.youtube.com/watch?v=89nOwhzjCxc&index=80&list=WL |
|
|
Though the video shows the jitter, there are no visual clues as to what's causing it. The monsterclip around the crate has the same dimensions as the crate, so it's unlikely the player is off the AAS grid. So it might not be the same problem. To solve this, I'm going to need a savegame showing the problem. There are too many factors involved. |
|
|
Ok, this happened while testing today. There are two AI right in front of me, both of them staring right at me and 'jittering' back and forth between frames of an animation. http://www.mindplaces.com/glitch.zip |
|
|
After updating to Obs' latest Sikkmod commit this morning, I've been unable to build anything I can debug with. As soon as we work through the issues and I can build again, I'll try to see what's going on here. |
|
|
The problem is that the AI ramps up to Combat, then there’s not enough light for him to see the player, so he drops back to AgitatedSearching, where he checks player visibility differently. Now he sees just enough of the player to push him back into Combat, where he loses sight of him again, and drops back to AgitatedSearching. This cycle is repeating about once per second, causing the observed twitching. Changed the player visibility check when in Combat so it more closely matches the visibility check done as the AI is ramping up to Combat. Now, when the AI enters Combat, he stays there unless the player’s visibility drops off to where the AI can’t see the player in any state. Rev. 6009: CombatState.cpp |
|
|
I think my original assumption that this was a "player's in monsterclip" problem was wrong. All my tests with moving in and out of monsterclip resulted in the AI doing the right thing: either coming after me or stopping to throw stones. The problem was that the player was visible enough for AgitatedSearching to see him, but not visible enough for Combat to hang onto him, so he quickly toggled back and forth between the two states, which caused the jitter. |
|
|
No sightings in the 2 months after the fix, so I'm resolving this one. |
- Anonymous
