 |
http://forums.thedarkmod.com/topic/10173-ai-reaction-time/page__view__findpost__p__200252 |
|
|
Changed the visibility polynomial value to match the wiki. An AI won't see you, even in full brightness, if the distance between you is > 40m (1,575 Doom units). At that distance, you can see that someone is there, but it's difficult to tell exactly who it is. I.e. a Priest has a lot of red and a Revenant has a lot of red. So we turn the table and assume that an AI can tell you're there, but he can't see enough detail to know you're an enemy. If an AI starts to search because he might have seen you, he no longer runs if the search point is far away. He will run toward you if he enters Combat mode and stays there. He won't enter Combat mode if farther than 20m (787 Doom units). 20m is set with a new cvar. The AI barks something from "snd_alert1s" when starting the Combat pause. These barks are of the "huh?" variety. Pause before fully entering Combat. Check for visibility of player after pause is finished. This gives the player a short time to duck back out of sight. The pause varies from 0.1s to 2s, depending on distance. 2s is the value used at 20m. These are hard-coded. If the AI quits Combat because he can no longer see the player after the pause, he drops back into Agitated Searching. So he will continue to walk toward where he thought he saw you. Delayed a "player sighting" (for mission stats) until after the Combat pause is over and the AI can still see the player. Allowed an AI to spot the player regardless of where the AI was in his hiding spot effort. If he had ramped up to AgitatedSearching, he was less likely to spot the player than if he had been in Idle State under the same circumstances. rev. 5366: CombatState.cpp CombatState.h SearchingState.cpp AI.cpp AI.h SysCvar.cpp SysCvar.h MeleeWeapon.cpp |
- Anonymous
