These settings specify the search paths used by C4DtoA to find textures, procedurals (e.g. ASS files) and plugins (e.g. third-party shaders).

Texture Search Path

 Here you can set folders where Arnold will look for textures. Folders have to be separated with a semicolon (;) character. C4D string tokens (e.g. $prj) can be used in the search path.

Procedural Search Path

 C4DtoA will search for files referenced by procedurals (e.g. ASS, obj, etc.) in the folders defined by the Procedural Search Path. For example, if a file called 'forest.ass' is saved in a folder in C:\temp\ass you can define this folder as the search path and give a relative file name in an Arnold Procedural:

Folders have to be separated with a semicolon (;) character. C4D string tokens (e.g. $prj) can be used in the search path.

Plugin Search Path

Here you can set folders where Arnold will look for plugins (e.g. shader libraries, custom procedural or volume binaries). These plugin binaries are .dll files on Windows, .dylib files on OSX and .so files on Linux. Folders have to be separated with a semicolon (;) character. C4D string tokens (e.g. $prj) can be used in the search path.

$C4DTOA_INSTALL_FOLDER/shaders and $C4DTOA_INSTALL_FOLDER/procedurals folders are automatically added to the Plugin Search Path where $C4DTOA_INSTALL_FOLDER is the folder where the plugin is installed.

Search In Subfolders

With this option enabled, textures and procedurals can be located not just in the specified folders, but in any subfolders.

Be careful using this flag because a folder with hundreds or thousands of subfolders can slow down time to first pixel, specially when using a network drive.

OSL Include Path