WebGPURenderer: Introduce TiledLighting

[sunag]

Description

The main idea of ​​having a lighting system is to open up the possibility for contributors to add their own lighting system like clustered lighting, which is why I added TiledLighting in addons.

About TiledLighting, there are still improvements to be made, such as sorting the lights according to the proximity of the camera to obtain better indexes, adding disposes, math optimizations and mainly added WebGLBackend support.

API

The user does not need to manipulate anything special, such as shaders or uniforms, just define the class for light system.

const lighting = new TiledLighting(); // ( maxLights = 1024, tileSize = 32 )

renderer = new THREE.WebGPURenderer();
renderer.lighting = lighting; // set lighting system

Or define per material.

import { tiledLights } from 'three/addons/tsl/lighting/TiledLightsNode.js';

const lightsNode = tiledLights();
lightsNode.setLights( [ ...pointLights ] );

const materialA = new THREE.NodeMaterial();
materialA.lightsNode = lightsNode; 

const materialB = new THREE.NodeMaterial();
materialB.lightsNode = lightsNode; 

Process summary

1. Store all the light data in a texture. It's position, color, distance...

2. Create a buffer that represents pieces of the image, the tiles. Each tile will have the indexes of the lights that are visible in that piece.

3. Instead of processing all the lights on the entire screen, we will only process the lights that are present in the indexes of each tile, I made each tile store 8 indexes. It is as if it had only 8 lights to calculate per pixel.

4. There is a pre-renderer stage where the compute-shader will project the position and radius of light to screen space where we can check for intersection with the tiles using AABB and thus bind the light, indexing it in the tile buffer.

As I limited it to 8 indexes per tile and we do not have a sort lights, the system may fail if too many lights are added close to each other.

three.js.webgpu.-.tiled.lighting.-.Google.Chrome.2024-10-13.07-36-53.mp4

Commits

• introduce lighting system
• introduce tiled lighting
• WGSLNodeBuilder: Remove incompatible types
• Renderer: move .nodes.library -> .library

[github-actions]

📦 Bundle size

Full ESM build, minified and gzipped.

	Before	After	Diff
WebGL	689.92 170.93	689.92 170.93	+0 B +0 B
WebGPU	814.81 219.39	815.27 219.76	+465 B +372 B
WebGPU Nodes	814.32 219.25	814.78 219.63	+465 B +373 B

🌳 Bundle size after tree-shaking

Minimal build including a renderer, camera, empty scene, and dependencies.

	Before	After	Diff
WebGL	462.94 111.81	462.94 111.81	+0 B +0 B
WebGPU	537.62 145.06	538.01 145.26	+392 B +198 B
WebGPU Nodes	493.74 134.79	494.13 135.13	+392 B +338 B

[RenaudRohlinger]

Am I the only one with 5fps on the webgpu_lights_tiled example when using 100 lights, and having both my Chrome and Chrome Canary completely crashing when using 1000?

Also the demo looks odd, maybe related to the recent changes on the transmission pass of the Renderer:

/cc @sunag

[Mugen87]

On dev I have a black screen and see the following warning in Chrome:

Error creating pipeline state Fragment function exceeds available stack space
at InitializeImpl (../../third_party/dawn/src/dawn/native/metal/RenderPipelineMTL.mm:449)

[mrdoob]

It hangs Chrome here (M1 Pro) and eventually I get this in the console:

[sunag]

I ended up turning it off after an unsuccessful cleanup, here it is again
#29722

[mrdoob]

This is how it looks like now on a Pixel 8:

https://raw.githack.com/mrdoob/three.js/dev/examples/index.html?q=tiled#webgpu_lights_tiled

[mrdoob]

Looks good on ChromeOS!

[sunag]

This is how it looks like now on a Pixel 8:

Could it be cache?

[mrdoob]

This is how it looks like now on a Pixel 8:

Could it be cache?

I think it was yeah.
Just tried again and it works properly 🎉