在 2018年7月10日星期二 UTC+8上午3:33:21，Gabby Getz写道：
Yes, the geometric error is used to determine the screen space error (SSE) for the tile. If the width of the tile in pixels is greater than the SEE, the tile is rendered. The bottom-most children tiles will generally have a geometric error close to 0. You can start with determining the geometric error og the the root tile, and divide by two for each successive LOD. So for instance, if your root tile has an error of 100, the next LOD would have 50, etc.
On Sunday, July 8, 2018 at 10:40:49 PM UTC-4, karl...@gmail.com wrote:Hi Gabby
Thank you, I read that document,and as I understand that,in the usual way, each model is already split into layers of parent and children and children's children, so I should just give them suitable geometricError values to be displayed at different distance of the camera, thus LOD, right?
The last few days I've been studying the New York demo, after I downloaded the data(https://s3.amazonaws.com/cesiumjs/3DTiles/NewYorkCityGml.zip), T can't open the json file(tileset.json) in Chrome nor notepad, it just show messy, and to put it into VS2017 it shows a binary code, is it encrypted or I just don't know the right way?
And I can't use that data, putting that json file into localhost shows nothing.
As a matter of fact, to load these 700MB models Cesium need more than 1.5GB of RAM, to load my own 1.2 GB models Cesium need nearly 2GB of RAM. For it's your official demo, is there really not some better way to improve that?
Never the less, the New York demo is still much more fluent than mine.It's not the RAM usage problem, I was thinking of LOD, since I can't read the json file, could you please tell my how did you deal with the New York demo?