LarryG on 19/8/2017 at 20:13
I've been going crazy over this all morning. My AI patrols just fine to the TrolPausePt but does not pause.
Here are the setting on the AIWatchObj link from the AI to the TrolPausePt (click to enlarge). What have I forgotten is necessary? Why isn't this working?
[ATTACH=CONFIG]2379[/ATTACH]
LarryG on 21/8/2017 at 04:01
No takers? No one with any ideas why this TrolPausePt works as a TrolPt, but no pausing?
john9818a on 21/8/2017 at 05:42
I would use a TrolPt instead and use a AIWatchObj link from the AI to the TrolPt. Set the trigger height to 5 and make sure the TrolPt is placed about waist to chest high above the floor. Also make sure the AI can see the TrolPt with enough light on the TrolPt itself.
I honestly don't know how an AI would know to observe a TrolPausePt. Is there a script that grabs the Watch info and establishes the link?
Zontik on 21/8/2017 at 07:48
Try to check box "No test once triggered", I don't think you need it unchecked.
If doesn't help, then try to move the point a bit, maybe AI don't like where it is (because of pathfind database cells).
Then, radius 10 seems too big (just for my taste).
john9818a on 21/8/2017 at 07:58
Actually if the TrolPt was in a bad location where the AI couldn't pathfinding to it, the AI would stop at the previous TrolPt and remain there.
FireMage on 21/8/2017 at 10:32
Because there is no specific Line Requirement, light is not the problem.
I don't think that T2 manage automatic AIWatchObj.
Create the link yourself and make sure the source is the AI and the destination the TrolPoint.
Make sure the Point is enough high but not too much. It should be as high as the butt or torso of a random AI guard.
Make sure you placed your point in a place with a correct pathfinding.
Your settings also needs some improvements :
1) 8 radius and 8 height is enough.
2) Do not set to absolute but to High max. Or else the guard will never stop his pause when needed even if he is suppose to be dead or chase the player.
3) Do not tick No Test Once Triggered or else, it will happen exactely like an absolute priority.
4) Write "Stand 0" instead of "idlegesture 0". IdleGesture is an array of motions and some motions are longer than others and can add randomness to the game that could increase the difficulty to sneak correctly, breaking player's timing.
Just to make sure, set the same time defined for "reuse delay" for "reset delay".
That should do it.
If it still don't works, more details will be needed about your ais, your map and the environnement set for the patrol to see what's wrong.
Yandros on 21/8/2017 at 10:45
A TrolPausePt is just a TrolPt with the default AIWatchObj link settings property set on it, nothing special.
Larry, I assume the AI is reaching the point but just not executing the pseudoscript, and this isn't a path issue where he can't reach the TrolPt. If so, I would try what Zontik suggested above as I've seen that cause similar issues.
Zontik on 21/8/2017 at 12:33
Quote:
3) Do not tick No Test Once Triggered or else
Are you sure?
If it means exactly what is says, it should be ticked. Unfortunately I don't know what does it really mean.
Anyway, I have no problems with AIWatchObj since I've started to tick this checkbox every time I use the link.
"Very High" is also safe enough, but "Absolute" is dangerous, right (but can be used for testing purposes).
For the second thought, it can't be pathfinding issue. Radius 10 covers all possible problems.
LarryG on 21/8/2017 at 12:45
Quote Posted by Yandros
A TrolPausePt is just a TrolPt with the default AIWatchObj link settings property set on it, nothing special.
Larry, I assume the AI is reaching the point but just not executing the pseudoscript, and this isn't a path issue where he can't reach the TrolPt. If so, I would try what Zontik suggested above as I've seen that cause similar issues.
Exactly. That is what I was trying to describe. It patrols just fine, but the pseudoscript isn't executing. And it is not just one of these. I have 4 in the patrol path, none of which execute, but all of which get patrolled to. All of these have AIWatchObj links to them from the AI.
Edit: Ticking or unticking "No test once triggered" has no effect. Nor does changing the priority. Nor does adjusting the height parameter on the pseudoscript. The thing is I have a very similar setup on another AI in the mission which works just fine. But not this one.
Zontik on 21/8/2017 at 13:18
Maybe something special with this certain AI?
Or... a stupid thought: is the link attached in correct direction? Changing direction is easy now in New Dark and can be made by mistake.