Volodymyr Agafonkin

Can you share a full example, e.g. on JSFiddle? This is likely caused by the `999` maxZoom — Supercluster isn't really designed to work with zooms over 32 (and even...

@luixo yes, I think we should cap internally.

Thanks for the report! It looks like the stuttering occurs when the browser compiles shaders — which looks as `useProgram` taking a lot of time if you run the performance...

@garydevenay can you compare the example on legacy styles with GL JS v2.15.0 vs v3.0.0-beta.4? Is the amount of stuttering the same, or noticeably worse in v3?

@webprofusion-chrisc thanks for the report! Just be clear, is the v3 performance is choppy for you on the same style as v2 (e.g. streets-v12), not the newer Mapbox Standard?

@webprofusion-chrisc when you don't set `style` explicitly in GL JS v3, it uses Mapbox Standard by default, which is a more demanding style, so it's expected for it to possibly...

@garydevenay looking at the JSFiddle examples, it looks like you are comparing the Streets v12 style with the new, much heavier Mapbox Standard (which has 3D landmarks, trees, advanced lighting,...

`-sort-key` properties only reorder features within a layer — they are not designed to control rendering order across layers. We might need to clarify this in the docs, but that's...

@idanlo when adding a layer with [`map.addLayer`, there's a `beforeId` parameter](https://docs.mapbox.com/mapbox-gl-js/api/map/#map#addlayer) you can use to specify where to place that layer in relation to other layers.

Hmm, yeah, weird — I can confirm that popup is lagging compared to marker, even though internally their position is updated with the same mechanism. Will investigate.