-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
3D tiles bounding volumes don't move with tileset modelMatrix #5984
Comments
This came up on the forum too: https://groups.google.com/forum/#!topic/cesium-dev/OIP2B_UgGns I started to investigate but realized this was only affecting tilesets that use From the spec:
https://github.com/AnalyticalGraphicsInc/3d-tiles#tile-transform |
Congratulations on closing the issue! I found these Cesium forum links in the comments above: https://groups.google.com/forum/#!topic/cesium-dev/OIP2B_UgGns If this issue affects any of these threads, please post a comment like the following:
I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome. 🌍 🌎 🌏 |
@lilleyse this is a problem because the point cloud flickers a lot as you move the camera. Is it being culled incorrectly or something because the points are no longer inside the bounding volume? //Point Cloud by Prof. Peter Allen, Columbia University Robotics Lab. Scanning by Alejandro Troccoli and Matei Ciocarlie.
var viewer = new Cesium.Viewer('cesiumContainer');
viewer.extend(Cesium.viewerCesium3DTilesInspectorMixin);
viewer.terrainProvider = new Cesium.CesiumTerrainProvider({
url : 'https://assets.agi.com/stk-terrain/v1/tilesets/world/tiles',
requestWaterMask : true,
requestVertexNormals : true
});
var chappes = viewer.scene.primitives.add(new Cesium.Cesium3DTileset({
url : 'https://beta.cesium.com/api/assets/1460?access_token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJqdGkiOiIyMzk2YzJiOS1jZGFmLTRlZmYtYmQ4MS00NTA3NjEwMzViZTkiLCJpZCI6NDQsImFzc2V0cyI6WzE0NjBdLCJpYXQiOjE0OTkyNjQ3NTV9.oWjvN52CRQ-dk3xtvD4e8ZnOHZhoWSpJLlw115mbQJM'
}));
chappes.readyPromise.then(function() {
var cartographic = Cesium.Cartographic.fromCartesian(chappes.boundingSphere.center);
var surface = Cesium.Cartesian3.fromRadians(cartographic.longitude, cartographic.latitude, 0.0);
var offset = Cesium.Cartesian3.fromRadians(cartographic.longitude, cartographic.latitude, 415.49299710114906); //2.9262921309980063, 46.388339804887515, 415.49299710114906
var translation = Cesium.Cartesian3.subtract(offset, surface, new Cesium.Cartesian3());
chappes.modelMatrix = Cesium.Matrix4.fromTranslation(translation);
});
viewer.camera.flyTo({
destination: new Cesium.Cartesian3(4401822.465194312, 225035.28458448383, 4595539.250208599),
orientation: {
heading: 5.404892352900644,
pitch: -1.4530591151917136,
roll: 6.260800942147647
}
}); |
Should Cesium throw a |
One other thing we could do is let the transform happen, but transform the underlying oriented bounding box and not touch the region. It's possible this will cause other side effects though. |
Another issue from the forum: https://groups.google.com/forum/#!topic/cesium-dev/rUFnzb0d14o |
Brought up on the forum: https://groups.google.com/forum/#!topic/cesium-dev/j-8uQL0lJTo |
Another forum post: https://groups.google.com/forum/#!topic/cesium-dev/DE_iV6WAZcs I submitted a PR to fix this, if we decide to allow transforms to move regions. #6755 |
Congratulations on closing the issue! I found these Cesium forum links in the comments above: https://groups.google.com/forum/#!topic/cesium-dev/OIP2B_UgGns If this issue affects any of these threads, please post a comment like the following:
I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome. 🌍 🌎 🌏 |
With the chappes church point cloud model:
The text was updated successfully, but these errors were encountered: