You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MapLibre GL Native is using the shaders from MapLibre GL JS before the TypeScript migration. I am worried about changing the shaders in GL JS if we cannot test the consequences in native.
@wipfli Yes we have copied them over and they are being refactored to take advantage of OpenGL ES 3.0.
I think WebGL 2 has some of the same functionality of OpenGL ES 3.0, but GL JS does not use WebGL 2 yet. In any case, keeping them in sync will need to happen manually going forward.
@louwers , GL JS could very soon allow for some webgl2 though, so I have a hope that we might be able to copy some of these great changes to the shaders back to GL JS when it's ready.
MapLibre GL Native is using the shaders from MapLibre GL JS before the TypeScript migration. I am worried about changing the shaders in GL JS if we cannot test the consequences in native.
@birkskyum created a branch to use the shaders after the TypeScript migration: https://github.com/maplibre/maplibre-gl-native/tree/generate-shaders-using-typescript
Since we forked GL JS, there have been only a hand full of updates to the shaders, see https://github.com/maplibre/maplibre-gl-js/commits/main/src/shaders for a complete list. Notable changes were:
The text was updated successfully, but these errors were encountered: