I create a tile set for testing. Usually i use the 3D tile inspector example to load the tile set, and it works fine with Cesium before version 1.47. But when i use the same example to the tile set in Cesium after(include) version 1.47, When the terrain loaded, the tile set disappeared.
Old version
https://drive.google.com/open?id=1JEH11jaoNT0pFZi7Q0h6akYUdkTJ393-
Before the terrain loaded
https://drive.google.com/open?id=1I7Jv6mH2vShUapnMBX_GXR028gIU_xZv
Tileset disappered
https://drive.google.com/open?id=17QzBbb-nP2KeUAWswjsfDJQHgPQ4Vu-C
The test tileset
https://drive.google.com/open?id=1JEEesgg3IRWS9qZXgdIUwGjsw5SNq36W
I only change the code in 3D tile inspector example like:
var viewer = new Cesium.Viewer('cesiumContainer'
, {
terrainProvider: Cesium.createWorldTerrain()
}
);
viewer.scene.globe.depthTestAgainstTerrain = true;
viewer.extend(Cesium.viewerCesium3DTilesInspectorMixin);
var inspectorViewModel = viewer.cesium3DTilesInspector.viewModel;
var tileset = new Cesium.Cesium3DTileset({
// url: Cesium.IonResource.fromAssetId(5741)
url: "../../SampleData/testtile/tileset.json"
});
viewer.scene.primitives.add(tileset);
What could i do to prevent situation like this? Modify the tiles.json? Call some api to set the scene correctly?
I test it with Cesium 1.45 and 1.48. OS is Windows 10, Browser is chrome.
Hi there,
It sounds like the features in your tileset are positioned under terrain. This is determined at tiling time when you create the tileset. Where did you create the tileset?
Thanks!
Gabby
Gabby Getz於 2018年8月21日星期二 UTC+8上午4時42分57秒寫道:
Hi there,
It sounds like the features in your tileset are positioned under terrain. This is determined at tiling time when you create the tileset. Where did you create the tileset?
Thanks!
Gabby
On Wednesday, August 15, 2018 at 1:43:12 AM UTC-4, seane...@gmail.com wrote:I create a tile set for testing. Usually i use the 3D tile inspector example to load the tile set, and it works fine with Cesium before version 1.47. But when i use the same example to the tile set in Cesium after(include) version 1.47, When the terrain loaded, the tile set disappeared.
Old version
https://drive.google.com/open?id=1JEH11jaoNT0pFZi7Q0h6akYUdkTJ393-
Before the terrain loaded
https://drive.google.com/open?id=1I7Jv6mH2vShUapnMBX_GXR028gIU_xZv
Tileset disappered
https://drive.google.com/open?id=17QzBbb-nP2KeUAWswjsfDJQHgPQ4Vu-C
The test tileset
https://drive.google.com/open?id=1JEEesgg3IRWS9qZXgdIUwGjsw5SNq36W
I only change the code in 3D tile inspector example like:
var viewer = new Cesium.Viewer('cesiumContainer'
, {
terrainProvider: Cesium.createWorldTerrain()
}
);
viewer.scene.globe.depthTestAgainstTerrain = true;
viewer.extend(Cesium.viewerCesium3DTilesInspectorMixin);
var inspectorViewModel = viewer.cesium3DTilesInspector.viewModel;
var tileset = new Cesium.Cesium3DTileset({
// url: Cesium.IonResource.fromAssetId(5741)
url: "../../SampleData/testtile/tileset.json"
});
viewer.scene.primitives.add(tileset);
What could i do to prevent situation like this? Modify the tiles.json? Call some api to set the scene correctly?
I test it with Cesium 1.45 and 1.48. OS is Windows 10, Browser is chrome.
I put the scene at 121.5478805,25.0350183,300(lat,lon,height), after i change the height to 600, tileset appears in the sky. So if some models in the tile is underground, the whole tile will not show?
So you modified the values in the tileset JSON file directly to do that, correct?
If so, you should update the bounding volumes too. That’s what Cesium used to determine if a tile is visible or not, not the location of the content directly.
If some (or all) of the tilesets are underground, it will still render. Sorry to confuse.