When a VR Juggler application is initialized, it creates an internal database of configuration information. This database will contain information about the kind of IO devices available, the display windows VR Juggler should open, and lots of other stuff.
Typically, this database will be filled up by reading one or more configuration files. With many VR Juggler applications, the names of config files to load are given as command-line arguments when the program is run. For example:
% cubes ~/.vjconfig/simstandalone.config
runs the cubesdemo program and tells it to load a configuration file called simstandalone.config, which provides a basic simulator-mode configuration for running applications.
Configuration files can be stored in serveral places:
The VR Juggler distribution contains a number of sample files in $VJ_BASE_DIR/share/Data/configFiles/. These include a variety of configuration files for simulator-mode use, as well as a number of files demonstrating how VR Juggler can be configured for various kinds of VR hardware.
Juggler expects you to have a directory called .vjconfig in your home directory. This is a good place to put any config files that you've chosen to modify. For example, if you've changed one of the simulator config files because you didn't like the keyboard shortcuts it was using, you should put it in ~/.vjconfig.
Your system administrators may have also created a repository of VR Juggler config files set up to work with your local systems and hardware. For example, VRAC keeps local configurations in the directory /home/vr/vjconfig.