TSL&NodeMaterial: Unexpected result with custom material.

[Jenychen1996]

Description

Extending from NodeMaterial, rewrite the ColorNode and PositionNode materials, and initialize multiple material objects in the same scene. Only the Node of the first one is not null, while the rest are null.

When I use a custom input parameter, such as speed, in a ColorNode or PositionNode, the last input speed data will be used globally.

I encountered this issue while using Line2NodeMaterial in webgpu_lines_fat_raycasting.html.

Reproduction steps

1. Extend from NodeMaterial to implement a custom Material, such as Line2NodeMaterial.
2. Modify ColorNode, PositionNode, etc.
3. In the same scene, initialize multiple custom Materials.
4. When executing the code in the console, you will find that it is null.

materials.forEach(material => {
    console.log(material.colorNode)
})

Code

like Line2NodeMaterial

Live example

NodeMaterial

Screenshots

No response

Version

r178

Device

No response

Browser

No response

OS

No response

[Mugen87]

I don't see in your fiddle where you add and modify a color node. The log looks as expected to me.

[Jenychen1996]

I don't see in your fiddle where you add and modify a color node. The log looks as expected to me.

update link: FlashingNodeMaterial

I have regenerated the example. Please take a look.

What I expected was to obtain different material objects based on the given speed values, presenting the corresponding flow effects. However, the current result is that the same flow effect is obtained regardless of the different speed values provided.

[Mugen87]

The material system computes the same cache key for both material instances. You must move the speed uniform node into public space, only then the node will be part of the cache key computation.

Updated live example: https://jsfiddle.net/v3fdxjrz/1/

[Jenychen1996]

The material system computes the same cache key for both material instances. You must move the speed uniform node into public space, only then the node will be part of the cache key computation.

Updated live example: https://jsfiddle.net/v3fdxjrz/1/

Thank you for your reply, which has resolved the issue I was currently facing.