Xiaoji Chen

This is likely connected to https://github.com/visgl/deck.gl/issues/6328 The issue is not specific to MVTLayer; any other layer seems to break the transition, but only if the other layer is rendered *before*...

@Oussema-Dallel This issue is a feature proposal. Please open your own issue or discussion thread if you need help with a current release.

I'm unable to reproduce this issue. It's understandable if React causes some performance overhead. It's also a known issue that the second monitor of Mac suffers from WebGL performance degradation....

I agree this is a reasonable expectation, though there are some complications if we decide to pursue this. A naïve implementation would be to block `attributeManager` from updating if `props.visible`...

@ibgreen The props diffing function aborts when the first change is detected and set the `propsChanged` flag, therefore we cannot rely on the flags to tell which props have changed....

A change like this will have a cascading effect on use cases such as tiling, multi-view, and transition. There is also the concern of holding on to outdated resources in...

Yes that is a known flaw of this example - if you have a path that is a closed loop (`positions[0]` is the same as `positions[positions.length - 1]`), the tesselator...

We have not checked in the new caniuse version because it somehow changes the render test results -_o_- But I guess it's ok to update them in a dedicated PR....

This looks like an issue fixed by https://github.com/visgl/deck.gl/pull/5727 in 8.5.0. Which flavor are you using, is it React + managed view state?

Here is a minimal example of managed view state: https://codesandbox.io/s/deck-gl-managed-view-state-yfh9p?file=/src/App.js If you comment out the line `setViewState(e.viewState);` you can see that the maps become misaligned. Mapbox normalizes the viewport to...