Best way to deal with multi sphere trace line of sight?

[Krileon]

@pezzott1

Try a cone shape collision to get overlapping actors in angle in front of player rather than multi trace. Removes the need to tick if managed on begin/end overlaps.

I don’t need a cone trace, but a sphere trace with line of sight. If I needed a cone trace I’d still do a sphere trace and use vector math to filter out any hits that aren’t within my cone. I actually have a post about this below with the vector math provided.

How to check if sphere trace hit is within radius?

Below is the solution I came up with. Seams to work well. Reviewed the BehaviorTree ConeCheck source code and remade the check in BP. Trace [image] IsHintInCone [image] ConeTraceDebug [image] Basically just do a normal trace. Pass its hit along (IsValid check before passing if you want) and it’ll report true/false if is within your cone radius. It’ll use the trace start/end points to determine the cone size along with your radius. The cone is infinite so you need to be sure your actual…

I do not recommend trying to do custom traces by attaching collision shapes to actors. They’ve to update their transform along with the actor. That’d be a lot slower than doing a sphere trace. The sphere trace itself is incredibly fast. Even if it hits 1000 it’s fine. It’s just itinerating over that 1000 for example that could be slow, but that’s mostly a BP problem. CPP can deal with large loops fine.

@pezzott1

IMO might be better to just have 2 separate arrays over a map. Having 2 separate arrays allows to sort without duplicating. Then access closest from index 0->.

I don’t see why it’d matter to be honest. You still need to push the sorted results into an array to be returned.