Using the Presets pop-up you can apply any of your presets, save your current settings as a preset or delete existing presets. exrTrader has its own system to manage presets. The main reason for developing a custom system was to differentiate between user, global and project (content directory) specific settings.
user presets are stored in the same directory where your LightWave3D configuration files are stored, in a subdirectory called “SimplePresets”.
global presets are stored in a directory that is accessible to all users on the current machine (and can be mirrored on a server).
On Windows the location is:
On MacOS it is
Content presets are stored in the current content directory.
exrTrader supports the concept of default presets. If you name a preset “default” then it will be loaded automatically if exrTrader is added to a scene.
exrTrader searches for default presets in the user, global and content presets in that order. This means that a default content preset overrides a global default which in turn has precedence over a user preset.
This option allows you to save the current exrTrader settings to a preset. Choose any of the three types and enter a name for the preset. You can also use the small pop-up to select any of the currently available preset names.
This allows you to select and of the available presets and delete them from the hard drive.
This allows you to load previously saved settings for exrTrader from a file.
This allows you to save the current exrTrader settings to a file.
It is possible to define user directories to store the presets in. This is done by placing a text file called “SimplePresetPaths.cfg” either into:
The files are read in that order, and preset paths defined in an earlier configuration file can be overwritten. The text file should be formatted as such
# this is just a comment, anything that starts with a # is ignored # first the name of the path as displayed to the user (without spaces) # followed by the path network \\db-w\lightwave\presets local_temp c:\my_temp_presets
The path name is not case sensitive, it will be capitalized automatically. It may not contain spaces though.
You can also overwrite the existing default paths by using user, content or global as path names.