WIP: Geometry Nodes: new socket shape for unknown socket type category #113608

Jacques Lucke · 2023-10-12T15:45:45+02:00

Jacques Lucke commented

2023-10-12 15:45:45 +02:00

The goal here is to experiment with a different shape for sockets of which the type "category" is unknown. By category I mean whether it is a field or single value (and in the future maybe list, grid, image, ...). Many function nodes like math nodes can work on all these kinds of data, and ideally their socket shape indicates that.

Currently, we use a diamond with a dot for that purpose, but that doesn't scale so well, because it looks to similar to field sockets and hence potentially works less well if we have other socket shapes for other kinds of data.

We'll also eventually need a solution for unknown socket type (float, vector, etc.) that can be combined with any other socket type.

I choose an asterisk symbol here, because it's often used as "wildcard" that can be anything.

This might not completely replace the diamond-with-dot shape. For example, the new shape doesn't really make sense for the Set Position node.

The goal here is to experiment with a different shape for sockets of which the type "category" is unknown. By category I mean whether it is a field or single value (and in the future maybe list, grid, image, ...). Many function nodes like math nodes can work on all these kinds of data, and ideally their socket shape indicates that. Currently, we use a diamond with a dot for that purpose, but that doesn't scale so well, because it looks to similar to field sockets and hence potentially works less well if we have other socket shapes for other kinds of data. We'll also eventually need a solution for unknown socket type (float, vector, etc.) that can be combined with any other socket type. I choose an asterisk symbol here, because it's often used as "wildcard" that can be anything. ![image](/attachments/482cb286-1b90-41b8-b8d3-381bf653353e) This might not completely replace the diamond-with-dot shape. For example, the new shape doesn't really make sense for the Set Position node. ![image](/attachments/cb33d63b-5d38-4308-99a4-90fb139758bb)

image.png

27 KiB

image.png

38 KiB

image.png

34 KiB

image.png

87 KiB

Jacques Lucke added 1 commit 2023-10-12 15:45:58 +02:00

add asterisk socket shape 9bc65c2865

Dalai Felinto commented

2023-10-12 16:00:14 +02:00

Can you increase it so it matches the circle size?

Can you increase it so it matches the circle size? ![image](/attachments/24feecbe-38b8-45b5-9114-ac5587fcce8b)

image.png

5.7 KiB

Jacques Lucke added 1 commit 2023-10-12 16:11:05 +02:00

use size from circle socket ab42efa057

Jacques Lucke commented

2023-10-12 16:15:25 +02:00

I updated the size.

Dalai Felinto commented

2023-10-12 17:26:02 +02:00

Have you tried rotating so we have a vertical tick?

Not sure which one I prefer to be honest.

Have you tried rotating so we have a vertical tick? ![image](/attachments/a10e5f90-5df9-49b6-be2b-d5ec94df943b) Not sure which one I prefer to be honest.

image.png

35 KiB

This pull request has changes conflicting with the target branch.

source/blender/blenkernel/intern/node_tree_field_inferencing.cc
source/blender/gpu/GPU_shader_shared.h

View command line instructions.

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u asterisk-socket-shape:JacquesLucke-asterisk-socket-shape

git checkout JacquesLucke-asterisk-socket-shape

Sign in to join this conversation.

No reviewers

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

WIP: Geometry Nodes: new socket shape for unknown socket type category #113608

Checkout