Stacks! Low stacks, high stacks, lots of stacks! Cloth, ropes, bridges, springs! 50,000 block destruction in realtime! The #WebGPU physics engine, based on last year's SIGGRAPH "Real-Time Live!" winner AVBD, is almost here. Follow for updates!

Transformers.js v4 Ships WebGPU Runtime for Browser ML HuggingFace's Transformers.js v4 rewrites its WebGPU runtime in C++, supports 200+ architectures, and delivers up to 4x faster inference in browsers and server-side JS runtimes.

Transformers.js v4 Ships WebGPU Runtime for Browser ML

awesomeagents.ai/news/transformers-js-v4-...

#Huggingface #TransformersJs #Webgpu

Transformers.js v4 Ships WebGPU Runtime for Browser ML HuggingFace's Transformers.js v4 rewrites its WebGPU runtime in C++, supports 200+ architectures, and delivers up to 4x faster inference in browsers and server-side JS runtimes.

Transformers.js v4 Ships WebGPU Runtime for Browser ML

awesomeagents.ai/news/transformers-js-v4-...

#Huggingface #TransformersJs #Webgpu

Other #Firefox and Linux users, does #WebGPU apps work ? Doesn't for me...

Kiln also has experimental OME-Zarr support. This is the Beechnut — a 3 GB micro-CT scan streamed directly from a public OME-Zarr store into the browser. No preprocessing, no conversion. github.com/MPanknin/kil...

#WebGPU #OMEZarr #VolumeRendering

A TypeScript-powered 3D architectural editor with React Three Fiber + WebGPU that lets you design buildings in the browser with proper spatial relationships and state persistence.

https://github.com/pascalorg/editor

#TypeScript #WebGPU #Architecture

either #WebGPU doesn't work on firefox or my gpu is outdated.

The Lab On WebGPU compute shaders, the joy of building things that move, and the after-hours work that matters most.

We build WebGPU particle simulations after hours — 3M particles, strange attractors, slime mold networks, artificial evolution. All running on your GPU, zero dependencies. I've never seen any of them. Now they're live.

#WebGPU #creativecoding #AI #programming

We are going to be learning how to use #webgpu in #cpp to draw things to the screen www.youtube.com/watch?v=WFWd...

#WebGPU should be enabled by default in Firefox !

Unified Strata — WebGPU

#WebGPU tool, I am looking for a few testers.. Please if you do try it let me know if you have any questions, issues or suggestions.

lardratboy.github.io/nested/neste...

The best #Web3D I've seen in a LOOONG time.

So good. https://fractalworlds.io

#WebGPU #WebGL #WebXR

WebGPU + WASM is finally bringing 'pro' video editing to the browser. Forget heavy desktop installs; the goal is to be the 'Photopea of video.' But can a browser really handle 4K timelines without choking? The tech stack says yes, but the reality is more complex. 🎬 #webgpu 1/5

Professional video editing, right in your browser? WebGPU and WebAssembly are making it a reality, bringing desktop-class performance and GPU power to the web. See how!

thepixelspulse.com/posts/professional-video...

#webgpu #webassembly #wasm

Wonderland Engine Foundations course in Gamedev.js Jam 2026

Win THIRTY Wonderland Engine Foundations courses in #GamedevJS Jam 2026!

gamedevjs.com/jam/2026/#wo...

#gamedev #gamedevjs #Wonderland #WonderlandEngine #foundations #course #WebXR #WebGL #WebGPU #webgamedev

Bruno Simon Bruno Simon's creative portfolio

Stressing out, didn't realize #webgpu in Linux was all software rendered still. This is going to be like video encoding isn't it, going to be a half or full decade of everyone else having support but not us?

Trying to enjoy Bruno Simon's site:
bruno-simon.com

Some in-progress screens of the billboards in use:
#webgpu

Why Are We Still Doing GPU Work in JavaScript? (Live WebGPU Benchmark & Demo🚀) JavaScript has been the main language of the web for years. Its popularity probably surprised even...

Why Are We Still Doing GPU Work in JavaScript? (Live WebGPU Benchmark & Demo🚀) JavaScript has been the main language of the web for years. Its popularity probably surprised even its creator,...

#webdev #javascript #typescript #webgpu

Origin | Interest | Match

My hello-terrain library is finally getting picked up by game devs :)

hello-terrain.kenny.wtf

#threejs #webgpu #r3f

Got the path tracer running on mobile with 16-bit output using Kahan-summation & residuals packed into 8 bits. I'm a bit worried about precision loss so I'll probably replace this with something else. But it still looks quite good on these simple scenes! 🦀

#threejs #raytracing #webgpu #javascript

I built a procedural medieval island map generator using Wave Function Collapse on hex grids. 4,100 cells, 900 possible states per cell, 60fps on mobile. Wrote up the whole process with lessons learned. Links below 👇 #threejs #webgpu

Android's Advanced Protection Mode may soon start disabling WebGPU in chrome to protect against security threats

✅ Details & screenshot - www.androidauthority.com/android-adva...

#Android #Google #WebGPU

Table showing the tree-shaken bundle sizes for spark.js with WebGPU and/or WebGL.

I fixed the shader imports to work with static analysis, so you can estimate bundle sizes for WebGL and WebGPU.

In practice, though, shaders are imported dynamically. You only pay for what you use, so the overall size is tiny.

#webgl #webgpu #sparkjs

Calling all programmers!

Khronos Group is hosting "3D on the Web" -- an evening of talks, demos & networking around #WebGL #WebGPU, #glTF & #Gaussian splats.

March 11 · 5:30-9:30 PM PDT
Easy 12 minute walk from GDC in
San Francisco

Learn more and register: khr.io/1ng
#WebDev #3D #GDC2026

Join us for 3D on the Web on March 11 in San Francisco

Calling all programmers!

Khronos Group is hosting "3D on the Web" -- an evening of talks, demos & networking around #WebGL #WebGPU, #glTF & #Gaussian splats.

March 11 · 5:30-9:30 PM PDT
Easy 12 minute walk from GDC in
San Francisco

Learn more and register […]

[Original post on fosstodon.org]

Announcing spark.js 0.1 I'm excited to announce spark.js 0.1, now with WebGL support!

I'm excited to announce the release of spark.js 0.1 now with support for WebGL!

www.ludicon.com/castano/blog...

#webgl #webgpu #sparkjs

Announcing spark.js 0.1 I’m excited to announce spark.js 0.1, now with WebGL support! spark.js has been evolving since I released it last summer. Since then, the WebGPU ecosystem has matured considerably. WebGPU is now more stable and widely supported across browsers and platforms. However, users kept telling me the same thing: even though targeting WebGPU is practical today, most teams have codebases that still rely on WebGL, and that made adoption difficult. For that reason I committed to adding WebGL support. This felt like the right moment to bump the version number to 0.1 and signal that spark.js is production ready, not just experimental. That said, I expect the API to continue evolving based on the features developers need and the friction points they encounter. ## WebGL Support Support for WebGL is the main feature of this update. For a long time I believed WebGL could not update the contents of a block compressed texture from the GPU. I thought it lacked support for Pixel Buffer Objects and didn’t support `EXT_copy_image` either, making it impossible to implement Spark without a CPU read-back. Turns out I was wrong, PBO support is there! I’m not entirely sure where that misconception came from. I was possibly confused because PBO support in WebGL is somewhat limited compared to OpenGL. That may have been reinforced by Unity’s documentation, which reports that WebGL does not have texture copy support, making me think that these limitations imposed a more severe constraint. However, in practice, WebGL provides everything needed to implement copies from UINT textures to block-compressed textures. That said, these copies are more expensive compared to WebGPU and native APIs like Vulkan and D3D12. In WebGPU the shader can output to a buffer and then copy its contents to the compressed texture, and in some native APIs the shader can write to the compressed texture directly. The process in WebGL is far more convoluted. Compute shaders with buffer stores and raw image copies aren’t supported, so the codec has to run as a fragment program and output compressed blocks to a render target, then copy the render target to a pixel buffer object, and the PBO to the final compressed texture. Even with this overhead, real-time compression remains practical and fast enough for most applications. ## Cached Temporary Resources Another issue I wanted to address is the driver overhead when compressing many textures. In my initial implementation I created temporary resources for each texture and destroyed them afterward. To reduce this overhead I added support for caching of the temporary resources. This is particularly critical in WebGL where you need to have both, temporary buffers and render targets. In order to use the feature you have to opt-in when creating the spark object, and you can free the resources explicitly when done: // Create spark object with temp resource caching enabled. const spark = await Spark.create(device, { cacheTempResources: true }) // Load and transcode a bunch of textures at once. const textures = await Promise.all( imageUrls.map(url => spark.encodeTexture(url)) ) // Free cached resources. spark.freeTempResources() ## Other Features Another way to reduce overhead is to allocate the output texture once and reuse it across updates. This is useful for textures whose contents change frequently, and can be achieved by passing the output texture as an option: persistentTexture = spark.encodeTexture(renderTarget, { outputTexture: persistentTexture } ) In the future I’d like to extend this option to support other use cases, for example, encoding regions of a larger texture, which would be helping to support virtual texturing applications. The mipmapping improvements I discussed in my previous post have now been merged. One unexpected issue I encountered is that alpha-weighting and the magic kernel did not play well together. The negative lobes of the kernel would sometimes produce zero or near zero alpha values. These would then cause fireflies when un-pre-multiplying. For now I’m using the alpha-weighted box kernel for textures with alpha. In the future, the right solution is probably to apply the sharpening filter after undoing the alpha pre-multiplication. If you’ve tackled this problem before, I’d love to hear how you approached it. Finally, I’ve also started publishing the examples automatically with a github workflow, so you can explore them without having to checkout the repository or install the required development tools: https://ludicon.github.io/spark.js ## WebGL Demo With WebGL support in place, I’ve updated the gltf-demo to support it. WebGL is used automatically when WebGPU is not supported, but you can also choose it explicitly using the `?renderer=webgl` URL argument: https://ludicon.com/sparkjs/gltf-demo/?renderer=webgl ## Integration with 3D Tiles Renderer To really showcase this release, I wanted to take an existing WebGL application and add real-time texture compression, and I thought there was no better stress test than the 3D Tiles Renderer. Integrating spark.js turned out to be extremely straightforward. The `TilesRenderer` uses three.js’s `GLTFLoader`, and spark already provides a plugin that handles image transcoding automatically, so the initial integration required just a couple of lines of code. There was one gotcha: `TilesRenderer` tracks memory used by loaded tiles to decide when to stream in new tiles or unload existing ones, and it does this by assuming textures have an associated image bitmap. That assumption breaks when transcoding textures with Spark, since the resulting textures are `ExternalTexture` objects. To handle this, the Spark GLTF Plugin now stores the byte length in the texture’s `userData` field: const texture = new THREE.ExternalTexture(textureObject.texture) texture.format = textureObject.format texture.userData.byteLength = textureObject.byteLength And the memory footprint calculation handles this special case: if ( tex instanceof ExternalTexture && tex.userData?.byteLength ) { return tex.userData.byteLength; } The results speak for themselves. Texture compression doesn’t just reduce bandwidth and power consumption, it frees up memory for higher-resolution textures with mipmaps (improving aliasing) and increased geometric detail. As they say, a picture is worth a thousand words: Spark OFF Spark ON Spark OFF Spark OFF Spark ON Spark OFF You can check out the full code changes in our fork of the 3DTilesRendererJS repository: https://github.com/NASA-AMMOS/3DTilesRendererJS/pull/1497 ## See You at GDC Finally, if you would like to see spark.js in person or chat about texture compression, I’ll be at GDC next week and I will be presenting at the 3D on the Web Khronos event: https://www.khronos.org/events/3d-on-the-web-2026 Hope to see you there!

I'm excited to announce the release of spark.js 0.1 now with support for WebGL!

www.ludicon.com/castano/blog/2026/03/ann...

Going to GDC next week? If so, join us at 3D on the Web in San Francisco on March 11th! 3D on the Web showcases the latest in WebGL, WebGPU, glTF and 3D Web Graphics. See the agenda and register: www.khronos.org/events/3d-on...
#glTF #3D #graphics #programming #WebGPU #WebGL #glTF

Join us at 3D on the Web on March 11 in San Francisco

Next week, 3D on the Web is back!

Join industry leaders, developers, and creators on March 11, 2026 in San Francisco for a showcase of the latest in WebGL, WebGPU, glTF, and 3D web graphics. Whether you’re building immersive apps, innovative tools, or next-gen […]

[Original post on fosstodon.org]

Happy to report that Lego LDraw models are working

#threejs #raytracing #webgpu #lego