change google earth terrain to grass lumenrt

The UpdateTerrainPositionsAndNeighbors() method is the core function here. It is the same 9 tiles over and over again. I've positioned the camera to highlight how the chunking works. We have 9 terrain tiles with random noise heightmaps and as the camera moves the tiles behind us are recycled and moved to in front of us. Here are some scripts to illustrate the basic concept of 'streaming terrain chunks'. Reduce fidelity of heightmaps or elevation data Reduce number of tiles loaded in memory at onceĭistribute tile loading across multiple frames using coroutines Keep frustum in centre/ keep tiles near originĮach tile has lat/lon independent of world spaceĮach tile gets imagery splat texture from disk, cache, remote server Terrain built at runtime not serialised in scene, dynamically constructedĭatabase used to persist tiles and objects and stuff Solution: Streaming terrain in any directionįundamental ideas - Stream terrain around frustum

Visible symptoms at 60 100,000m float errors are 0.0078m componded up the transform stack at 60 fps Have gaps between the 2^32 values on a 2^129 domain Render meshes for terrain and other objectsĪI/ Behaviour - increases complexity by #objects^2 Solving the Continuous World Problem is not easy (who knew?) and the solution is a work in progress.

Change google earth terrain to grass lumenrt