There is currently very little documentation for this addon – unfortunately you’re on your own! If you’d like to help write something up, please let me know and I can help you.
Paths
3Delight/blender uses its own variable parsing for many user-set paths, which isn’t available in the standard blender. This functionality was added to make up for blender lacking easy means of using environment variables or expressions in string fields. These variables will be checked in paths in the following order:
- Environment Variables
If these are already set outside of Blender, these will be preserved and not overridden by Blender. Otherwise if the variables are not set, they will be initialised by what’s in the Render Properties → Environment Variables panel, - Special 3delight/blender data variables
- {blend} – blend file name (without file extension)
- {scene} – scene name
- {object} – object name
These are only accessible where relevant, when there is an obvious context. Eg. {object} is available in the shadow map path (translating to the name of the light), but not in the RIB export path, where there is no specific object that can be implied.
- Frame numbers
3delight/blender will convert sequences of hashes to the current frame number where possible. Eg. /path/file_####.exr -> /path/file_0001.exr - Blender relative paths
Eg. //myfile.exr
3Delight/blender uses some environment variables by default (eg. $OUT, $SHD, $PTC), which can be easily set in the Render Properties → Environment Variables panel. If these variables are already set in the environment they will be inherited, and not overridden by blender.
Shader Parameter Annotations
gadgettype
checkbox –> Boolean property
optionmenu –> Enum property
floatslider –> Float property with slider
inputfile –> String property, with file selector
Using Primitive Variables
example: http://www.pasteall.org/pic/17679