im using the first person thing and i cant get anything to work. please help, ive been at this for days. it sees me but just isnt updating to chase me

Add "AI Perception Stimuli Source" component to your FPS Character. Make sure you have "move to" set as TargetActor, which you have implemented in your AI Controller. @@kirill2525

@@kirill2525 You also need to change the type of the 'Get Sense Class for Stimulus' to the normal sight one, not the config one

Affirmative. Did like you told i.o. using Stimulus Receiver Location. Before that with what was on the tutorial, AI was immediately skipping the MoveToLastLocation task and gointo to the MoveToRandomLocation sequence.

It didn't work for me, and I used both "get player character" and "get player pawn". I'm fucked.

@@leonelsandoval987did you ever fix your problem? i can’t seem to find what my mistake was

​@@leonelsandoval987 this is a bit late of a response, but have you set the "detection by affiliation" to enemy neutral and friendly? Idk I missed to do that. I'm suing the two "Get player Character" blocks in the handle sight, but it wouldn't follow my character because I didn't set the detection be affiliation. Hope this helps.

Mines not showing either. I double checked that I typed it in the HandleSightSense, compiled and saved. It still won't show.

same, and when added in doesn't seem to connect to the literal name

At least in my experience pawn sensing doesn't have as much control and isn't as dynamic as this is but pawn sensing is easier to set up

Its working fine for me mate, make sure your chase sequence is properly setup, with the abort both and also TargetActor Is Set, and both Move To are pointing to the right locations, one to TargetActor and the other to LastKnownLocation.

did you get it working for you?

@@blindphoenix I did but my "friend" turned out not to be a good one. Unfortunately because of what he did to the project and the only version I still have the file doesn't open properly so I can't tell you how I fixed it. It was not the way the gentleman above stated for me though. I ended up redoing the entire system using enumeration.

This is because the perception event is checking agains the "get player character", for multiplayer you will want to check the class of the actor sensed. I will add an episode about this to the series.

If your player character derives from the character class you don't have to add this component. It is already an auto registered class.

@@RyanLaley I see I didn't know that but I guess it's good to have that bit of info for anyone who can run into this issue like me. Thanks for the tip and the videos.

@@lmbits1047 that info helped me too thanks

@@RyanLaley FYI: I tried following your tutorial with a top down template and the AI didn't see me until i add the AIPerceptionStimuliSource. In my case it worked even without adding any "Register Source for senses" or "auto register as source". Not quite sure how or why, but just adding the component seemed to be enough. ^^;;

And even weirder it continued to work afer being removed.. I dont get this engine XD (but i like it)

" ' " he says it at 14:29 i didnt notice till my like 4th time rewatching the part wondering the same thing

Update : I did nothing wrong except turn off debugging. I'm actually not sure how I did that but when I restarted the editor it turned it back on and I could see my actor being noticed.

Same Here bud. cant figure this out. went over the code and spellings

I think it has to do with the "Observer Abort: Both", maybe? I don't fully understand how it reaches the last known location movement. If you indicate that you abort the self "flow" and also the rest of low priority flows (like moving to last known location), it'd just go back to Roaming. Or maybe I'm understanding it wrongly.

I'm sure this is irrelevant and you've already solved the issue, but the fix is making sure the TargetActor make literal name is identical to the TargetActor in the blackboard. For me, the blackboard's had a space between target and actor, removing that fixed it!

@@textik5821 Have the same problem but can' find a way to fix it as well X(

Please help

Create a "New Key" in Black Board and select object, rename it target actor and on the right open the key type and base class set to actor

All right thanks I will try that

@@Zatellia Thank you so much! It worked!

@@Zatellia Hero

Did you ever figure this out?

I think if you increase the BP_NPC’s max walking speed during the chase then reduce it when they are in patrol it should work

@@brodiemorris2081 yes, exactly this. i made a "set run" and "set walk" function in my enemy blueprint. in my BT i call a task to either set run or walk on my enemy blueprint depending on whether a boolean is set. make it public and set it in your chase / roam sequence appropriately when calling the task.

well because the AI Sight Config just stores the index. Since index 0 has a name (AISense_Sight), the index 0 have different configurations for such things as sight radius etc. Since you can add more indexes with different sight senses, you cant add the AI Sight Config.

to anyone it may concern after days of trouble shooting the cause was my character's capsule component idk why this matters but if you ever scaled it up or down put all xyz scale values back to 1 and it will fix the issue

Key is '

I have the same issue. Every single time. No matter what BT or how its configured. For those who need a work around, at the moment what I do for "Move To" is create a Task (BTT) for each Move To event. My enemy AI moves to my character by having a sequence that only triggers if the enemy AI senses the player (with "Player" tag) and if it senses the player then it will cancel its roaming and call the task "Enemy AI Move To Player" that runs a simple "AI Move To" with the "Controlled Pawn" node from the event trigger connected to the "Pawn" node on the AI Move To, "Get Player Character" attached to "Target Actor" node, and I made the Acceptance Radius node an editable variable so I can set this on each BT it gets called to (for ranged vs melee attackers - it's a simple means that I'll replace later with a more complex means of AI positioning relative to its target). From the AI Move To I ran "Finish Execute" from the "On Success" and "On Fail" nodes with the "On Success" having its "Success" box checked and the "On Fail" having its "Success" box unchecked. I'm working with more complex move to concepts using the AI Controller (I use the AI Controller for targeting - the less you can do in the BT the less likely it is to break). There's some really cool position finding stuff out there! It's just... there are a LOT of bugs with UE's system where things that should work simply won't and without knowing C++ it's going to be a LONG work around. I do not know C++ hahaha

Check AIPerception - Senses Config - Sense - Detection by Affiliation. Try different values of the checkmarks. Detect Enemies doesn't work for me. I set Detect Neutrals to true to get On Target Perception Updated event to be called. Maybe there is a way to set who is the enemy and who is not? Let's watch the rest of the video...

@@javacpp2525 ​@javacpp2525 Yeap, I did the whole thing, still not call the HandleSightSense function, ……until I follow Gorka Games‘s tutorial, finally, the AI chase me!