Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

[Closed] AIPerception dominant sense has no impact

Hi @Mieszko,

Running epic/master and considering the following BP EventGraph on an AIController:

alt text

Two senses are configured: AI Hearing and AI Sight; order they are created in the AIComponent does not matter it seems as it has no impact. Dominant Sense is either not set; it's set to Hearing; or set to Sight.

In any of the Dominant Sense cases, when Actor Perception Blueprint Info is iterated over and sense class name printed for index 0, it always returns Sight, no matter what sense is really active/last stimulated.

I believe this to be a bug or unintended behaviour. The Last Sensed Stimuli array should return in index 0 the sense that was last stimulated, which is not the case, at least not with Blueprints.

Either the array is not ordered in correct age order (Last In First Out); or the Sight takes precedence over Hearing regardless of the Dominant Sense configuration; or Hearing lags behind Sight

Actually this last one (Hearing sense lagging behind) seems to be the case almost always, as it does not appear to be detected/triggered all the time for me.

EDIT: Forgot to mention, when I trigger Hearing from my character, the AI still detects Sights even though I am not in the line of sight or visible to the AI at all.


Product Version: Not Selected
aiperception.jpg (179.4 kB)
more ▼

asked May 19 '15 at 09:27 PM in Bug Reports

avatar image

1.1k 53 33 90

avatar image amigo May 21 '15 at 09:49 PM


Any comments or ideas about this?


(comments are locked)
10|2000 characters needed characters left
Viewable by all users

The question has been closed May 25 '15 at 01:24 PM by amigo for the following reason:

The question is answered, right answer was accepted

1 answer: sort voted first

It seems there's a bug in AIPerceptionComponent that results in information about dominant sense never getting processed and all derived data doesn't get set. I'll file this as a bug.

Last sensed stimuli has fixed indices so that, for example Sight is always index 0. I say "for example" because it's game-specific and depends on your setup. In general stimuli arrays are indexed with "Sense ID". These are not usable in BP yet.

Regarding hearing lagging behind: this can be a glitch related to "speed of sound" feature I have in hearing sense implementation. I'll have a look.

Thanks for taking your time to report this!



more ▼

answered May 25 '15 at 12:32 PM

avatar image

MieszkoZ STAFF
7.4k 225 57 415

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question