-
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
Clipping planes don't work on certain Android devices #8061
Comments
here's my webglreport:
|
@zhangwenjin what kind of phone is it? Your WebGL report screenshot is missing the "platform/vendor/renderer" information at the top which is relevant here. |
@OmarShehata To see draft extensions in Chrome, browse to about:flags, enable the "Enable WebGL Draft Extensions" option, and relaunch. WebGL 2 Functions Implementation Status: copyBufferSubData |
Several tpye of Huawei mobile phones have been tested,clipping planes don't work at all |
Brought up on the forum.
On my Pixel 3 phone, clipping planes don't work at all. I can see the plane moving but it's as if the
discard
isn't doing anything. Testing this on the clipping planes Sandcastlehttps://cesiumjs.org/Cesium/Apps/Sandcastle/index.html?src=3D%20Tiles%20Clipping%20Planes.html
I thought it might be when we changed clipping planes from passing uniforms, to packing it into a texture, which was in 1.44, but trying the 1.43 version also doesn't work (try the model in the drop down):
https://cesiumjs.org/releases/1.43/Apps/Sandcastle/index.html?src=3D%20Tiles%20Clipping%20Planes.html&label=Showcases
Here's my WebGLReport on this phone:
Interestingly, it works on @likangning93 's much older Android, which is also Qualcomm but is an Adreno (TM) 308.
The model does sort of shimmer a bit, so you can tell that something is happening. On the globe clipping planes, the result is different:
The only one that seems to work is isolating a piece of terrain, but this is only because of the CPU clipping full tiles, still not actually successfully discarding fragments:
The text was updated successfully, but these errors were encountered: