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

Custom Model rendering issue/default Cesium rendering issue #8562

Closed
devond5 opened this issue Jan 22, 2020 · 3 comments · Fixed by #8600
Closed

Custom Model rendering issue/default Cesium rendering issue #8562

devond5 opened this issue Jan 22, 2020 · 3 comments · Fixed by #8600

Comments

@devond5
Copy link

devond5 commented Jan 22, 2020

ForCesium.zip

Attached in the Zip file is the model I am using and a video of the issue I am seeing for your reference.

I work for a company that is using a more detailed model of the one provided, and are seeing this model rendering issue. It is prominent when the model is loaded into a cesium sandbox. However, I also loaded the model into the gltf vs code extension and saw a similar result. The thing that makes me think this is a Cesium problem is from the video you can see I first view the model and animations in Babylon.js and there are no issues, but when I view the model from the Cesium model preview I see the problem. The filament sheet when it is close or intersecting another object with some camera changes there is a blending issue. For instance, if you rotate to the bottom of the model after the animation, the filament is clearly intersecting the black rectangle but with a move of the camera the filament is more prominent and the black rectangle is hidden. Also when the filament is fully animated and you rotate around the purple filament brace blends through the filament.

This is a problem for my employer because the accuracy of the model is of the upmost importance. The modelers of the model have also tried adding UV's and image maps but that did not solve this.

In the sandcastles I have messed around with frustums, camera properties, etc. I was not able to find an immediate solution.

While you are looking at this issue and determine it is something on the model side that needed to be changed to fix this then let us know what it is so that our modelers can determine how to create for Cesium users, but I would think that cesium out of the box should be able to handle models the way babylon.js or three.js can.

Cesium Version: "1.61.0"
Sandcastle example: Load attached glb or gltf into the 3D models sandcastle to see the blending problem.

Browser: Chrome 79.0.3945.117

Operating System: Windows 10 Enterprise(1809)

Devon Despain

@sanjeetsuhag
Copy link
Contributor

sanjeetsuhag commented Jan 22, 2020

@devond5 This is a known issue related to logarithmicDepthBuffer.

Turning this option off makes the bottom of the box visible through the filament:

viewer.scene.logarithmicDepthBuffer = false;

@devond5
Copy link
Author

devond5 commented Jan 29, 2020

Perfect we were tying to figure this out for the longest time!!

@devond5 devond5 closed this as completed Jan 29, 2020
@mramato mramato reopened this Jan 29, 2020
@mramato
Copy link
Contributor

mramato commented Jan 29, 2020

@devond5 I'm glad you are happy with this workaround, but I've re-opened this issue since it should be fix for when the depth buffer is enabled as well.

@lilleyse lilleyse mentioned this issue Feb 7, 2020
7 tasks
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

Successfully merging a pull request may close this issue.

3 participants