# Creating Custom Install Directories

***

If regular installation is not flexible enough to meet your administrative criteria, use the methods below for custom installations.

## License

Nuke might change the default application directory during startup (if using .nk files directly). We have introduced environment variables to control this:

**OPTICAL\_FLARES\_LICENSE\_PATH**\
if set, Optical Flares will look up license in this directory\
\
**OPTICAL\_FLARES\_PATH**\
If above variable is not set, Optical Flares will try to load the license from this directory

The license file is named OpticalFlaresLicense.lic. You can extend the license file with the\
computer name in case you are managing multiple licenses in one location.

OpticalFlaresLicense\_\[computername].lic 

## Textures and Presets

Nuke might also change the default application directory during startup (if using .nk files directly) so this is not reliable. We have introduced environment variables to control this:

**OPTICAL\_FLARES\_PRESET\_PATH**\
if set, Optical Flares will look up data in this directory\
\
**OPTICAL\_FLARES\_PATH**\
If above variable is not set, Optical Flares will look up presets and textures in this directory

You can resolve trouble with white spaces in our path names by creating symbolic links.<br>

Optical Flares writes a preference file with user settings. It will go to the same directory as the presets, unless you specify a separate folder for it:

**OPTICAL\_FLARES\_PREFERENCE\_PATH**