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
HeatmapLayer/GPUAggregator: fix WebGL feature checking #3483
Conversation
if (!isWebGL2(gl)) { | ||
log.error(`HeatmapLayer ${this.id} is not supported on this browser, requires WebGL2`)(); | ||
if (!hasFeatures(gl, REQUIRED_FEATURES)) { | ||
const info = REQUIRED_FEATURES.reduce( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Call GPUAggregator.isSupported
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Though the checks are same, HeatmapLayer doesn't use GPUGridAggregator, in future it is possible these feature list will change.
if (!hasFeatures(gl, REQUIRED_FEATURES)) { | ||
const info = REQUIRED_FEATURES.reduce( | ||
(acc, feature) => | ||
`${acc} ${feature}: ${hasFeatures(gl, feature) ? 'SUPPORTED' : 'NOT SUPPORTED'} `, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- this is technically debug info. I suggest moving this into
hasFeature
and uselog.log(NON_ZERO_PRIORITY, ...)
map
and thenjoin
will be more readable.
31d7180
to
9f42694
Compare
luma.gl now logs, when feature is checked and not supported. Updated |
For #3480
Requires: visgl/luma.gl#1210
Background
Fix
feature
checking in Heatmap Layer and GPUGridAggregator.Change List