[Bug]HexagonLayer issues warnings if colorRange has "too many" elements (starting with version 9.1.x)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 14.6k
- Forks
- 2.3k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 42
Description
Description
If I create a HexagonLayer with a large colorRange, the following warnings are issued:
- INVALID_VALUE: texSubImage2D: width or height out of range
- GL_INVALID_VALUE: Desired resource size is greater than max texture size.
In addition, all hexagons become black.
These warnings were not issued with deck.gl 9.0.x.
Expected Behavior
Same behavior as in deck.gl 9.0.x, or at least a warning in the documentation of colorRange about large color ranges (and what "large" means).
Steps to Reproduce
Add
colorRange: new Array(2 ** 14 + 1).fill([186, 74, 0, 128]),
to the HexagonLayer example in the documentation.
Environment
- Framework version: 9.1.4
- Browser: Opera, Edge, Firefox
- OS: Windows
Logs
- INVALID_VALUE: texSubImage2D: width or height out of range
- GL_INVALID_VALUE: Desired resource size is greater than max texture size.
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 HexagonLayer example in the documentation and reproduce the issue using the reported colorRange size in deck.gl 9.1.4, then compare it with 9.0.x. Trace how HexagonLayer handles colorRange and texture limits; the work is done when the warnings and black hexagons are resolved, or the documentation clearly states the supported limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- data-visualization
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100