 |
You said he spent a few seconds looking at you. I assume you mean he was looking in your direction, but couldn't see you. Did he stop seeing you because you put notarget on before he could complete the climb up into combat state? Or did you duck out of sight? Or were you in shadows the whole time and he heard you but didn't see you? |
 |
He stopped seeing me because I put notarget on. I guess that's not really a fair case, come to think of it, since notarget can do weird things. I'll have to see if I can recreate it under normal conditions. |
|
|
Yes, going to 'notarget' causes weirdness. If you can recreate it w/o using notarget, I'm about to check in some code changes that would help in debugging the problem. It'll be a bit more clear as to why he says what he says and why he goes into Alert Idle when he calms down. |
|
|
Code checked in and Windows DLL uploaded to SVN. You'll want to add these two lines to Darkmod.cfg: seta tdm_ai_debug_transition_barks "0" seta tdm_ai_debug_greetings "0" Set the first cvar to "1" to have debug statements printed to the console. These will show the events that cause an AI to have "seen evidence" and to shift from Idle to Alert Idle. It will also print the barks an AI makes when he transitions to a new alert index (state), so you can see the barks ramping up and down. This might be useful when reproducing the original problem. |
|
|
I think this is actually the same issue as this: 0003472 |
|
|
This should be fixed with all the recent changes. |
- Anonymous
