Volodymyr Agafonkin

> also the heatmap example under https://docs.mapbox.com/mapbox-gl-js/example/heatmap-layer/ seems to work on both devices even though the webgl1 extension "OES_texture_half_float" is not available. The heatmap layer falls back to RGB textures...

@marco333333 oh, you're right, overriding isn't easy because of the internal classes... I guess what we could do is to cut out these two lines into it's own method (e.g....

One more thing to note is that WebGL 2.0 has [Uniform Buffer Objects](https://webgl2fundamentals.org/webgl/lessons/webgl2-whats-new.html) feature that allows setting uniforms in a typed array and uploading it at once instead of doing...

@kresli just pass `useWebGL2: true` in `Map` options if you need GL JS to be powered by WebGL2. There is no performance difference, only compatibility considerations. GL JS intends to...

Interesting! Might be GPU-dependent? Here's how the example works for me on macOS:  Can you also try different browsers?

Hmm, I have no ideas why Windows wouldn't like the `NEAREST` mag filter. Perhaps you could poke around the code and see if there are any clues? https://github.com/mapbox/mapbox-gl-js/blob/master/src/render/draw_raster.js#L48

> if geojson-vt is causing segmentation issues and if the errors introduced by geojson-vt are predictable enough, could we not fix that issue at source in geojson-vt? They aren't predictable...

@anisart no, that looks like a different issue — might be a regression. Let me take a look.

@simonrp84 this is likely an unrelated issue. E.g. tiles without buffers.

@vomc no, this one looks more like low `maxzoom` of a GeoJSON source — set it to a higher value. Although I can't say for sure without a reproducible live...