When operating mouse by double click or zooming in to make viewpoint quickly fly from a high position (eg. pyramid level = 1) to a low position (eg. pyramid level = 15), the tiles on each level of pyramid spanned by the track will be called and draw. When the viewpoint has arrived at the endpoint for a while, the tiles are still refreshing and the high resolution tiles cannot be drew quickly, which make operators feel the refreshing is not very smooth.
I find cesium calculates the current tile id by quartering its father node, instead of calculating it by the level of endpoint and the range of the window. So all the tiles along the track will be calculated and refreshed, which delays the appearance of last tiles who has the highest resolution in the track.
I am wondering whether my guess is right. If it is, why cesium choose such a method to schedule tiles. Does anyone knows the way to refresh the tiles on the level of endpoint directly (like google earth’s or skyline’s way), without schedule and draw the tiles in the middle.