Add an "Exists" boolean to the named attribute input node #100004

New Issue

Hans Goudey · 2022-07-26T18:21:48+02:00

Hans Goudey commented

2022-07-26 18:21:48 +02:00

It could be helpful to tell if an attribute exists when building node groups, to choose between different behaviors or to give more helpful errors.

For the purpose of the attribute usage/dependency info shown in node overlays and the modifier, this should count as "read".

It could be helpful to tell if an attribute exists when building node groups, to choose between different behaviors or to give more helpful errors. For the purpose of the attribute usage/dependency info shown in node overlays and the modifier, this should count as "read".

Hans Goudey commented

2022-07-26 18:21:48 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Hans Goudey commented

2022-07-26 18:21:48 +02:00

Added subscriber: @HooglyBoogly

Erindale commented

2022-07-27 14:05:51 +02:00

Added subscriber: @Erindale

Erindale commented

2022-07-27 14:05:51 +02:00

Would this allow for example to check if a node group socket is occupied and if not then to, eg, use Position? Similar to how the texture nodes had a default state that can be overridden by plugging into the vector socket.

Irakli Kupunia commented

2022-07-28 02:06:16 +02:00

Added subscriber: @ikakupa

Paul Larson commented

2022-08-01 21:46:44 +02:00

Added subscriber: @GeorgiaPacific

Shan Huang commented

2022-09-26 04:32:53 +02:00

Added subscriber: @Shan-Huang

Shan Huang commented

2022-09-26 04:32:53 +02:00

Hmm noob question: where should the boolean be stored? Should it be stored in the GeoNodeExecParams object passed to the node exec function, as a used_name_attribute?

Hmm noob question: where should the boolean be stored? Should it be stored in the `GeoNodeExecParams` object passed to the node exec function, as a `used_name_attribute`?

Iliya Katushenock commented

2022-09-26 08:15:35 +02:00

Added subscriber: @mod_moder

Iliya Katushenock commented

2022-09-26 08:15:35 +02:00

This is the provider's attribute response to a request by name, I think.

Edward commented

2022-10-21 02:29:22 +02:00

Added subscriber: @edward88

Edward commented

2022-10-21 02:29:22 +02:00

@HooglyBoogly I believe the only way to get the geometry component that has the attribute in question is during the evaluation of the node's attribute field, and i can't figure out how. Doesn't this feature belong to a data flow node?

Hans Goudey commented

2022-10-21 04:06:26 +02:00

The new output should be a field input (GeometryFieldInput) internally, it can be single value though, with VArray<bool>::ForSingle

The new output should be a field input (`GeometryFieldInput`) internally, it can be single value though, with `VArray<bool>::ForSingle`

Edward commented

2022-10-21 11:00:07 +02:00

This comment was removed by @edward88

*This comment was removed by @edward88*

blender-admin commented

2022-11-17 00:27:28 +01:00

This issue was referenced by 0d3a33e45e

This issue was referenced by 0d3a33e45eb3a69b665429cd24694d2d2ca0cbd4

Edward was assigned by Iliya Katushenock

2023-01-18 22:21:39 +01:00

Hans Goudey commented

2023-01-18 22:22:54 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Hans Goudey closed this issue

2023-01-18 22:22:54 +01:00

Serge Lyatin commented

2023-05-26 17:26:42 +02:00

I have a question about feature's design.
Let's take vertex weight for example: Exists shows True for all geometry no matter how many vertices have really assigned weight, but at the same time it can't be plugged to Switch Geometry as it represents a field type data.
What's the point of working it that way, maybe a single value boolean output would have more meaning?

I have a question about feature's design. Let's take vertex weight for example: _Exists_ shows `True` for all geometry no matter how many vertices have really assigned weight, but at the same time it can't be plugged to _Switch Geometry_ as it represents a field type data. What's the point of working it that way, maybe a single value boolean output would have more meaning?

attribute_exists.blend

118 KiB

Iliya Katushenock commented

2023-05-26 18:04:58 +02:00

@SergeL

Vertex weight isn't attribute.
Exists outputs is a field. Due to this it take geometry from context. This can not be used fot single-value input socket.
Exists return true if this name is contains in data layers. This not check is this vertex is was be in the mask for saveing named attribute / vertex weight is setted.

@SergeL 1. Vertex weight isn't attribute. 2. `Exists` outputs is a field. Due to this it take geometry from context. This can not be used fot single-value input socket. 3. `Exists` return true if this name is contains in _data layers_. This not check is this vertex is was be in the mask for saveing named attribute / vertex weight is setted.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Add an "Exists" boolean to the named attribute input node #100004