I don’t know if this is the case in every kind of blueprint, but in a normal actor blueprint the GetLinearColorValue node is not accessible through the context sensitive menu. The node is working as expected, so i guess this is a UI-Bug and not an invalid use of the node.
Since you are using a custom variable, the context sensitivity might not always detect the correct context in which you are going to use the variable. The important thing is that it still functions within the scope of what you are attempting achieve when using the node.
Hi Andrew, thanks for the comment! Since the variable is of the type LinearColorCurve and the GetLinearColorValue works on these classes, i thought it should be an easy check for the “blueprint parser”. On the other hand i don’t know how blueprints are compiled, so i guess i’m wrong here From an interaction design standpoint these failing checks are a problem. Maybe you could give a hint to the user in case of a custom variable to look into the “not sensitive” results as well. Even more useful would be to always display “not sensitive” results, if the search couldn’t find anything in the “sensitive list”.