Graphics.NewbieDougConfigFile - lordmundi/wikidoctest GitHub Wiki
Newbie Doug Config File
« Appendix | NewbieIndex | Doug Commandline »
The Doug config file is the main user interface for setting up a doug session. The config file is daunting to my newbiehood, so I will glean what I can at this point… and offer hooks for further elaboration.
Brad, the Doug Guru, says, paraphrased: Generally there is a block for each type of application in the DSP software set (MANAGER, CACHE, DISPLAY, and DOUG). Then there are the supporting data sub-blocks in the DATA block (SCENE_LOAD, HELMETS, CAMERAS), with the SCENE_LOAD sub-block having its optional sub-blocks (CONTROLS, CAMERAS, MODELS, LIGHTS,GROUPS). Each application block can have optional PLUGINS and COMMAND_LINE blocks with the DOUG application also supporting the GUI block. Each display application (dsp_viewer, doug) also requires at least one CHANNEL# block defining the window/display configuration etc. Additionally, configuration files can and usually do contain additional user defined blocks that are not processed at all by DOUG.
Config File Syntax
Example : Click Here For Example
Blocks : Stuff in curlies are "blocks". The name of the block precedes the open curly. Blocks are arranged in a tree. Each line in a block is logically separate from the next.
Comments : Use the hash (#)
Environment Vars : Specify environment variables like so: ${MY_ENV_VAR}
Order Is Important
Config files may have blocks labeled PRELOAD and POSTLOAD. Config files are parsed one at a time with all files in the order specified in the PRELOAD block (if any) preceeding the current file and all POSTLOAD files in the order specified in the POSTLOAD block (if any) following the current file.
Existence Is Not Important
If a POST/PRELOAD file is non-existent, it is silently ignored.
Tree Brokendown
- DSP_CONFIG
- LENSFLARE_INFO
- DSP_TRACKCAM
- DSP_SCRIPT
- COMM_FLAGS
- DSP_LODLOADER
- SOCKET_COMM
« Appendix | NewbieIndex | Doug Commandline »