-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Classification example broken under WebGL 2 #8629
Comments
Same behavior in Firefox and with my laptop's integrated GPU ( |
Lots of stuff is broken under WebGL2, it's going to take a concerted effort to fix/validate/maintain it and given the current WebGL2 adoption rate, it hasn't been a priority. |
From https://caniuse.com/#search=webgl2 with 74.31% usage, it seems that webgl2 is ready to be commonly used. |
Ah cool, I wish it could break down support by WebGL extension but it's better than nothing. |
Actually I take that back. See https://caniuse.com/#search=EXT_frag_depth |
Yeah, caniuse is awesome, I just never noticed the stats in the upper right before. Pretty sad that frag depth is that low. Is an extension still needed for it in WebGL2? |
frag depth is core in WebGL 2 (and probably others) 74.31% support of WebGL 2 kinda makes a much better case for switching if we can get all the features that were previously WebGL 1 extensions. |
Stuff like this is what I'm most excited about, a lot of mobile devices that can support extensions like this don't, but their WebGL2 implementation does, so it's a big win for Cesium. |
Zero support for WebGL2 on Safari, though, which is probably irrelevant on desktop but a problem on iOS. 😠 |
I'm closing this since CesiumJS does not officially support WebGL 2, but it is on the roadmap, so we can consolidate known bugs and discussion in this issue: #797 (comment). |
The Classification Sandcastle example works fine under WebGL1. However, when I switch to WebGL2 by changing the first lines to:
The classification no longer works correctly.
WebGL1
WebGL2
Chrome, Windows 10, renderer:
ANGLE (NVIDIA GeForce GTX 1650 Direct3D11 vs_5_0 ps_5_0)
The text was updated successfully, but these errors were encountered: