WebGPURenderer: Move .init() to private and added .setAnimationLoop()

[sunag]

Description

This is one of the part to maintain backward compatibility between WebGLRenderer and WebGPURenderer.

After initializing the WebGPU Device it will call the setAnimationLoop() callback, but as there are legacy projects that don't use .setAnimationLoop(), the .render() and .compute() function makes a test to verify if the device is available.

const renderer = new WebGPURenderer();

// recommended approach
renderer.setAnimationLoop( animate );

// legacy approach
requestAnimationFrame( animate )

This contribution is funded by Google

[mrdoob]

Love this!

Would it be possible to initialise webgpu in renderer.render() instead?

That way if someone needed to make sure webgpu was initialised the could call await renderer.init() themselves, but renderer.render() would do it for them automatically.

🤔

[sunag]

Ways to initialize a WebGPU Device.

// 1. Adding an animation loop callback
renderer.setAnimationLoop( animate );

// 2. Async init
renderer.render( scene, camera );
// or
renderer.compute( computeNode );
// or
renderer.init();

// 3. Sync init
await renderer.render( scene, camera );
// or
await renderer.compute( computeNode );
// or
await renderer.init();