UX Feature Request: "In-line Property Reference"

When working with heavily parameterized graphs, something I feel would help a lot that perhaps may not rock the boat too much, would be the ability to direct properties and attributes in-slot, in addition to dragging wires around. Something like you see in many ‘scriptable object’ based architectures. Take the following example:

It’s a bit contrived, but demonstrates some of the issues I see in a lot of real-world graphs → crisscrossing wires, wires crossing nodes, wires crossing over large spaces (portals are coming soon though I think?), nodes that are near blocks converging and fighting for vertical space. Spaghetti. As blocks get added to the different contexts, you’ve really gotta work to keep things vertically organized. And as more complex behaviour is added it becomes both more difficult to look at and also wire things up.

What would be great would be, in addition to the existing wires and ports, a button or context menu next to the port to set them to properties or attributes directly, without running additional wires or anything. Not exactly like you see in “scriptable object architectures”, but something like:

I could mock up a more detailed example, but I think anybody reading this who’s familiar with the concept gets the basic idea. I started this post with just VFX graph in mind, though as everything seems to be moving towards a Graph Toolkit base, it would be nice to have this elsewhere too. Or maybe it can be done already in GTK? Thanks!

Thanks a lot for your feedback. We’ve been doing some mockup that is going in this direction.
The idea was to have some Button/Dropdown that would allow you to convert an input port to the most common usecase:
Constant / Random / Curve / Attribute and Property binding.

This would save a lot of space, should be more discoverable and make some simple block obsoletes.
Right now, we don’t have any ETA on this as for now it still in the concept stage.

Again, thank for your inputs, and don’t hesitate to share your views and ideas. Can I asssure you that we’re reading all of them :slight_smile:

Have a lovely day.

Great to hear, and appreciate the reply.

One small thing just while I’m still thinking about this, would be including activation ports (or maybe you are already :slight_smile: ). I don’t love branching, but especially when prototyping an idea or where they make sense would be nice.

Anyway, thanks again for the reply, keep up the great work!

Btw of small QOL graph improvements can Shader Graphs open with minimal working set up (_MainTex/_NormalMap/_MaskTex + samplers + connections, and grouped where applicable)? Also I like VFX graph picker more where there is additional pop up with descriptions for each template, and also option to pick from some ready samples. I think those would help me when I first started with shader graphs.