WebGPU: NodeMaterial updates

[sunag]

NodeMaterial

• new example webgpu_materials
• new nodes NormalNode, MathNode d95eb36 4c2ab57
• build node in custom shader stage eef49b1
• fixes nodes: VaryNode, PositionNode.LOCAL
• fix displace with normals example webgpu_sandbox 2337179

[sunag]

Some known reason to those extra lines?

[mrdoob]

That looks like my first programs in GWBasic! :')
Is it a WebGPU thing?

[sunag]

@mrdoob Yes! in WebGPU :)

[mrdoob]

@sunag I mean like an implementation thing... I guess we can't try on Firefox yet?

[sunag]

@sunag I mean like an implementation thing... I guess we can't try on Firefox yet?

Ah yeah, nice question... I try run in Firefox Nightly but not work the example.

[Mugen87]

Sidenote: You can enable WebGPU in Firefox Nightly by opening about:config and setting the flags dom.webgpu.enabled and gfx.webrender.all to true. However, the current implemented WebGPU API differs between Canary and Nightly quite noticeably. So none of the three.js examples work right now.

[Mugen87]

The CI fails because there is no screenshot for the new example webgpu_materials.

You can add one by doing this: npm run make-screenshot webgpu_materials

[mrdoob]

I'll merge and generate the screenshot on my end.

[mrdoob]

Thanks!

[Mugen87]

BTW: It's good that you have implement transparency settings like so 👍 . This should solve #18038 since the render list is now correct in the first frame.

Material.transparent needs to be set by the user, not by the material system.

[sunag]

This was not a hated feature in general, it facilitates in most cases ( #16996 (comment) ) . More few months we must abandon the old NodeMaterial system and adopt the new one that uses .transparent... Should we wait this change only for the new NodeMaterial system?

[Mugen87]

Replacing the old material system with the new one makes sense. But maybe it's better to invest a bit more time in developing the new one before doing this step.