Get Ready for Houdini Render
1. Default submitting protocol
a. The platform will select the version when the hip scene file was saved automatically, or the higher version which is closest to it in two sides.
b. Each machine renders only a single frame in order to get more nodes for a task(file). Since Houdini generates exclusive Houdini textures before the render process, the textures caching process will be long. In this situation a 50-frame task will need 50 nodes to render and generates the textures cache 50 times if each node only renders a single frame in its process; However, it will halve the caching time if each node renders 2 frames in the same time, and the rest of the nodes can be used for other tasks, which is better for the cost and productiveness balance. In other words, it's better to render multi-frame for one node, such as 2 to 5 frames regarding the rendering time. Needing additional instructions.
2. Desktop client does not support Houdini render job.
3. Houdini projects preparing instruction
a. The detail software version of the project, such as Houdini 15.5.657.
b. The detail plugin version of the project, such as htoa.
c. The drive mapping of the project, such as drive Z.
d. The user-defined configuration of the project, such as $JOB.
e. The path mapping such as Linux path.
f. For force plugin loading, such as otls, it's merely needed to new an otl or otls folder with relavant otls plugin, or put the otls's files into the customer's path of Fox Renderfarm account ID.
g. Default Houdini configuration referring to textures or cache is preferred.
Please inform all the above information to our customer service, Project Manager or Technical Director in advance. Thank you.