Newbie Doug Environment

« | NewbieIndex | »

The .doug_cshrc, located where I unpacked Doug, and sourced from the run_graphics script sets up the environment. It assumes $DOUG_HOME is already set. I am going to guess at what environment variables do what.

I feel like a detective. And I'm beginning to question what is Doug and what is an Application Of Doug and where the lines blurr in the config files, environment, paths etc.

| Home | || | setenv DOUG_HOME pwd | | DOUG_HOME must be set first. This is the location where Doug is unpacked to. Out of the box, it is assumed I will launch Doug in the directory I unpacked it. For now, that is okay, I can launch it here. |

| My Platform | || | setenv VR_HOST_CPU "Linux_FC3" setenv DOUG_HOST_CPU "Linux_FC3" | | This is my platform. And I'm itching for "Linux_64bit" and "MacOSX". |

| Doug Communications | || | setenv MC_TAG cev_comm setenv MC_PORT 12349 setenv MC_GROUP 225.0.0.48 setenv TCP_PORT 7010 setenv UDS_NODE /tmp/cev_comm_${USER} | | I am guessing MC stands for Multicast. This MC business must be because Doug has some way to communicate with clients which dynamically attach. I do not know why there'd be a static IP at 7010. |

| Doug Configuration File (and related) | || | setenv DOUG_CONFIG_FILE ${DOUG_HOME}/cev.cfg setenv USERDATA ${DOUG_HOME}/userdata setenv MISSION CEV setenv BASE_STATE ${DOUG_HOME}/states/BASE_${MISSION} | | As a newbie, I hear that maybe I should not touch the DOUG_CONFIG_FILE with a ten-foot pole. I will not even open cev.cfg yet. I do know what CEV stands for. It stands for Crew Exploration Vehicle.

It looks like Doug is configured out-of-the-box to launch to the moon.

USERDATA looks promising. I bet I am supposed to put my stuff in there. |

| DSP | || | setenv DSP_HOME ${DOUG_HOME} setenv DSP_CONFIG_FILE ${DOUG_CONFIG_FILE} setenv DSP_TARGET_PATH ${DSP_HOME}/targets setenv DSP_OPTION_PATH ${DSP_HOME}/options setenv DSP_PLUGIN_PATH ${DSP_HOME}/plugin_${VR_HOST_CPU} setenv RECONFIG_PATH ${DSP_HOME}/reconfigs setenv DSP_SESSION_TYPE undefined setenv INSTALL_DIR ${DSP_HOME}/bin_$VR_HOST_CPU | | DSP stands for Display Software Package. My understanding it is the core of Doug. Actually, I've heard Doug is a wrapper of sorts around DSP. I see in this case that the DSP_CONFIG_FILE is equal to DOUG_CONFIG_FILE. |

| Paths | || | setenv DSP_TARGET_PATH ${DSP_HOME}/targets setenv DSP_OPTION_PATH ${DSP_HOME}/options setenv DSP_PLUGIN_PATH ${DSP_HOME}/plugin_${VR_HOST_CPU} setenv FLIGHT_MODEL_PATH ${DOUG_HOME}/models/OpenFlight/ksc setenv RECONFIG_PATH ${DSP_HOME}/reconfigs setenv RECONFIG_FILE ${RECONFIG_PATH}/input.ARD setenv BINARY_MODEL_PATH ./:./models:./tiles setenv TEXTURE_MAP_PATH .:./bumpmaps:./textures | | I suppose these paths tell Doug where to find stuff. Some of this is obviously model specific and not Doug-core related. I also guess that the BINARY_MODEL_PATH and TEXTURE_MAP_PATH are relative to something else. |

| Shared Object Location | || | setenv LD_LIBRARY_PATH ${DSP_HOME}/lib_${VR_HOST_CPU} setenv LD_LIBRARYN32_PATH ${DSP_HOME}/lib_${VR_HOST_CPU} | | Doug is designed to dynamically link in .so libraries. The LD environment variables are system variables which tell the loader where the shared object libraries are. |

| Cache & Width | || | setenv DEV_MEM_ADDR_CACHE 0x76000000 setenv DEV_MEM_NAME_CACHE /tmp/doug_CACHE setenv DEV_MEM_SIZE_CACHE 30000000 setenv WIDTH 4 | | This looks like VOODOO settings. Cache's are always complex. They imply optimization. Optimization means the system can't handle simple brute force… so you gotta get smart… and when you get smart… you get complicated… And then upkeep is tough… and you need more money.

Width has nothing to do with anything. IMHO, environment variables named "WIDTH" belong on the ash heap. |

| __GL | || | setenv __GL_FSAA_MODE 4 setenv __GL_LOG_MAX_ANISO 0 setenv __GL_SYNC_TO_VBLANK 1 | | Settings for internal openGL stuff. |

« | NewbieIndex | »