Loading Terrain (Context Capture)

RSET can handle auto-importing tilesets in Context Capture-styled formats. These are still .obj files but RSET expects them to be in a particular folder structure. For example:

• Sample_Terrain_Set/

  • Data/

    • Tile_+000_+006/

      • Tile_+000_+006_L16.mtl

      • Tile_+000_+006_L16.jpg

      • Tile_+000_+006_L16.obj

      • Tile_+000_+006_L17.mtl

      • Tile_+000_+006_L17.jpg

      • Tile_+000_+006_L17.obj

      • Tile_+000_+006_L18.mtl

      • Tile_+000_+006_L18.jpg

      • Tile_+000_+006_L18.obj

    • Tile_+000_+007/

      • <tile files>

    • <More Tiles>

The structure above is comprised of a parent folder (which contains a data folder and some metadata), a Data folder (which contains potentially hundreds of subfolders, one for each Tile), and tile subfolders (which contain 1 or more sets of 3D Data). Each "set" of 3D data is an .obj file that defines the 3D data, an .mtl file that dictates the material properties, and one or more image texture files. In the example above, Tile 000_006 has three "sets" of 3D data, each a different "Level of Detail" for the tile. Higher level of details will have higher poly counts and higher image resolutions, but take longer to load and use more memory. Some terrain datasets will be impossible to load if you choose too high of a LOD when importing the terrain.