AISense_Hearing / ReportNoiseEvent never triggers OnTargetPerceptionUpdated (UE 5.8)

Hi everyone,

I’m running into what looks like a reproducible bug with the AI Perception Hearing sense in UE 5.8. AISense_Sight works perfectly, but AISense_Hearing never fires OnTargetPerceptionUpdated, even in a minimal, freshly-created test project.

Steps to reproduce:

  1. New ThirdPerson template project (UE 5.8).
  2. Created a simple AIController Blueprint with an AIPerceptionComponent.
  3. Senses Config: added AISense_Hearing (Hearing Range 900, Detect Enemies + Detect Neutrals = true, Max Age 5.0, Starts Enabled = true, LoSHearingRange 0.0).
  4. Created a simple Character/cube Blueprint, set as this AIController’s pawn (Auto Possess AI = Placed in World or Spawned), placed it in the level.
  5. On the ThirdPerson player character, bound a raw Input Key (T) directly to AISense_Hearing::ReportNoiseEvent, with Instigator = Self, NoiseLocation = GetActorLocation, Loudness = 1.0, MaxRange = 0.0 (no limit), Tag = None.
  6. Bound OnTargetPerceptionUpdated on the AIController to a Print String.

Result: Pressing T next to the test pawn (confirmed via a Print String right before ReportNoiseEvent, so the call is definitely executing) never triggers OnTargetPerceptionUpdated / the Print String. No warnings or errors appear in the Output Log.

As a sanity check, I added AISense_Sight to the same AIPerceptionComponent (Sight Radius 1000, Detect Enemies + Detect Neutrals = true), and walking into the pawn’s view cone correctly fires OnTargetPerceptionUpdated immediately. So the perception binding, the controller, and the pawn possession are all confirmed working — only Hearing fails to ever produce a stimulus.

I also tried:

  • Adding an AIPerceptionStimuliSourceComponent on the player with Auto Register as Source enabled and Hearing registered in “Register as Source for Senses”.
  • Manually calling Register Perception Stimuli Source (Sense = AISense_Hearing, Target = Self) on BeginPlay, confirmed via Return Value that registration succeeds.
  • Removing and re-adding the Hearing entry in Senses Config, recompiling/resaving in between.
  • Testing from multiple call contexts (Enhanced Input, raw Input Key, Custom Event via Set Timer by Event) — all produce the same negative result.

None of these changed the outcome. Has anyone else seen Hearing fail like this in 5.8? Is this a known regression? Happy to upload a minimal repro project if useful.

Thanks!