The Arnold for Katana plugin comes with Arnold core bundled but without the SDK. Setting it up generally requires pointing to your license server(s), setting KATANA_RESOURCES, and launching Katana.

Installing KtoA

The download package comes in a self-extracting installer. Downloads of KtoA can be obtained here.

Linux

Change the downloaded installer to be executable, for example, if you had downloaded KtoA version 3.4 for Katana version 3.6 in a terminal:

chmod a+x KtoA-3.4.0.0-kat3.6-linux.run

Then run the installer in a graphical environment to get a walk-through of the installation.  You should have installed your desired Katana version previously.

./KtoA-3.4.0.0-kat3.6-linux.run

Windows

Run the downloaded installer which will pop up a window to walk you through the installation process.  You should have installed your desired Katana version previously.

Running KtoA

KtoA has a bundled script for launching KtoA with your desired version of Katana.  It is recommended to customize that script (or a copy of it) for your environment, and use it or a shortcut to it to launch KtoA.  See the files launchKtoA.sh (Linux) and launchKtoA.bat (Windows) for a typical launch script.

KtoA comes bundled with Arnold core and is tuned to work with the version it is bundled with.  It also has additional plugins, such as common shaders, volume plugins (OpenVDB volumes), kick, the Arnold Python API, and so on.  Generally to launch Katana with KtoA you just need to expand the KtoA tarball and set the following environment variables, customized to your environment (the PATH and license variables are not required):

export foundy_LICENSE=4101@localhost
export ADSKFLEX_LICENSE_FILE=5053@localhost
export solidangle_LICENSE=5053@localhost
export DEFAULT_RENDERER=arnold
export "KATANA_TAGLINE=With KtoA and Arnold"
export KTOA_ROOT=/path/to/KtoA
export PATH=/path/to/Katana:${KTOA_ROOT}/bin:$PATH
# NOTE: this is the only absolutely required variable
export KATANA_RESOURCES=${KTOA_ROOT}

Each KtoA version comes pre-qualified for particular Arnold core and Katana versions and comes bundled with a particular Arnold core version. Please see the release notes for each KtoA version for compatibility.

Setting Environment Variables

Note that on Windows, KtoA comes with an example script to launch Katana with KtoA: launchScript.bat.  You can readily customize that script rather than set your own environment variables.

On Linux, after installing Katana and downloading KtoA, the following environment variables ought to be set, and an example of each is given:

On Linux, if you are using a bash shell, you should consider creating a script to set the main environment variables and launch Katana for you.

Configuring USD Plugins

Katana to Arnold ships with multiple USD plugins, a Render Delegate, a Node Registry Plugin, a custom build of Foundry's KatanaUsdPlugins, and plugins for UsdIn. These plugins can be activated by either using the launch scripts or manually setting the environment variables listed below.

Render Delegate and Node Registry plugin

Katana to Arnold includes two components from Arnold-USD to allow using Arnold directly in the Hydra Viewport.

On Linux:

export "FNPXR_PLUGINPATH=${KTOA_ROOT}/USD/Viewport:${FNPXR_PLUGINPATH}"

On Windows:

set "FNPXR_PLUGINPATH=%KTOA_HOME%\USD\Viewport;%FNPXR_PLUGINPATH%"

 

 

 

More Environment Variables

There are a few more environment variables of interest:

Licensing Environment Variables 

Although not specific to Katana, you may want to set the following environment variables to remove the Arnold watermark from your rendered images: