Store named attribute always creates an attribute despite it's selection #110157

New Issue

Shmuel Israel · 2023-07-16T03:53:25+02:00

Shmuel Israel commented

2023-07-16 03:53:25 +02:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98

Blender Version
Broken: version: 4.0.0 Alpha, branch: main, commit date: 2023-07-02 22:31, hash: 7be0d1481c67
Worked: (newest version of Blender that worked as expected)

Short description of error
when you use the selection on the store named attribute node the attribute is still created; all it does is set the attribute to 0.
The behavior expected is that no attribute would be created on unselected geometry.

Exact steps for others to reproduce the error

store a named attribute (with store named attribute)
set the selection to False (with a boolean node)
check in the spreadsheet for the attribute. this might not be a good enough proof (if you have some items with a true selection) , there for
use a viewer node to view the exists selection from a named attribute node with the attribute name, and see (in the spreadsheet) that is does exist, when it shouldn't.

Rant
I'm not sure if this is a bug or the way it is intended it work, but either way I don't think it's the appropriate behavior.
Basically, when you use the selection on the store named attribute node the attribute is still created; all it does is set the attribute to 0. I'm not sure purpose of the selection in this case; it's really not that useful with this behavior (I believe). It would be really useful to use this with the exists selection from the named attribute node. It's surprising to me that is doesn't work this way, that's why I'm reporting this as a bug (I believe this is a bug and not a design). Right now to do what I want, I would have to either use two separate geometry nodes for every store named attribute, or a second store named attribute to let me know if it's assigned; either way not that good. aswell, it would be a good idea to add a selection to the remove named attribute node.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2070 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98 **Blender Version** Broken: version: 4.0.0 Alpha, branch: main, commit date: 2023-07-02 22:31, hash: `7be0d1481c67` Worked: (newest version of Blender that worked as expected) **Short description of error** when you use the selection on the *store named attribute* node the attribute is still created; all it does is set the attribute to 0. The behavior expected is that no attribute would be created on unselected geometry. **Exact steps for others to reproduce the error** - store a *named attribute* (with *store named attribute*) - set the selection to False (with a *boolean* node) - check in the spreadsheet for the attribute. this might not be a good enough proof (if you have some items with a true selection) , there for - use a viewer node to view the *exists* selection from a *named attribute* node with the attribute name, and see (in the spreadsheet) that is does exist, when it shouldn't. <video src="https://projects.blender.org/attachments/f7295ed2-d59c-45fa-bb44-756ff5df7f30" title="2023-07-08 22-47-22.mp4" controls></video> **Rant** I'm not sure if this is a bug or the way it is intended it work, but either way I don't think it's the appropriate behavior. Basically, when you use the selection on the *store named attribute* node the attribute is still created; all it does is set the attribute to 0. I'm not sure purpose of the selection in this case; it's really not that useful with this behavior (I believe). It would be really useful to use this with the *exists* selection from the *named attribute* node. It's surprising to me that is doesn't work this way, that's why I'm reporting this as a bug (I believe this is a bug and not a design). Right now to do what I want, I would have to either use two *separate geometry* nodes for every *store named attribute*, or a second *store named attribute* to let me know if it's assigned; either way not that good. aswell, it would be a good idea to add a selection to the *remove named attribute node*.

2023-07-15 22-22-14.mp4

701 KiB

Shmuel Israel added the

labels 2023-07-16 03:53:25 +02:00

YimingWu commented

2023-07-16 10:07:44 +02:00

This is probably not expected behaviour from the implied logic of "selection" here, just like you can have vertex to have weight in some groups but not the other.

Will poke developers about this.

This is probably not expected behaviour from the implied logic of "selection" here, just like you can have vertex to have weight in some groups but not the other. Will poke developers about this.

YimingWu added

Module

Nodes & Physics

Status

Needs Info from Developers

and removed

Status

Needs Triage

labels 2023-07-16 10:08:00 +02:00

Iliya Katushenock referenced this issue

2023-07-16 10:14:35 +02:00

Store named attribute selection always sets an attribute #110118

Iliya Katushenock commented

2023-07-16 10:16:18 +02:00

As you can see, there is a similar behavior for zero size domains. This is so by design, the attribute should always be created if possible.

Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

As you can see, there is a similar behavior for zero size domains. This is so by design, the attribute should always be created if possible. ![image](/attachments/52a63338-265d-4bd0-a614-e177caae3e65) Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors. For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

image.png

248 KiB

Iliya Katushenock closed this issue

2023-07-16 10:16:20 +02:00

Blender Bot added

Status

Archived

and removed

Status

Needs Info from Developers

labels 2023-07-16 10:16:22 +02:00

Shmuel Israel commented

2023-07-16 19:47:16 +02:00

As you can see, there is a similar behavior for zero size domains. This is so by design, the attribute should always be created if possible.

Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Okay if that is by design. I wasn't sure if this was intentional. I'll have try something else or use double attributes. Thanks.

> As you can see, there is a similar behavior for zero size domains. This is so by design, the attribute should always be created if possible. > ![image](/attachments/52a63338-265d-4bd0-a614-e177caae3e65) > > Thanks for the report, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors. > > For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests > > For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug Okay if that is by design. I wasn't sure if this was intentional. I'll have try something else or use double attributes. Thanks.

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

Store named attribute always creates an attribute despite it's selection #110157