This page has been translated automatically.
Interface Overview
Assets Workflow
Settings and Preferences
Adjusting Node Parameters
Setting Up Materials
Setting Up Properties
Using Editor Tools for Specific Tasks
Setting Up Development Environment
Usage Examples
UUSL (Unified UNIGINE Shader Language)
File Formats
Rebuilding the Engine and Tools
Double Precision Coordinates
Common Functionality
Controls-Related Classes
Engine-Related Classes
Filesystem Functionality
GUI-Related Classes
Math Functionality
Node-Related Classes
Networking Functionality
Pathfinding-Related Classes
Physics-Related Classes
Plugins-Related Classes
CIGI Client Plugin
Rendering-Related Classes
Warning! This version of documentation is OUTDATED, as it describes an older SDK version! Please switch to the documentation for the latest SDK version.
Warning! This version of documentation describes an old SDK version which is no longer supported! Please upgrade to the latest SDK version.

Procedural Refinement

Procedural refinement system, makes it possible to improve the quality of generated terrain using Houdini Digital Assets. Procedural refinement can be used for:

  • height data correction (erosion, riverbeds, etc.)
  • landcover masks improvement (smoothing, etc.)
  • generation of high-resolution detail masks

In order to use procedural refinement Houdini Engine version must be installed on your computer. You can download and install it by clicking here.

Please note, that trial version does not allow to use Houdini assets in the Landscape Tool.

Windows: After installing Houdini you should add Houdini binary location to the PATH environment variable.

Linux: After installing Houdini you should add location of the (e.g., /opt/hfs16.0/dsolib) to the LD_LIBRARY_PATH environment variable.

A procedural data source is assigned with a Houdini digital asset (*.hda file) and can be used to refine data from elevation and landcover data sources. It can also be used to refine the data produced by another procedural data source. The area for which refinement is to be performed is determined by an adjustable bounding rectangle, which can be manually placed inside the Play Area on the Preview panel.

Due to the equirectangular projection, it looks like a trapezium near the terrestrial poles.

There are two procedural refinement workflows:

  • Basic workflow (described below): you have a Houdini digital asset (a set of assets) that performs all necessary data refinement.
  • Custom workflow: there is no Houdini digital asset available to perform necessary refinement. In this case you have to create a new houdini digital asset.

The basic workflow is as follows (assuming necessary elevation and landcover data sources are added, see Specifying Data Sources section).

  1. In the Sources panel, add a procedural data source.

  2. Select a procedural data source you added in the Data Sources panel and adjust its bounding rectangle on the Preview panel (to indicate the area, for procedural refinement).

    If the bounding rectangle of a procedural data source is larger than the Play Area specified, procedural refinement calculations will be performed for this larger area. This may significantly increase generation time.

  3. Specify the following data source parameters in the Parameters panel.

    Density The density of the procedural data source, in meters per pixel. A procedural data source grabs the data for the Houdini asset from underlying data sources with the set density value (upsampling is performed if necessary).
    Asset path The path to the Houdini digital asset (*.hda file) that performs data refinement.
    Processing order Priority of the data source in the whole generation process.
    For more information see the Processing Priority section.
    Houdini parameters The list of parameters required by the selected Houdini digital asset (if any). These parameters are specified when the digital asset is created and are used to pass certain numerical values or tags from the Landscape Tool to configure refinement procedure (e.g. you can specify landcover tags to be treated by the Houdini asset as rivers for elevation adjustment).
    Currently supported types include float, integer, dropdown list.
    Landcover tags The list of tags of all underlying landcover data sources. If the bounding rectangle of the procedural data source covers (completely or partially) a landcover data source, all tags of the latter will be added to this list.
    A Houdini asset can generate its own landcover tags on the basis of input data. To add these tags to the list of available landcover tags use Update landcover tags button.
  4. You can add as many procedural data sources as necessary.

Last update: 2019-11-28
Build: ()