Function Executes Even When It's Not Supposed To?

Community Community & Industry Discussion
,
1

Hey community :slight_smile:

So I have this trace function for my character for interaction and the function runs even when the trace is false even though it’s not supposed to. Outside the function it only goes straight to an interface message to the “trace hit actor” and I don’t save the hit actor anywhere. Here is the function:

Trace Function Issue
Trace Function Issue1677×471 167 KB

Here is an example of the situation. In the first picture the trace actually hits the door and interacts like its supposed to. In the second picture I am away from the door and the trace hit is false, but it still interacts with the door. Here are the pictures:

Trace_Function_Issue_1
Trace_Function_Issue_11075×595 33.3 KB

Trace_Function_Issue_2
Trace_Function_Issue_21073×593 28.6 KB

I have checked the hitboxes of the door and the length of the trace, it’s not one of those. Also the trace works as it’s supposed to otherwise.

Thanks :slight_smile:

2

Understand that the exec pin outside the function always fires, even if you don’t have logic going to a return node. Outside the function, either (a) return a bool of if there was a hit, or (b) check if the hit actor & component are valid.

1 Like
3

Oh really? Hmm, okay :thinking: Is that a thing that happens exclusively with functions and not with macros or other such things? I didn’t realize that before

4

Yeah, functions always fire the exec pin so it can run the next node after it; macros don’t. Also, functions can only have one exec pin, whereas macros can have multiple.

1 Like
5

Yeah I kinda knew the other differences between macros and functions but not the continuous exec on functions. Thanks for enlightening me :slight_smile:

1 Like