3 ms·
Just to contribute: yet another instance of "cool slideshow" on my (most definitely low end) laptop with integrated graphics. Then tried it on my aging Mate 20
by exikyut 3y ago
Just to contribute: yet another instance of "cool slideshow" on my (most definitely low end) laptop with integrated graphics.
Then tried it on my aging Mate 20 Pro (not too new, not tooo old), and it just seemed to get stuck at "Downloading runtime". Got a funny feeling my flaky 4G wasn't actually to blame, inspected the tab from my laptop (chrome://inspect) via USB, and was greeted with
Uncaught (in promise) Error: Needs OES_texture_float_linear to function
at M (worker-3ec07b2e.js:1:3338)
at J (worker-3ec07b2e.js:1:3403)
It is what it is. It's a good philosophical question about whether it's worth coding up an error screen, since it's all just to tell people they can't play with the toy. Hehe.
- murkle 3y agohttps://github.com/evanw/OES_texture_float_linear-polyfill https://github.com/evanw/OES_texture_float_linear-polyfill
- TrevorSundberg 3y agoHmm, I think that polyfill might only be for WebGL1 (we use WebGL2). When I go to the WebGL1 report I see that my card supports both: OES_texture_float OES_texture_float_linear But on WebGL2, it only shows OES_texture_float_linear. I think OES_texture_float doesn't exist on WebGL2 I'm guessing.
- xeonmc 3y agoHow low end is it? I'm using my 8-year-old Surface Pro 4 on Starbucks wifi and it's blazing fast.