WebGLBackend

[sunag]

Related issue: #26079

Description

https://raw.githack.com/mrdoob/three.js/dev/examples/webgpu_lights_selective.html

A minimal version of WebGLBackend. WIP.

[mrdoob]

Amazing!

[sunag]

WIP

https://raw.githack.com/sunag/three.js/dev-backend-webgl/examples/webgpu_cubemap_adjustments.html

[github-advanced-security]

CodeQL found more than 10 potential problems in the proposed changes. Check the Files changed tab for more details.

[sunag]

Should we show this message to the fallback? For examples that are already working on both backend? @mrdoob @Mugen87

[Mugen87]

The project used this type of message to inform the user when WebGL/WebGL 2/WebGPU is not supported and thus the example does not work. But since the example does work (just with a different 3D API), I wonder if logging a info message to the browser console is already sufficient.

[sunag]

Now we have 3 pure output option in webgpu_tsl_editor:

WebGLBackend was based on WebGL2 - GLSL ES 3.0

[sunag]

The examples below are working on both backends:

• webgpu_cubemap_adjustment
• webgpu_cubemap_mix
• webgpu_equirectangular
• webgpu_instance_uniform
• webgpu_lights_custom
• webgpu_lights_phong
• webgpu_lights_selective

Example like webgpu_loader_gltf needs to be added RTT support in WebGLBackend.

There are two verifications if WebGPU or WebGL2 is available.

if ( WebGPU.isAvailable() === false && WebGL.isWebGL2Available() === false ) {

	document.body.appendChild( WebGPU.getErrorMessage() );

	throw new Error( 'No WebGPU or WebGL2 support' );

}

[jrjdavidson]

looks great and excited about these developments! I'm having trouble running the cubemap adjustments example , see screenshot:

[jrjdavidson]

looks like the error is with this variable 'extension'

[WestLangley]

webgpu_lights_selective.html should define an env map. MeshStandardMaterial requires it -- especially for metals.

Also, the same example fails under Firefox because navigator is not defined. I expected it to fall back to WebGL.

[sunag]

After this fix it's working on Firefox using WebGL2.

webgpu_lights_selective.html should define an env map. MeshStandardMaterial requires it -- especially for metals.

I think the idea of this example is just to show the Light API being used in analytical light, in this case selective lights.

[WestLangley]

I think the idea of this example is just to show the Light API being used in analytical light, in this case selective lights.

Users copy the examples. It is incorrect to use MeshStandardMaterial without an environment map to reflect.

If you refuse to add an envmap, then as a compromise, please hardwire metalness to zero in the example. Otherwise the rendering is completely wrong.

[sunag]

If so, are examples like webgl_lights_physical, webgl_clipping_stencil, webgl_loader_draco and others not valid because they don't have an env map?

As far as I know the webgl_lights_physical example was created to test the light result in analytical lights and not IBL.

[LeviPesin]

Do we need GLSL1NodeBuilder if we are already deprecating WebGL1?