-
Notifications
You must be signed in to change notification settings - Fork 7
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
EXT_color_buffer_float not supported #9
Comments
This message indicates that the |
I've actually noticed this as well. It is working fine on Firefox for me, but crashes on Chrome. Chrome Version 127.0.6533.120. Love your heatmap layer by the way, way better than the built in features on mapbox. |
What OS are you using? I didn't manage to reproduce the issue |
I've tried on Windows 10 & 11, same behavior on both for me. Here's a deployed version I have up in case the stack trace in dev tools is helpful, the first heatmap layer generates when you hit the play button on the left: https://topdowndatabase.com/#/air_temperature |
Thanks, I also see the issue on your website when using Chrome. However, I was not able to create a minimal project reproducing the issue. I tried a vanilla website, a Typescript React website created with Could you give more details on how you created your dashboard? Like the React template you used, the versions of react, mapbox-gl |
I created version 1.6.2 which does not throw any error when an extension cannot be loaded (only an error message is logged). Could you check if that works now? |
Not 100% what I'm doing wrong here, I get this error after the map has loaded:
Uncaught WebGL extension EXT_color_buffer_float not supported
I think I followed the documentation correctly
I checked my browser support and it does support that extension
A sample of my code:
`
const map = new mapboxgl.Map({
container: this.$refs.map,
style: 'mapbox://styles/mapbox/light-v10',
zoom: 7,
pitch: 0,
center: [5, 51]
});
map.on('load', () => {
const points = this.locations.map((o) => ({ lat: o.latitude, lon: o.longitude, val: o.complexityScore }))
});
`
Any idea what could be happening?
The text was updated successfully, but these errors were encountered: