There is a bizarre issue with WebGPU lighting.

[jellychen]

Description

Sometimes we inherit from Three.js's light classes to create a subclass with additional custom functions. This works fine in WebGL, but causes issues in the WebGPU renderer.

WebGPU relies on the class's constructor to locate the lightNode, and when we create a new subclass via inheritance, this process breaks.

Is this considered a bug?

Reproduction steps

empty

Code

empty

Live example

empty

Screenshots

No response

Version

175

Device

No response

Browser

No response

OS

No response

[Mugen87]

Do you mind sharing a small code example that demonstrates the issue? I'm afraid I don't understand the problem yet.

[jellychen]

Do you mind sharing a small code example that demonstrates the issue? I'm afraid I don't understand the problem yet.

class MyLight extends Three.DirectionalLight {
...
};
const l = new MyLight();
scene.add(l);

Works in the WebGL renderer but not in the WebGPU renderer.

Maybe Cause of MyLight.constructor donot match any lightNode

[Mugen87]

In WebGPURenderer, lights are implement based on nodes. If you define a custom type, you must tell the renderer what node class should represent it.

renderer.library.addLight( THREE.DirectionalLightNode, MyLight );

Live example: https://jsfiddle.net/d60893mf/1/

[jellychen]

https://jsfiddle.net/d60893mf/1/

ok thanks