Arnold makes a splash with Cube
An overhaul to Cube’s render workflow with Arnold places the power back at the director’s feet.
Cube, the Paris based 2D/3D animation visual effects studio, recently adopted Arnold for their photorealistic render workflow. Previously relying on Softimage and Mental Ray they are now switching to Maya, Arnold and Yeti to help speed up their iterative rendering process. In an interview with the head of the realistic projects at Cube, Technical Director Julien Stigler describes the reasons for the change.
What made you look at Arnold for a render solution?
With Mental Ray I was happy to find a solution to each new challenge, but as the level of detail in movies increased it got harder to make this work. In the end I was generally disappointed by the lighting and since the rendering was slow making a change to a director’s request was a nightmare. In Mental Ray, like in VRay, there are many render methods to choose from but none are perfect in a realistic production.
Before we made the switch to Arnold we tested with 3delight and made an uber-shader that took advantage of point clouds, deep shadows, etc. These were some nice ideas to make the preprocess automatic for the user, but in the end none of these provided the simplicity of brute force path tracing for glossy and indirect components. I see now PRMan and 3delight are now switching to raytraced multiple importance sampling shaders.
Now that we have switched to Arnold, I am very happy to give the director the opportunity to have an open discussion about the picture and make changes quickly in the render scene when necessary.
What improvement has Arnold been over your previous renderer?
The two main improvements are the quality of the final picture due to the brute force glossy / indirect and the stability of the renderer on huge scenes, due to the strong optimisation of geometry loading and the simplicity of path tracing.
What was your biggest problem with you previous renderer and how did Arnold resolve them?
In short there is no technical preparation necessary and the brute force internal optimisation does the job.
Can you tell us what process you went through for the interior lights?
At the beginning we tested using backlighting on windows but quickly realised that it produces indirect lighting and thus noise. So in addition to the sun we have simply removed the sky dome and switched to area lights only which are pretty fast in Arnold.
Can you explain the approach you took to render the water?
The water splashes were simulated with Naiad and exported as .ass archives. I was surprised that, even with over 10 million triangles per splash, they loaded instantly and rendered so fast, unlike Renderman blobbies.
How did you come up with the idea for "5m80"?
Nicolas Deveaux came to Cube 10 years ago with the idea of a jumping elephant and wanted to work with us on improving the realism. He is also a very good modeler and anatomy expert and always has strong views for the picture. He has many projects involving animals in human environments and it has slowly become a theme of his work.
Following the jumping elephant project he wanted to work on another jumping animal and the water was an elegant solution for the fall impact. The anatomy of the giraffe did not permit strong intentional jumps, so the idea emerged of using their running speed and the neck of the giraffe as a propulsion force. He wanted to represent the animal in the context of a familiar and human location to create a surreal, poetic and funny contrast between the two universes. He insisted on getting a strong blue bounce of light that seemed natural due to the strong impacts of the sun on water to give a graphic but credible look. He wanted the animals to stay saturated to avoid the sfx look of integration and keep that graphic contrast.