xeru98

For riot. This bug is likely caused because you are using a UWidgetComponent which by default is hit testable. Just change the collision profile of the widget component to IgnoreAll

This bug was caused by a misconfigured collision setting in the parent component of the UI prompt. I've fixed it on our side.

xeru98

In this case the UWidget is most likely part of a UWidgetComponent which treats it’s UserWidgetObject as part of the collision on the component. I don’t know if the widget it’s self is hit testable. But the widget itself would intercept a line trace since it’s on a widget component.

You are right though.... hit testable is specifically taking about widgets. I really meant to say the components collision profile

We're on the same page, and I simplified my response. :)