-
Notifications
You must be signed in to change notification settings - Fork 348
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
why cesium can not display the terrain? #110
Comments
@Brilliant-orange I faced the same problem. Unzipping generated tiles solved the issue for me. |
|
写.terrain时,不能用gzwrite,那样写不出正确的.terrain,而是用fwrite方式. void Terrain::writeFile(const char fileName) const
}
} |
|
|
I know its been over a year since this issue was opened, but figured I'd leave this here in case anyone else is experiencing this issue. Rather than unzipping the gzipped terrain tile, what solved it for me was that I had to configure my server to set the following headers for
These links helped me figure this out. tum-gis/cesium-terrain-builder-docker#8 (comment) |
There was a problem loading the terrain in cesium. The cesium globe displays normally after removing the terrain.
In cesium1.96, chrome displays the following error:
Cesium.js:85 An error occurred in "Py": Failed to obtain terrain tile X: 0 Y: 0 Level: 0. Error message: "RangeError: Invalid typed array length: 8894653434"
Cesium.js:85 An error occurred in "Py": Failed to obtain terrain tile X: 1 Y: 0 Level: 0. Error message: "RangeError: Invalid typed array length: 2017542741"
cesium code like this:
var terrainProvider1=new Cesium.CesiumTerrainProvider({
url:"http://localhost:9000/"
});
const viewer = new Cesium.Viewer("cesiumContainer", {
baseLayerPicker: false,
imageryProvider: imageryProvider,
terrainProvider:terrainProvider1
});
viewer.scene.globe.enableLighting=true;
However, in the latest cesium, chrome does not output any errors and just does not display the globe.
How can I solve this problem? @homme @thomas001 @chris-cooper @tmizu23 @kyosho-
The text was updated successfully, but these errors were encountered: