Starting with v3.0, Babylon.js supports rendering using WebGL1 and WebGL2 contexts. The support is transparent for developers. By default the engine tries to get a WebGL2 context. If none is available then a WebGL1 one is retrieved.
You can test which version of WebGL is enabled with:
When WebGL2 is enabled, the shaders are automatically converted to GLSL v3.0. Babylon.js will then automatically take advantage of extended instruction/uniform counts.
If you are using custom shaders, the best idea would be to provide GLSL v2.0 shaders. This way your code will work on both contexts. You can obviously provide only v3.0 shaders but in this case your code will only work when WebGL2 is enabled.
You can find here the list of supported features and the backward compatibility options (when available)
|Feature||Description||WebGL1 compatibility||Demo||More info|
|Depth Frag||Used to compute logarithmic depth buffer||Yes through an extension||PG -
|Multisample render targets||Rendertarget textures can be multisampled to get antialiasing effect||No. Has no effect on WebGL1 context||PG -
|Standard derivatives||Standard derivatites are used in Babylon.js to help compute realtime bump||Yes through an extension||Demo||Documentation|
|Texture LOD||Used by PRBMaterial to simulate microsurface||Yes through an extension||Demo||Documentation|
|Vertex array objects (VAO)||A Vertex Array Object (or VAO) is an object that describes how the vertex attributes are stored in a Vertex Buffer Object (or VBO)||Yes through an extension||N/A. Every rendering is done with VAO by default||See below|
By default render targets (like mirrors for instance) are created without support for multisampling. To turn it on, just define a value for
renderTarget.samples > 1.
On WebGL1 context, this will do nothing. On WebGL2 context, this will enable multisampling (more samples imply better antialiasing but a slower rendering).
Here is an example of a mirror (512x512) with and without multisampling:
|No MSAA (1 sample)||MSAA (8 samples)|
When possible (either on WebGL2 context or when extension is available on WebGL1 context), Babylon.js will use VAO to control rendering. VAO are a kind of geometry objects. Instead of sending all attributes and buffers used by a mesh (one for position, one for normal, one for indices, one for texture coordinates, etc..), you can build a VAO which will keep track of all attributes / buffers used.
At rendering time, you just have to define one VAO instead of multiple VBO (vertex buffer object).
You can find more details on Tojicode's blog.