Skip to content

Commit 2872c73

Browse files
authored
Revise WebGPU support documentation - landing page (#1431)
Updated the WebGPU support documentation to reflect recent changes and improvements since the Babylon.js 5.0 release.
1 parent 01baad8 commit 2872c73

File tree

1 file changed

+8
-19
lines changed

1 file changed

+8
-19
lines changed

content/setup/support/webGPU.md

Lines changed: 8 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -9,12 +9,12 @@ video-content:
99
---
1010

1111
## Introduction
12-
Following the specification from the [GPU for the Web Working Group](https://github.com/gpuweb/gpuweb), we have begun the journey to support this new technology. Our plan is to deliver support with WebGPU and WebGL feature parity in Babylon 5.
12+
Since the Babylon.js 5.0 release in May 2022, WebGPU support is available and backward compatible with the WebGL implementation of the engine. It was a huge milestone after many iterations on the specification from the [GPU for the Web Working Group](https://github.com/gpuweb/gpuweb) and with a tight collaboration with the amazing teams implementing WebGPU into the browsers. In 2024, we also rewrote all core engine shaders in native WSGL, to avoid the use of TintWASM in full WGLS applications.
1313

1414
![Inspector](/img/extensions/WebGPU.png)
1515

1616
### Benefits of WebGPU
17-
The promise behind [WebGPU](https://developer.chrome.com/en/docs/web-platform/webgpu/#what) is an exceptionally faster API provided through lower level control to system graphics resources from JavaScript. We hope to bring these extra performance improvements to developers in order to create even higher quality 3D web games and experiences through a tool they are already familiar with: Babylon.js.
17+
The promise behind [WebGPU](https://developer.chrome.com/en/docs/web-platform/webgpu/#what) is a faster API provided through lower level control to system graphics resources from JavaScript and also new capabilities. We hope to bring these improvements to developers in order to create even higher quality 3D web games and experiences through a tool they are already familiar with: Babylon.js.
1818

1919
Some features WebGPU brings to the table are:
2020
* Compute shaders
@@ -26,29 +26,20 @@ Some features WebGPU brings to the table are:
2626

2727
See the [dedicated progress page](/setup/support/webGPU/webGPUStatus).
2828

29-
You can also follow our progress on out [GitHub dedicated issue](https://github.com/BabylonJS/Babylon.js/issues/6443).
29+
The current implementation of WebGPU is merged in the main branch of the Babylon.js [GitHub repository](https://github.com/BabylonJS/Babylon.js).
3030

31-
The current implementation of WebGPU is now merged in the main branch of the Babylon.js [GitHub repository](https://github.com/BabylonJS/Babylon.js).
32-
33-
WebGPU is now supported by [Node Material and can be defined in the editor](/features/featuresDeepDive/materials/node_material/nodeMaterial#using-node-material-with-webgl-and-webgpu).
34-
35-
We are putting in a big effort alongside our next release to implement full support. Every contribution is more than welcome, so feel free to create a PR if you are interested in contributing to the future of high performance game development on the web.
36-
37-
## Potential Issues
38-
Even if we are now far into the development process, we are still subject to potential changes as well as specification uncertainties. We will handle these changes one at a time but as a result we may have to adjust the release schedule accordingly.
39-
40-
We have the full support from the amazing teams implementing the WebGPU into the browsers, so we can work together as needed to make development smoother for all.
31+
WebGPU is also supported by [Node Material and can be defined in the editor](/features/featuresDeepDive/materials/node_material/nodeMaterial#using-node-material-with-webgl-and-webgpu).
4132

4233
## Migration of Existing Games and Apps
43-
As backwards compatibility is one of our pillars, the only difference we wish to have is with the engine initialization which needs to be asynchronous:
34+
As backwards compatibility is one of our pillars, the only difference we have is with the engine initialization which needs to be asynchronous:
4435

4536
```javascript
4637
const engine = new BABYLON.WebGPUEngine(canvas);
4738
await engine.initAsync();
4839
```
4940

50-
## Will WebGL still be supported?
51-
Yes! Support for WebGL and WebGPU will be maintained side by side for the foreseeable future.
41+
## Is WebGL still be supported?
42+
Yes! Support for WebGL and WebGPU is maintained side by side for the foreseeable future.
5243

5344
## Testing WebGPU
5445
You can refer to [this page](https://github.com/gpuweb/gpuweb/wiki/Implementation-Status) for detailed information on browser support.
@@ -57,6 +48,4 @@ Assuming you're using a browser that supports WebGPU, you can try it out yoursel
5748

5849
![WebGPU](/img/extensions/webGPUPlayground.jpg)
5950

60-
Follow the status from the dedicated [Chrome Status Platform Page](https://www.chromestatus.com/feature/6213121689518080).
61-
62-
All demo code is available on [Github](https://github.com/BabylonJS/Website/tree/master/build/Demos/WebGPU), so you can compare both the WebGL and WebGPU versions and take notice that there are currently no differences beside initialization. We will try to keep it this way. :-)
51+
All demo code is available on [Github](https://github.com/BabylonJS/Website/tree/master/build/Demos/WebGPU), so you can compare both the WebGL and WebGPU versions and take notice that there are currently no differences beside initialization. We will try to keep it this way. :-)

0 commit comments

Comments
 (0)