Skip to content
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 does decreasing the error target cause tiles to load for so much longer to the same spot? #376

Open
gkjohnson opened this issue Jun 19, 2023 · 2 comments
Milestone

Comments

@gkjohnson
Copy link
Contributor

Change the error target to 6 and open the google tiles aerial view.

@gkjohnson gkjohnson modified the milestones: v0.3.21, v0.3.20 Jun 19, 2023
@gkjohnson
Copy link
Contributor Author

gkjohnson commented Jun 22, 2023

Likely because at least the whole environment afar is still loading and when the error target is lower then it takes longer for the far off tiles to reach a loaded state.

  • The "priorityCallback" function could be possibly updated to be sorted differently based on closer tiles, etc.
  • Perhaps the apparent calculation for screenspace error can increase quadratically based on distance?

@gkjohnson
Copy link
Contributor Author

Looks like Cesium uses a single "priority" value rather than a waterfall-style fallback compare:

https://github.com/CesiumGS/cesium/blob/22658a56b57b671c815647bf00ed08be8565901f/packages/engine/Source/Scene/Cesium3DTile.js#L2239-L2247

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant