Skip to content
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

skined model show a wrong effect #8875

Closed
lafflan opened this issue May 25, 2020 · 6 comments
Closed

skined model show a wrong effect #8875

lafflan opened this issue May 25, 2020 · 6 comments

Comments

@lafflan
Copy link

lafflan commented May 25, 2020

the model was export from blender2.82, when i load it by cesium, it seems like has some problems about transparent or depth:

wrong

but when view from top of the model ,it looks normal:

top

i test in threejs and gltf-viewer, both have no problem.

here is the model:
miner.zip

@lilleyse
Copy link
Contributor

@sweerwen it looks like this is the same problem as #6447.

A workaround is to set viewer.scene.logarithmicDepthBuffer = false;

@lafflan
Copy link
Author

lafflan commented May 26, 2020

@sweerwen it looks like this is the same problem as #6447.

A workaround is to set viewer.scene.logarithmicDepthBuffer = false;

thanks @lilleyse , it works. but when set viewer.scene.logarithmicDepthBuffer = false;, whether it will cause other problems?

@lilleyse
Copy link
Contributor

@sweerwen In general it should be okay but there are some known issues like

#4381
#7705

I think we might be able to fix #6447 pretty soon and not require the workaround here.

@lafflan
Copy link
Author

lafflan commented May 26, 2020

I think we might be able to fix #6447 pretty soon and not require the workaround here.

@lilleyse glad to hear that, thanks for your contribution.

@lafflan
Copy link
Author

lafflan commented May 26, 2020

just tested when set log depth to false on HDR page then switch the HDR checkbox,it crashed. but comment this line //viewer.scene.highDynamicRange = true;, has no problem.

@lilleyse
Copy link
Contributor

@sweerwen that sounds like this bug possibly: #8372

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants