Table of Contents
A release archive contains everything you need to run Redshift for Houdini and Solaris, including the Redshift libraries, the plugin binaries, the menu shelf, the HDAs, etc. Redshift for Houdini supports the latest production build for the 4 most recent major Houdini versions (18.0, 18.5, 19.0, 19.5, and 20.0) as well as the three most recent production builds of the most recent major Houdini version (19.5). Both the Qt5 (regular) and Qt4 flavors of Houdini are supported. In general you need will need to match the versions of Houdini and the Redshift plugin target Houdini version, however if there are no changes in the Houdini HDK between the Redshift plugin's target Houdini version and your preferred Houdini version, you may be able to run Redshift.
Redshift version 3.6 supports the following Houdini versions
Redshift 3.5 - 2.5
Redshift version 3.5 supports the following Houdini versions
Redshift version 3.0 supports the following Houdini versions
Redshift version 2.6 supports the following Houdini versions
Redshift version 2.5 supports the following Houdini versions:
In this forum topic, there are additional custom builds of the Houdini/Solaris plugins released before they are available inside the main Redshift release installers to support recent Houdini production builds or to include quick fixes: https://www.redshift3d.com/forums/viewthread/32053/
Click here for Windows instructions
Before you can use Redshift in Houdini, you have to tell Houdini where the Redshift plugins are located on your system. The location of the Houdini and Solaris plugins must be established in one of two ways, editing a houdini.env file or creating a Houdini .json package file. This must be done for each version of Houdini you are using.
After installation, Redshift and the Houdini plugin will be installed in the C:\ProgramData\Redshift folder along with your log files, license file (if using a node-locked license), and the Redshift preferences.
The plugin files are located in the main Redshift installation folder:
Each user’s home Houdini directory contains a
houdini.env file you can use to specify environment variables. The
houdini.env file on Windows is located at
C:\Users\<username>\Documents\houdiniX.X\houdini.env (for example: C:\Users\<username>\Documents\houdini20.0\houdini.env)
It is also possible to set this as a system environment variables so not every user needs to maintain their own houdini.env file.
Edit your houdini.env file to include the following lines (Note the direction of the slashes!):
HOUDINI_DSO_ERROR = 2
PATH = "C:/ProgramData/Redshift/bin;$PATH"
HOUDINI_PATH = "C:/ProgramData/Redshift/Plugins/Houdini/20.0.506;&"
PXR_PLUGINPATH_NAME="C:/ProgramData/Redshift/Plugins/Solaris/20.0.506;&"
OCIO Support & Warnings
If you want OCIO support in Solaris, Mplay, or to avoid OCIO warnings in Houdini 20, you should force Houdini to use Redshift's default OCIO config by adding the following line to your Houdini .env configuration:
OCIO = "C:\ProgramData\redshift\Data\OCIO\config.ocio"
Note: This line should be added to the .env config even if you configure Redshift using a Houdini package
If you switch to the Redshift OCIO config and load a scene you already started with the Houdini OCIO config you may need to update the camera parameters so it recognizes the OCIO change. This can be accomplished by selecting the cameras in your scene and pressing the "CamParms" button highlighted in the image below. Or you can automatically update all cameras in the scene by using the "Redshift_cameraSpareParameters" command in the Houdini Textport.
|
A Houdini package is a .json file that can be created and used to configure Redshift for Houdini instead of editing a Houdini .env file. It is generally easier to manage and maintain since they can be separated from other plugin configurations unlike in a .env file where multiple plugins share the same file. For more information, please see the Houdini Packages help page.
Create a Houdini package for Redshift that contains the following:
{
"env":[
{"RS_PLUGIN_VERSION" : "${HOUDINI_VERSION}"},
{"REDSHIFT_COREDATAPATH": "C:/ProgramData/Redshift"},
{"HOUDINI_PATH": "${REDSHIFT_COREDATAPATH}/Plugins/Houdini/${HOUDINI_VERSION}"},
{"PATH": "C:/ProgramData/Redshift/bin"},
{"PXR_PLUGINPATH_NAME" : "${REDSHIFT_COREDATAPATH}/Plugins/Solaris/${RS_PLUGIN_VERSION}"}
]
}
Click here for Linux instructions
Before you can use Redshift in Houdini, you have to tell Houdini where the Redshift plugins are located on your system. The location of the Houdini and Solaris plugins must be established in one of two ways, editing a houdini.env file or creating a Houdini .json package file. This must be done for each version of Houdini you are using.
After installation, Redshift and the Houdini plugin will be installed in the /usr/redshift default folder along with your log files, license file (if using a node-locked license), and the Redshift preferences..
The plugin files are located in the main Redshift installation folder:
Each user’s home Houdini directory can contain a
houdini.env file you can use to specify environment variables. The houdini.env file on Linux is located at ~/houdiniX.X/houdini.env (for example: ~/houdini20.0/houdini.env)
It is also possible to set this as a system environment variables so not every user needs to maintain their own houdini.env file.
Edit your houdini.env file to include the following lines:
HOUDINI_DSO_ERROR = 2
PATH = "/usr/redshift/bin:$PATH"
HOUDINI_PATH = "/usr/redshift/redshift4houdini/20.0.506;&"
PXR_PLUGINPATH_NAME="/usr/redshift/redshift4solaris/20.0.506;&"
OCIO Support & Warnings
If you want OCIO support in Solaris, Mplay, or to avoid OCIO warnings in Houdini 20, you should force Houdini to use Redshift's default OCIO config by adding the following line to your Houdini .env configuration:
OCIO = "/usr/redshift/data/OCIO/config.ocio"
Note: This line should be added to the .env config even if you configure Redshift using a Houdini package
If you switch to the Redshift OCIO config and load a scene you already started with the Houdini OCIO config you may need to update the camera parameters so it recognizes the OCIO change. This can be accomplished by selecting the cameras in your scene and pressing the "CamParms" button highlighted in the image below. Or you can automatically update all cameras in the scene by using the "Redshift_cameraSpareParameters" command in the Houdini Textport.
|
|
A Houdini package is a .json file that can be created and used to configure Redshift for Houdini instead of editing a Houdini .env file. It is generally easier to manage and maintain since they can be separated from other plugin configurations unlike in a .env file where multiple plugins share the same file. For more information, please see the Houdini Packages help page.
Create a Houdini package for Redshift that contains the following:
{
"env":[
{"RS_PLUGIN_VERSION" : "${HOUDINI_VERSION}"},
{"REDSHIFT_COREDATAPATH": "/usr/redshift"},
{"HOUDINI_PATH": "${REDSHIFT_COREDATAPATH}/redshift4houdini/${RS_PLUGIN_VERSION}"},
{"PATH": "${REDSHIFT_COREDATAPATH}/bin"},
{"PXR_PLUGINPATH_NAME" : "${REDSHIFT_COREDATAPATH}/redshift4solaris/${RS_PLUGIN_VERSION}"}
]
}
Click here for macOS instructions
Before you can use Redshift in Houdini, you have to tell Houdini where the Redshift plugins are located on your system. The location of the Houdini and Solaris plugins must be established in one of two ways, editing a houdini.env file or creating a Houdini .json package file. This must be done for each version of Houdini you are using.
After installation, Redshift and the Houdini plugin will be installed in the /Applications/redshift default folder along with your log files, license file (if using a node-locked license), and the Redshift preferences..
The plugin location changes depending on the CPU type of your Mac.
For Mac's with an Apple Silicon CPU, the compatible Redshift plugin is found in a subfolder with the "_arm64" suffix after the Houdini version (example: redshift4houdini/20.0.506_arm64)
For Mac's with an Intel CPU, the compatible Redshift plugin is found in a subfolder that only includes the Houdini version (example: redshift4houdini/20.0.506)
The configuration examples in this section can be modified for your hardware by including or omitting the arm64 suffix as needed.
The plugin files are located in the main Redshift installation folder:
Each user’s home Houdini directory contains a
houdini.env file you can use to specify environment variables. The houdini.env file on macOS is located at ~/Library/Preferences/houdini/XX.X/houdini.env (for example: ~/Library/Preferences/houdini/20.0/houdini.env)
It is also possible to set this as a system environment variables so not every user needs to maintain their own houdini.env file.
Edit your houdini.env file to include the following lines:
HOUDINI_DSO_ERROR = 2
PATH= "/Applications/redshift/bin;$PATH"
HOUDINI_PATH = "/Applications/redshift/redshift4houdini/20.0.506_arm64;&"
PXR_PLUGINPATH_NAME = "/Applications/redshift/redshift4solaris/20.0.506_arm64;&"
OCIO Support & Warnings
If you want OCIO support in Solaris, Mplay, or to avoid OCIO warnings in Houdini 20, you should force Houdini to use Redshift's default OCIO config by adding the following line to your Houdini .env configuration:
OCIO = "/Applications/redshift/Data/OCIO/config.ocio"
Note: This line should be added to the .env config even if you configure Redshift using a Houdini package
If you switch to the Redshift OCIO config and load a scene you already started with the Houdini OCIO config you may need to update the camera parameters so it recognizes the OCIO change. This can be accomplished by selecting the cameras in your scene and pressing the "CamParms" button highlighted in the image below. Or you can automatically update all cameras in the scene by using the "Redshift_cameraSpareParameters" command in the Houdini Textport.
|
|
A Houdini package is a .json file that can be created and used to configure Redshift for Houdini instead of editing a Houdini .env file. It is generally easier to manage and maintain since they can be separated from other plugin configurations unlike in a .env file where multiple plugins share the same file. For more information, please see the Houdini Packages help page.
Create a Houdini package for Redshift that contains the following:
{
"env":[
{"RS_PLUGIN_VERSION" : "${HOUDINI_VERSION}_arm64"},
{"REDSHIFT_COREDATAPATH": "/Applications/redshift"},
{"HOUDINI_PATH": "${REDSHIFT_COREDATAPATH}/redshift4houdini/${RS_PLUGIN_VERSION}"},
{"PATH": "${REDSHIFT_COREDATAPATH}/bin"},
{"PXR_PLUGINPATH_NAME" : "${REDSHIFT_COREDATAPATH}/redshift4solaris/${RS_PLUGIN_VERSION}"}
]
}