I’m trying to make an AI with an AIPerception Component and whenever I try’n make any changes to senses config, maybe like setting the dominant sense or so, the editor crashes. Is this a bug or am I doing something wrong.
I’ve attached the log file
Thank You.
[EDIT] Updated the log file. Please take a look.
It seems you’ve attached a wrong log file, it shows a regular run of a 4.7.4 version, from a week ago.
Sorry, I might have done that by mistake… Currently, I’m not with my workstation. So, i’ll upload the correct log file tomorrow. Sorry again for the wrong file.
@MieszkoZ I tried using the AIPerception Component again to produce the same result at home and yet again it crashed. I’ve attached the log file.
Log File
It’s launcher’s log again. Please navigate to your project’s folder and find relevant log in the Saved/Logs directory.
Now, I’ve attached the correct log files. But I don’t think this is an AI issue as the editor crashed again while editing a BSP brush.
You’re right, the crash in attached log is not AI related. But there is a perception system issue resulting in a crash if you have AI with different senses configured. This applies to hearing and sight - if you have one AI that uses sight for example, and another one that doesn’t the it will crash on game end or death of the one that doesn’t have sight.
A workaround would be to make sure all AI use same senses (just configure them differently). A proper fix will hit the master branch really soon (testing it now).
Cheers,
–mieszko
Thanks @MieszkoZ for this answer. But, the AIPerceptionUpdate only detects the class which is registered as source in Register Perception Stimuli Source Node.
I don’t know what to do to make it detect all the actors in its sight radius.
Sorry, but there isn’t any documentation on it. So, currently only experimenting with the stuff.
Your website shows the usage of PawnSensing Component. So, I’m using that for now.
All things that you want to be perceivable via the sight sense need to register with RegisterPerceptionStimuliSource. We don’t do “see all actors” kind of perception since that would be ridiculously expensive and redundant - you rarely care about that. Why not making a common parent class for all things you want to be perceivable? Or just add that call to all BPs you really want to “see”?
You really don’t want to see “all actors” - there’s really a lot of them.
Yeah! By all actors I meant character, should have been more precise. So, I’ve to add the base class,i.e, Character or do I have to register all the different characters separately?
You need to create a Blueprint (or C++) class deriving from Character, add Event Begin Play event and call RegisterPerceptionStimuliSource. And use this class for characters in your game.
Ya, Thanks I already did that using a loop on the character array derived form the Character class.