Make available for Capture Attribute node laziness evaluation #102511

New Issue

Iliya Katushenock · 2022-11-14T23:41:56+01:00

Iliya Katushenock commented

2022-11-14 23:41:56 +01:00

Nodes whose result may not be required should not cause inputs to be evaluated. The Capture Node already has compute disabled if it is not connected. But this is not enough. The node should support laziness and only call compute inputs when needed.

Nodes whose result may not be required should not cause inputs to be evaluated. The Capture Node already has compute disabled if it is not connected. But this is not enough. The node should support laziness and only call compute inputs when needed. ![image.png](https://archive.blender.org/developer/F13914609/image.png)

Iliya Katushenock commented

2022-11-14 23:41:56 +01:00

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

Iliya Katushenock commented

2022-11-14 23:41:56 +01:00

Added subscriber: @mod_moder

Hans Goudey commented

2022-11-15 00:05:16 +01:00

Added subscriber: @HooglyBoogly

Hans Goudey commented

2022-11-15 00:05:16 +01:00

If everything else is set up properly, this is probably pretty simple as params.set_input_unused(..).

It's a bit annoying to call it for every single input socket though-- all the different types. So maybe it would be easier to wait for dynamic socket types.
If someone did it earlier though, that would be fine too, it's a nice improvement.

If everything else is set up properly, this is probably pretty simple as `params.set_input_unused(..)`. It's a bit annoying to call it for every single input socket though-- all the different types. So maybe it would be easier to wait for dynamic socket types. If someone did it earlier though, that would be fine too, it's a nice improvement.

Iliya Katushenock commented

2022-11-22 18:07:27 +01:00

As it turned out, both #99563 (Store Named Attribute requires evaluation even if it does not used) have a hidden complexity. Now laziness for nodes connected by more than one link works a little differently than intended in these tasks. Because of this, these tasks will require deeper changes.

Gerstmann Bradley commented

2022-12-21 20:50:54 +01:00

Added subscriber: @Bradley_G

Gerstmann Bradley commented

2022-12-21 20:50:54 +01:00

Not sure if it's relevant to this post.
I want to add that if you output a capture attribute in a group node at the time when making an asset, this capture attribute will be computed even if that linkage is not used outside the node group. In such a case, Transfer attribute seems kind of better option for making a group node, as it won't be computed when its linkage is not being used regardless. However, when it's used, it also seems to be slower than capture attribute.

Not sure if it's relevant to this post. I want to add that if you output a capture attribute in a group node at the time when making an asset, this capture attribute will be computed even if that linkage is not used outside the node group. In such a case, Transfer attribute seems kind of better option for making a group node, as it won't be computed when its linkage is not being used regardless. However, when it's used, it also seems to be slower than capture attribute.

Iliya Katushenock self-assigned this 2023-01-28 20:21:21 +01:00

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Make available for Capture Attribute node laziness evaluation #102511