Switch to WebGL 2.0 #15136
Switch to WebGL 2.0 #15136
Conversation
|
📦 Preview the website for this branch here: https://deploy-preview-15136--ol-site.netlify.app/. |
|
@mike-000 could you please indicate where you get that data from? https://caniuse.com/webgl2 shows all green for chrome and edge (albeit with a slightly lower compatibility of 93% instead of 95% for webgl1). Edit: looks like Three.js will be dropping webgl1 support soon. Maplibre has also moved to webgl2 but still includes a fallback to webgl1. This thread is interesting: maplibre/maplibre-gl-js#2653 |
|
@jahow As in #14366 (comment) it is not a problem of browser support, it is Chrome and Edge will not work with older hardware (even though Firefox will work with it) so support for a WebGL fallback would be needed until October 2025 (I presume all Windows 11 compatible systems will be OK). Both of my ex Windows 7 systems have the same issue, while an ex Windows 8 system has no problem.
|
|
When we want to move to WebGL 2, the Canvas renderer provides an alternative for people who want to support older hardware. |
|
There is no problem requiring WebGL2 for new functionality which is currently experimental. Supporting only WebGL2 will break existing API functionality such as WebGL tile and Heatmap on the default browsers of many Windows 10 systems which still have 2 years support. The only alternative to ensure compatibility will be to not upgrade to newer OpenLayers versions or switch to alternative platforms. |
|
Yes, when we decide to do this, it will be in a major version. |
gberaudo
force-pushed
the
move_to_webgl2
branch
from
e2b3236
to
841a631
Compare
As discussed during the OL code sprint in Munich, we would like to move our code base to WebGL2.
This will allow us to write cleaner and more performant code, thanks to the new rendering techniques introduced in this new version.
Closes: #14377
Closes: #14366
Closes: #13367