We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Sandcastle code (existing example):
var positions = ellipsoid.cartographicArrayToCartesianArray([ Cesium.Cartographic.fromDegrees(-120.0, 45.0), Cesium.Cartographic.fromDegrees(-125.0, 50.0), Cesium.Cartographic.fromDegrees(-125.0, 55.0) ]); var width = 100000; var corridorFill = new Cesium.GeometryInstance({ geometry: new Cesium.CorridorGeometry({ positions : positions, width : width, vertexFormat : Cesium.PerInstanceColorAppearance.VERTEX_FORMAT, height: 700000 }), attributes : { color : Cesium.ColorGeometryInstanceAttribute.fromColor(Cesium.Color.fromRandom({alpha : 1.0})) } });
Depending on the view, the corridor is not shown in the closer frustum:
Most likely the bounding sphere is wrong. Use command. debugShowBoundingVolume in the primitive to debug.
command. debugShowBoundingVolume
This doesn't need to holdup b20.
The text was updated successfully, but these errors were encountered:
@pjcozzi I think @hpinkos fixed this in #1099. Could you check? I wasn't able to reproduce the issue.
Sorry, something went wrong.
yeah, the bounding sphere was incorrect before so if that was the cause of the issues it should be fixed now.
Looks good.
No branches or pull requests
Sandcastle code (existing example):
Depending on the view, the corridor is not shown in the closer frustum:
Most likely the bounding sphere is wrong. Use
command. debugShowBoundingVolume
in the primitive to debug.This doesn't need to holdup b20.
The text was updated successfully, but these errors were encountered: