log depth interpolation not handled correctly for large geometries
See original GitHub issueOur “big” geometries aren’t tessellated enough for log depth to interpolate correctly right now, which causes issues that look kind of like near-plane problems but don’t present as a planar cut:

I’m pretty sure it’s the “minimum tessellation” problem (described here: http://outerra.blogspot.sk/2009/08/logarithmic-z-buffer.html) because adding #define ENABLE_GL_POSITION_LOG_DEPTH_AT_HEIGHT to the top of vertexLogDepth.glsl seems to fix the problem.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:16 (14 by maintainers)
Top Results From Across the Web
Logarithmic Depth Buffer - Game Developer
Using logarithmic depth buffer to get rid of Z-fighting and near plane clipping in large-scale planetary rendering.
Read more >Maximizing Depth Buffer Range and Precision - Outerra
The problem is that the vertex shader computed value is correct only at the vertices, but the interpolated values at pixels can stray...
Read more >6.0 - HEC-RAS Known Issues
If the dataset had more than 1 mesh, and more than one mesh was in view, then the courant map would render incorrect...
Read more >Types of Interpolation - Advantages and Disadvantages
This technique is designed to honour local minimum and maximum values in the point file and can be set to limit overshoots of...
Read more >Use Azure Kinect Sensor SDK image transformations
Input parameters are the transformation handle and a depth image. ... Using nearest neighbor interpolation will prevent values not present ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Congratulations on closing the issue! I found these Cesium forum links in the comments above:
https://groups.google.com/d/topic/cesium-dev/kMZIgIa6lqQ/discussion https://groups.google.com/forum/#!topic/cesium-dev/NZwZnQnmC2U https://groups.google.com/forum/#!topic/cesium-dev/WhCZhIUaJIQ https://groups.google.com/d/msg/cesium-dev/hsPdXyBATS4/zNF17JkFCAAJ https://groups.google.com/d/msg/cesium-dev/fXHvE2psXD4/t181NoF1AgAJ
If this issue affects any of these threads, please post a comment like the following:
Came up again here: https://groups.google.com/d/msg/cesium-dev/fXHvE2psXD4/t181NoF1AgAJ