-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Corridor renders from Primitive API but not Entity API #4829
Comments
Related forum posts: Another example: positions : Cesium.Cartesian3.fromDegreesArray([
43.0298791905732,30.3249511347621,
43.0535143723772,30.3254863499896,
43.0531351413855,30.217161279318,
43.0300902644761,30.2171721034287,
43.0298791905732,30.3249511347621
]), |
From @mramato
|
I think I am having the same issue, but with polylines. I get the z-fighting you referenced in the related issue. Is there a fix for this yet? I have an example on the sandcastle running this code:
|
Hi @CHBaker. Polylines don't have a |
@hpinkos hmmm. I saw some posts about adding this feature in 2015, guess it never got added. The problem I have is two polylines crossing at a perfetc '+' sign, but when you zoom in one is floating above the other, so when you ctrl + click to move perspective the lines move a lot and do not lay directly on top of each other. This only occurs once you zoom in very close, they lay directly on top of each other, but once cesium renders as close as you can get, they don't appear on top of each other |
@CHBaker try changing the value of the granularity attribute. This is a value in radians that specifies the distance at which the line should be subdivided and pushed to the ellipsoid surface. Here's an illustration to show what I'm talking about: For a really large number, the line will just cut through the ellipsoid. A smaller value will break the line up to better fit the curvature. By default, it subdivides the line each degree ( |
Alright, I think that did it, thanks! |
From #4326
This corridor renders:
But this one doesn't
The text was updated successfully, but these errors were encountered: