11–20 of 95 posts
It's so frustrating that WebGPU support was released 1.5 years ago on Chrome, and yet is still unavailable on all other browsers. This is a real killer feature that will dramatically slow adoption of non-Chromium browsers, even with Google defanging ad blockers.
It's so frustrating that WebGPU support was released 1.5 years ago on Chrome, and yet is still unavailable on all other browsers. This is a real killer feature that will dramatically slow adoption of non-Chromium browsers, even with Google defanging ad blockers.
It's so frustrating that WebGPU support was released 1.5 years ago on Chrome, and yet is still unavailable on all other browsers. This is a real killer feature that will dramatically slow adoption of non-Chromium browsers, even with Google defanging ad blockers.
For Safari that's par for the course, but Firefox is in surprisingly far behind in terms of anything GPU related in the browser. I've recently been shocked trying out the WebGL aquarium demo [0] on Chrome and Firefox after running into some really odd performance issues on a project. You'd expect them to behave about the same with GPU acceleration, but FF barely gets half the framerate at the same load. Like, what?!…
But I still need to figure out what exactly this is.
While this has to be the most fun to watch demonstration I've seen, something like the free tier of Hamina will likely be many times more useful to those wanting to optimize home Wi-Fi layout https://www.hamina.com/planner. The downside being they force you to make an account whereas this one lets you use it locally with the power of your own browser. The upside being Hamina gives multiple distilled views of the simulation as focused on common Wi-Fi statistics + features and less focus on displaying the wave simulation itself.
It's so frustrating that WebGPU support was released 1.5 years ago on Chrome, and yet is still unavailable on all other browsers. This is a real killer feature that will dramatically slow adoption of non-Chromium browsers, even with Google defanging ad blockers.
Why do you need webgpu? It's unfortunate that people use technology that is "state-of-the-art techniques to run simulations at interactive speeds" without fully understanding what it's for. General compute on GPU is what webgpu is for.. To simulate basic waves like in this demo you absolutely do not need that, in fact it's an indication the author implemented the solution in a non-optimal way. WebGL is fully supporte…
You absolutely could do this using WebGL2 compute shaders too, but I thought it would be fun to try this newer API.
Earlier quoted context omitted.
Even Chrome only supports it officially on Windows, macOS and Android, no GNU/Linux (as stable). And when it becomes widespread, just like WebGL 2.0, it will be a decade behind of what native APIs are capable of. And in both cases, good luck debugging, other than replicating the content on native APIs, as means to use proper GPU debuggers, because even Chrome has yet to offer any developer tooling for GPU debugging.
Runs great on my ChromeBook.
It's so frustrating that WebGPU support was released 1.5 years ago on Chrome, and yet is still unavailable on all other browsers. This is a real killer feature that will dramatically slow adoption of non-Chromium browsers, even with Google defanging ad blockers.
Earlier quoted context omitted.
For Safari that's par for the course, but Firefox is in surprisingly far behind in terms of anything GPU related in the browser. I've recently been shocked trying out the WebGL aquarium demo [0] on Chrome and Firefox after running into some really odd performance issues on a project. You'd expect them to behave about the same with GPU acceleration, but FF barely gets half the framerate at the same load. Like, what?!…
I‘m not an expert but I think it works on IOS with Safari. You have to enable WebGPU in the extra flag category in the settings app. But I still need to figure out what exactly this is.
Earlier quoted context omitted.
Why do you need webgpu? It's unfortunate that people use technology that is "state-of-the-art techniques to run simulations at interactive speeds" without fully understanding what it's for. General compute on GPU is what webgpu is for.. To simulate basic waves like in this demo you absolutely do not need that, in fact it's an indication the author implemented the solution in a non-optimal way. WebGL is fully supporte…
Good question! This is actually a numerical solver for a few coupled partial differential equations - the method in this context (electromagnetism) is called FDTD. It's implemented as a WebGPU compute shader. You absolutely could do this using WebGL2 compute shaders too, but I thought it would be fun to try this newer API.