Component Overlap hit position always returns 0,0,0

3 years later to the date and I just ran into this same issue and 100% agree. If this isn’t intended to be supported then it shouldn’t be exposed. It looks like only “Hit Actor” and “Hit Component” are populated - though it seems to always be the actor and component that are sending the event which are already available via explicit outputs from the delegate. Which is to say - HitResult contains no novel information at all… it is effectively just the ctor default values.

Misleading at best and never useful. Remove it or (better yet) make it work!

2 Likes