Hitbox (box collision component) performance

[PazDim]

Hi. I have a performance problem with hitbox implementation.
In my FPS project I have 100 NPC. Shooting is implemented via hitscan traces. I use my custom hitbox for hit detection. It is just UBoxComponent, I create several hitboxes for each NPC and attach them to sekeletal mesh bones (two for leg, two for arm, for body, for head…).
Hitbox collision profile configured for QueryOnly and ignore all but Hitscan channel.
What I see:

1. In current implementation game has 50-60 fps (too low), without any hitscan traces;
2. If I fully disable hitbox collision (configure profile for No collision) - I get 120 fps;
3. Next test - enable QueryOnly, but set all channels ignored - again 50-60 fps.

What am I doing wrong? I found another approach - using Physical asset. But it requires higher performance (capsules vs boxes), doesn’t it? I tried to replace hitboxes by PA and got the same 50-60 fps.
Why do hitboxes consume performance even with all channels ignored? What is the right way to implement hitboxes?

[PazDim]

I set SetGenerateOverlapEvents to false and FPS was increased to 70+.

[Auran131 (Auran13)]

im no expert on performance but to offer an alternative you can use HitBone from trace results instead of box collision

otherwise just make sure yout hitboxes only collide with your projectile (not visibility etc)

[PazDim]

I tried to disable all channels, but hitboxes still affect performance.

[PazDim]

Found temporary workaround - attached all hitboxes to root component (capsule). Yes, they are not moving, but animations are simple static locations don’t metter. In static mode hitboxes don’t consume performance (I don’t know why).

[KaidoomDev]

Why not turn off collision for all your boxes and use one big hitbox or the character capsule itself, and once you get hit by a trace, turn on collision for all those boxes and do the trace again see which box is hit and then turn them back off.