Dynamic Batching using webGPU

[Attila_Schroeder]

I made the CodePen example for the three.js developers to show an error with DataTextures in connection with the positionNode. This is not due to the positionNode itself, but there is a float format incompatibility between the float type in DataTextures and wgsl, i.e. WebGPU. It will be fixed but probably not yet with r156.

What you’re doing sounds good. Doing the mesh creation in a compute shader would have the advantage that the DataTexture would become obsolete, because compute shaders can use the wgsl textureStore command to store textures directly.

This could possibly circumvent the current compatibility problem between wgsl and DataTextures.

However, I don’t yet know how to use the textureStore command in conjunction with the storage node. I asked the developers on github to create an example. It may be that this is not possible yet with r155, because I can’t find anything with workgroup_size in nodes.js in the three directory (three/examples/jsm/nodes/nodes.js). This is a compute shader specific command to set the number of gpu cores to use for the calculation.

How do I need to modify my wgsl compute shader to use it with the node system?

I want to create and save a texture with a compute shader. Then I want to load this texture into another shader. First i wrote a compute shader and fragment shader in wgsl code: //compute shader @group(0) @binding(0) var outputTexture: texture_storage_2d<rgba8unorm, write>; @compute @workgroup_size(8, 8, 1) fn computeTexture(@builtin(global_invocation_id) id: vec3<u32>) { var texelCoord: vec2<u32> = id.xy; var uv: vec2<f32> = vec2<f32>(f32(texelCoord.x) / 511.0, f32(texelCoord.y) …

Here is the url on the subject here in the forum. But since all this is still so new, nobody knows something about it. That’s why I suggested to the developers in github to create an example with the node system. The ability to store textures is one of the most valuable things compute shaders can do.