[Bug] Flickering on the new CollisionFilterExtension
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 14.6k
- Forks
- 2.3k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 42
Description
Description
While using the new CollisionFilterExtension, I'm experiencing flickering while moving the viewport, as well as layers that end up in inconsistent states after the viewport movement.
In the attached screen recording, there's a noticeable flickering effect, and the marker in the back sometimes keeps opacity 1 after the map movement.
Flavors
- Script tag
- React
- Python/Jupyter notebook
- MapboxOverlay
- GoogleMapsOverlay
- CartoLayer
- ArcGIS
Expected Behavior
No response
Steps to Reproduce
The described behaviour can be reproduced on this codepen
Environment
- Framework version: deck.gl@8.9.4
- Browser: Brave Version 1.49.128 Chromium: 111.0.5563.110 (Official Build) (arm64)
- OS: MacOS Ventura 13.1
Logs
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the React reproduction in src/Components/Map.js from the linked CodeSandbox and inspect how CollisionFilterExtension is used with MapboxOverlay. Reproduce viewport movement and compare the flickering and marker opacity states. Done means layers remain stable during and after movement, with no flickering or incorrect opacity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- data-visualization, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100