It would make blueprints WAY more clear if one could just use simple getter nodes for accessing input parameters than crossing the whole graph with several wires to the input node of the function.
Currently, I assign all input parameters to local variables with the same name each time manually to clean up my graph. That shouldn’t be necessary and ist just confusing:
For me it makes more sense that input parameters are shown exactly as what they are and where they come from. If you are crossing your graph too much, maybe you should clear it by grouping things and abstracting away to functions/macros.
Sorry, but a paramater value just is a local variable, so it should just be exposed as such, too. That’s also the reason why you can’t simply create a local variable with the same name.
It’s been more than a year with no reaction at all. Why is it so difficult to list the (already defined) local variables from the parameter list? Why are they still hidden?
Yes, this should definitely be a thing, since the variables are already hidden in the background anyway. Exposing these variables by default would save a ton of time.
Thanks for the feedback. As is mentioned in the linked forum post, we have a ticket for this request, UE-6936. It is currently backlogged, but we hope to tackle it eventually.
New: Function inputs are now exposed as variable “Get” nodes via the right-click context menu in a Blueprint function graph context.
To use: In a Blueprint Function graph, right-click to access the context menu. Any input parameters will be listed as additional “Get” actions. In this way, input parameters can be accessed like local variables from anywhere in the function graph; in other words, it’s no longer necessary to drag wires all the way back to the Function Entry node in order to access these values.
