Optimizing Houdini Redshift3d
Summary: decrease render times and costs when rendering from Houdini with Redshift using pre-converting textures.
The following topics are covered:
Pre-Convert Textures - References for converting textures locally.
Upload Pre-Converted Textures - Steps to upload converted textures.
Troubleshooting - How to enable debug log verbosity.
Pre-Convert Textures: Using the redshiftTextureProcessor tool to convert textures locally.
When a job is submitted to GridMarkets, textures are automatically converted to .rsbintex files. Depending on the quantity and size of the textures, the conversion process can cause a substantial increase to render times. The conversion step can be skipped, and render times reduced, by pre-converting your textures and uploading them to render.
When converting textures locally, be aware that the proper conversion options need to be set in order for the texture to match what the automatic conversion process would output from within Houdini.
For example, an .EXR texture used in an environment light might need to have -isphere and -l set as conversion options to render properly and not trigger an auto-conversion at render time:
"-isphere" is needed if it is a spherical projection map,
"-l" is needed to keep the image in linear gamma.
An example command using the redshiftTextureProcessor.exe tool and run using the Houdini Command Line Tools would be the following:
redshiftTextureProcessor.exe C:\Users\Steve\Desktop\rs_texture_test\hdr\bonifacio_aragon_stairs.exr -isphere -l
If you are unsure about which command-line options to use, check the Redshift Logs for conversion option recommendations. The image below shows an example of the conversion option recommendations found in a Redshift log.
If the scene is correctly referencing converted textures, it will not display any conversion warnings in the debug logs, as in the example below.
Upload Pre-Converted Textures: Follow these steps to upload .rsbintex files.
Once the textures have been converted, they will need to be manually added to upload via the pre-flight. This is how to do it.
1) Select the directory containing the converted textures and hit “add additional file”
2) Select all of the .rsbintex files and hit accept.
3) The .rsbintex files will now sit next to the original files when uploaded.
Troubleshooting: How to change Redshift log verbosity.
To check if the converted textures are being used when rendering on GridMarkets, set the log verbosity to "debug" by inputting the following command in the Pre-Render script parameter in the Redshift ROP.
Redshift_setLogLevel -L 5
The number at the end will determine what log level to output, where:
0 - Off
1 - Error
2 - Warning
3 - Info
4 - Detailed
5 - Debug
This command will need to be added for each job submission in order to view the debug messages.
The debug messages should now be displayed in the logs found in the render manager.
Questions? Contact us at