Building Efficient MetaFlight Terrains for 3D Network Visualizer

3D Network Visualizer can only load MetaFlight terrains built with certain tools. All MetaFlight files must be pre-processed by 3D Network Visualizer tools before they can be loaded into 3D Network Visualizer. The following are recommendations for constructing MetaFlight terrains that can be processed and loaded into 3D Network Visualizer:

  • The MetaFlight terrain can contain one or more Geometry Grid Datasets (GGDS).
  • The MetaFlight terrain can contain one or more Virtual Texture Datasets.
  • The MetaFlight terrain can contain one or more Cultural Feature Datasets.
  • The MetaFlight terrain can be built in the following coordinate systems: Geodetic, Geocentric, UTM, or Flat Earth.
  • For the best conversion of Virtual Textures into a tiled texture GGDS, match every Virtual Texture layer with a geometry layer.
  • For optimal performance the GGDS should be set up in a Pyramid structure (Level 1: 1x1, Level 2: 2x2, Level 3: 4x4, and so on).
  • For optimal performance, levels 1-4 should be made of FILE LOD GEOM tiles only. Do not put any children LOD GEOM tiles in these levels.
  • For optimal performance the terrain should be balanced so any single FILE LOD GEOM is not too large and can be paged in real-time (based on machine speed and video card.). In other words, keep any single file small.
  • For optimal performance any single FILE LOD GEOM should not contain too many LOD GEOM nodes as children
  • Geometry Grid Tile size (in meters) should match Virtual Texture Tile coverage (in meters.)
  • For optimal performance limit the number of external references. This will reduce cull times. (For example, instead of having 10 individual buildings, externally reference one city block with all 10 buildings.)