[[TracNav(TracNav/TOC)]]
= osgVisual configuration =
To use osgVisual, you have to configure osgVisual according to your needs.
Basiccally, osgVisual provides two configuration mechanisms:
* Via commandline parameters
* Via configuration file
== Configuration via parameters ==
osgVisual is build on top of !OpenSceneGraph. The core module is osgViewer which provides all the background technology to render the scene graph on the screen. You can use all osg related command line options by adding these options to osgVisual.
To get an overview of the available parmeters, execute
{{{
#!sh
osgviewer --help
}}}
or go to http://www.openscenegraph.org
== Configuration via configuration file ==
For all options which are not OSG but osgVisual related, the configuration mechanism is an XML configuration file. This file contains sections for each module to configure and for the scenery to display.
Example of a configuration file with module and scenery configuration:
{{{
}}}
=== Module configuration ===
The "module" sections are parsed while instantiation the modules at the beginning of the startup process.
Each module configuration contains at least the name and the enabled/disabled status of the module. Further module parameters are optional and module dependent.
Some modules ignore the "enabled" attribute because they are mendatory in osgVisual. If a module is compiled and used in osgVisual but the correpsonding XML entry is not available in the configuration file, the modules will raise an error and remain unconfigured. The behavior of an unconfigured module is unpredictable and hence should be avoided.
Example:
{{{
#!xml
}}}
A full list of all available modules with their XML configuration options is [wiki:XmlModuleConfiguration available].
=== Scenery configuration ===
==== Terrain ====
Example:
{{{
#!xml
}}}
==== Sky/Weather ====
Example:
{{{
#!xml
}}}
==== Models ====
Example:
{{{
#!xml
}}}