Dragging from “Hit Result” of Blueprint nodes “Line Trace By …” does not show “Break Hit Result” if context sensitive is checked.
It is, however, available in the non context sensitive list.
This is a minor but annoying issue. Using 4.7.6 in a new project.
Had this error a few months ago, too. Don’t know how to resolve it.
But here’s a workaround. You can split the the result right on the node itself (right mouse button, ‘split struct pin’).
Ah, cool tip! Thanks!
Hi btengelh,
I attempted to reproduce your issue in a new blank 4.7.6 project but this is the results that I get:
Is there anything going into the ‘Line Trace by Channel’ node in your setup?
Ok now that’s funny… in my PlayerController Blueprint it doesn’t offer this… however, in a (new, empty) actor blueprint it is available?
Shouldn’t it always offer to break $whatever no matter in which kind of blueprint I am currently?
OK I understand what you are saying but shouldn’t context sensitivity apply to the node it is dragged from - because the context in my case is a Line Trace (and, in my eyes, not the type of blueprint) 
anyway, these are design decisions and it is good to know how things are supposed to work. Until now I thought the context is only in relation to the node something is dragged from. thanks for the explanation!
Okay, I didn’t realize you were in the Player Controller. Generally a line trace is not performed in the PC so it is not a Context Sensitive option by design. This doesn’t mean that you can’t do it, you just need to have Context Sensitive off to be able to see it (which you know). And in turn, anything directly related to tracing is also locked out of Context Sensitivity.
Cheers,
TJ
OK I understand what you are saying but shouldn’t context sensitivity apply to the node it is dragged from
That was also what I was thinking until now…?
It’s ok if you remove Line Trace functions from controller blueprints, but remove Break Hit Result? That makes no sense. After all, there’s the “Get hit result under cursor” node that returns a hit result. And you can’t break it without turning off context sensitive. Usability fail there.
