Skip to content

Fix gl-js-team/issues/309 #11346

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 15, 2021
Merged

Fix gl-js-team/issues/309 #11346

merged 1 commit into from
Dec 15, 2021

Conversation

karimnaaji
Copy link
Contributor

@karimnaaji karimnaaji commented Dec 15, 2021

Since the stencil renderbuffer may be shared between different tiles we need to ensure that it is cleared when recycled. Otherwise stale data left in that buffer may interfere with the new tiles sharing that same buffer, resulting in flickering in complex source overlap situations. The flicker is very difficult to trigger in a render tests environment, as it require toggling terrain on and off and zooming fast in and out.

https://github.com/mapbox/gl-js-team/issues/309

<changelog>Fix a rare terrain flickering issue when using terrain with multiple vector data sources</changelog>

Since stencil may be shared between different tiles we need to now ensure it is cleared when recycled
@ryanhamley
Copy link
Contributor

I manually confirmed that this fixes the flickering issue. Nice work

@karimnaaji karimnaaji merged commit cc4db4e into main Dec 15, 2021
@karimnaaji karimnaaji deleted the karim/gl-js-team-issues-309 branch December 15, 2021 21:06
@Azusa89757
Copy link

When the data volume is more than one million, the vector layers will appear crazy flickering when they are stacked together. After testing, this problem will not occur before 2.6.1, but will occur after this version.

version: mapbox-gl@2.11.1

2.11.1.mp4

version: mapbox-gl@2.6.1

2.6.1.mp4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants