WebGPURender with logarithmicDepthBuffer is not work!

[ChuckieLei]

I use WebGPURender with logarithmicDepthBuffer but not work.
I find the reason when i use custom material and set vertexNode=xxxxx, i will show this error.

Then, i use three-js examples, webgpu_lines_fat.html, only modify WebGPURender param, add logarithmicDepthBuffer:true. It show same error. I try use three-js-v165 and v-167, it all not work!

[manthrax]

WebGPU renderer is still pretty new. It’s very possible that some features like logdepthbuffer might not be implemented yet.
You could try searching the github issues.

[Attila_Schroeder]

The logarithmic depthbuffer in webgpu works very well. I use it. You have to use the depthNode in webgpu if you use the logarithmic depthbuffer with custom raw shaders.

A little advertising for the three.js node system and WebGPU

I only work with WebGPU and therefore with the three.js node system. In the meanwhile WebGPU is very well integrated in three.js. [mars1.PNG] [mars2.PNG] [mars3.PNG] These are screenshots of my WebGPU original sized planet generator. I am not ready yet. I now have to add rock and sand textures to the surface. I would ideally have over 200k of data for the elevation profile, but the best thing NASA has so far as a coherent map is the Mars MOLA map with 46k. With that my virtual texture sys…

My whole app works with the logarithic depthbuffer. Works great And my app is huge.
In webgl you operated the depth buffer from the fragment shader. In webgpu there is an extra node for the depth buffer because wgsl works a little differently.

Three.js even has an example with the logarithmic depthbuffer in webgpu

https://threejs.org/examples/?q=loga#webgpu_camera_logarithmicdepthbuffer

In the screenshot you can see the webgpuRenderer and that the logarithmic depth buffer is active. The example is up to date with r167. It uses three.webgpu.js instead of three.module.js but that all worked since at least r161with three.module.js. The logarithmic depth buffer is therefore fully integrated into the webgpuRenderer. However, if you want to avoid the node materials and use your own shaders like I do, then you will have to operate the depthNode yourself. If you ignore it you will get your error messages.

Regarding the general status of webgpu in three.js:
I’m working very intensively with webgpu. I only work with webgpu. Three.js has changed its architecture with r167. The node system is now in the src folder and no longer in examples/jsm/, which I personally think is very good. With three.webgpu.js, three.js is also completely set up for webgpu. I assume in order to be able to maintain webgpu completely independently of webgl in the future. The webgpu system already works very extensively. I don’t miss anything from webgl anymore because the webGPURenderer and the node system meanwhile offer everything I know from webgl.

[manthrax]

Ahh good to know! ty Attila

[ChuckieLei]

OK，i’ll try operate the depthNode, thanks so much for your detailed reply!!

[Attila_Schroeder]

Here is a short example how I do it with wgslFn