[Bug] Horizontal lines flicker and/or disappear with ESRI SceneView
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- computer-graphics, data-visualization, frontend
Research direction
Start with the linked CodePen and the DeckLayer/DeckRenderer for ArcGIS path, reproducing the flicker in Chrome with ESRI SceneView while zooming. Compare one-pixel lines with wider lines and confirm that horizontal lines remain visible and stable when the issue is fixed.
Written by the indexing model from the issue text.
Description
Description
Here is a quick code pen that displays four horizontal lines with ESRI SceneView and deck.gl. An example image of it working properly is below.
However, every so often on the zoom end a line will disappear like the image below (red line is now missing). Lines also flicker while zooming.
.
Flavors
- React
- Python/Jupyter notebook
- MapboxLayer
- GoogleMapsOverlay
- CartoLayer
- DeckLayer/DeckRenderer for ArcGIS
Expected Behavior
Lines not flickering or disappearing
Steps to Reproduce
Visit this code pen and zoom in/out. The horizontal lines will flicker. Every so often, when you stop on a certain zoom level, one or more lines will completely disappear.
This flickering can be mitigated with the pixel width greater than 1. The disappearing of horizontal lines can be completely eliminated when pixel width is greater than one. This problem does not exist when running deck.gl without a basemap.
Environment
- Framework version: 8.7.8
- Browser: Chrome 100.0
- OS: Red Hat 8.5 and Mac OS
Logs
No response
- Dominant language
- TypeScript
- Stars
- 14.6k
- Forks
- 2.3k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 42
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.
More from visgl/deck.gl
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·