visgl / visgl/deck.gl

[Bug] PathLayer is "fuzzier" after upgrading to deck.gl 9.2 when passing `useDevicePixels: true`

Open
#9,817 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
14.6k
Forks
2.3k
Avg merge
2d 9h
Merged PRs (30d)
42

Description

Description

Here's deck.gl 9.2:

https://github.com/user-attachments/assets/dc0098b0-30d8-46c3-a950-6816fe973223

Here's deck.gl 9.1:

https://github.com/user-attachments/assets/360032b2-6193-49fd-97dd-9b5efd6159bd

The only commit in between them is this Lonboard PR that upgrades to deck.gl 9.2.

Flavors
  • Script tag
  • React
  • Python/Jupyter notebook
  • MapboxOverlay
  • GoogleMapsOverlay
  • CARTO
  • ArcGIS
Expected Behavior

No response

Steps to Reproduce

The easiest way to reproduce what I'm seeing is through Lonboard. It's this Python notebook in the Lonboard docs

git clone https://github.com/developmentseed/lonboard
cd lonboard
uv install
npm install
npm run build:watch
ANYWIDGET_HMR=1 uv run --group watchfiles jupyter lab

And then go to the north-america-roads.ipynb example

I'm really slow at making codepens because I don't work in JS often, so hopefully it's easy to spot what's going on 😬. Otherwise I can make a codepen in a follow up

Environment
  • Framework version: 9.2.1
  • Browser: Chrome 141.0.7390.54
  • OS: macos 15.6.1
Logs

I get notes about This version of luma.gl has already been initialized, but I see those often and I don't think those are related.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Lonboard north-america-roads.ipynb example and reproduce the React rendering difference with useDevicePixels: true. Compare deck.gl 9.1 and 9.2.1 around the PathLayer behavior and confirm the result in the notebook; done means the layer has the expected sharpness after upgrading to 9.2.1.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
computer-graphics, data-visualization
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.