I will try to reproduce it to PG
1 Like
ok, I reproduced my local issue in the playground, which seems to be due to an initialization problem with WebGPUEngine. Please comment on the creatEngine function to see the correct effect.
edit: If the camera target is set to 0 points, the correct effect can still be seen without annotating the creatEngine function.
Thanks for the repro, you need “filterable float” in your pg which needs to be requested at engine creation time, this will also imply going past the default webgpu limits:
2 Likes
thank you
1 Like
why filterable float is not init webgpu engine default config
why my deepin os system maxColorAttachmentBytesPerSample only 32？But on Windows, it can reach up to 128, and the graphics cards of these two machines are constant. Chrome also has Vulkan enabled.
This is why we do not enable those by defaults cause some devices do not support it.
Why is it not supported is a question for the Chrome team so you could try the Chromium bug tracker maybe ?