Qube Renderfarm: Arnold for Maya (Kick method)


By generating the Arnold format render frames in advance (as opposed to Maya generating it for each frame as they are rendered), we can submit jobs to the Qube farm that don't involve Maya any further.  


A set of ASS (Arnold Scene Source) files are generated under Linux using the Maya plugin.  Then using WranglerView, a job is submitted that points to these files. Qube then distributes and monitors the kick render processes.


  • Arnold is used as the renderer
  • ASS files MUST be generated in Linux so all paths can resolve

File Pathing

All external reference files such as HDR and texture files should use paths relative to the project folder, or an explicit path in Linux format:

RELATIVE:    sourceimages/ibl/myibl.hdr
WINDOWS:  X:\myDocuments\maya\projects\myscene\myibl.hdr

The first one is relative to the project folder and will work in both Windows and Linux, the second will resolve in Linux only, the last will resolve in Windows only and will fail when submitting a job for network rendering.

Some file types, such as VDB files, may only work with full explicit paths, in the case of these they must be in Linux notation. 

Spaces should be avoided in any part of the paths since these can cause issues, even if the render works interactively (i.e. by clicking Render within Maya).

In Maya under Linux use Window -> General -> File Path Editor to identify paths that need fixing ( ) or use our bespoke script to change the file paths en mass, info below.


How to use the script

  • For UG Students - Copy the script from /escape/shares/UG/assets/scripts/qube/
  • For SCMA Students - Copy the script from /escape/shares/SCMA/assets/scripts/qube/
  • Paste script into your personal maya/scripts directory
  • Open Maya
  • Open Script Editor and type in the script below which will load the UI for this tool
  • This will load this UI, where you can input a texture path and replace it with the Linux path

Generate ASS files in Linux

This process is a lot more simple than it might appear, after the first couple of times you will be able to get through it very quickly.


One point to note is that each file generated contains a full snapshot of shaders and geometry for that particular frame and so they can become very large.  Currently they MUST be manually deleted after the render is successfully completed (or if they are no good and need to be regenerated). If they are not, your home directory will end up taking a lot of space and you’ll get warnings from IT about it.  In the future we’ll streamline this process to make things more automated, but for now it is your responsibility to keep on top of things.


  1. Log into the Linux desktop, and launch Maya ( Applications -> Autodesk -> Maya <version> )
  2. Set your Maya project directory (it won’t carry over from Windows)
  3. Use Render Settings window to set up everything as intended, and ensure it works as a local render under Linux - try to choose a frame which has the most elements to test, e.g. animations, alembics or lots of geo/textures on screen
  4. File naming for output must be set to name.#.ext and NOT name_#.ext (dot must be either side of the frame number)
  5. Ensure the correct camera is selected
  6. If anything is not working, resolve any path issues, use relative paths to ensure they can resolve for both Windows and Linux
  7. When using something that does not support relative paths, such as VDB files and UDIM tiles, the full Linux path MUST be used.  ANY REFERENCES TO WINDOWS NAMING SUCH AS X:, U: or S: DRIVES WILL CAUSE RENDER FAILURES OR MISSING ELEMENTS
  8. Make sure any dynamics are cached, otherwise the files can take longer to generate and mail fail entirely
  9. Once ready to go, in Render Settings -> System change the following settings to the values shown. 
    In some cases you may also need to enable the "Expand Procedurals" tick box. On older versions, the Render Device option will not be present

  10. Half Precision (16-bit exr) should be used unless there is a clear provable need for greater bit depth.  If you’re not sure, use Half Precision since it should be plenty for all except the largest z-depth ranges and results in smaller files that are faster to work with in comp
  11. Now using the Render menu set, use Render -> Batch Render (do NOT use Render Sequence, it works but it does not resolve the project folders correctly and the output will not end up where it should be)
  12. The .ass files should end up in <ProjectDirectory>/data with one per frame, per render layer
  13. Maya can now be closed as it is not needed for the rest of the process


Open Qube Wranglerview


  1. In Linux, from the Applications menu, choose Render -> qubeWranglerView


  2. If you cannot see the option shown above, right-click on the desktop, choose Terminal and then paste or type the following and press enter:

  3. Once open, select Submit -> Arnold Kick Render Job…


First Time Setup (once only per user)

You need to configure the job type first. Please see the following document for steps. If you do not have access, log in at and then try again. Do not request access using your personal gmail account as it will not be granted.


Job Submission


With the defaults set, it should be easy enough to submit new jobs by only changing a couple of settings


  1. Open Wranglerview under linux as shown earlier
  2. As before, select Submit -> Arnold Kick Render Job…
  3. Change the job name to something relevant
  4. Set the frame range (e.g. 1-100 )
  5. Click Browse next to Arnold Scene Source and choose one of the .ass files created earlier - these should be in the “data” subfolder of the project directory
  6. Click “Submit” at the bottom right

Once the job is submitted, you can see its progress in either WranglerView or ArtistView but currently you must use WranglerView to submit

It is also a good option to right-click an old job (even if it didn't complete, but you know the reason why), and choose Resubmit.  This opens a new submission, whilst copying all the parameters from the previous one but allowing you to change anything that needs to be amended.




Troubleshooting (if renders fail, do these steps in order)

  • Check Permissions to use the Farm - you should see immediately on attempting to submit an error message that tells if you if you don't have permissions (email
  • Check Qube! Artist View for Error Messages, on both the StdOut Log and StdErr log tabs, look for lines that begin with Error
  • Check paths are correct
  • Make sure that nothing is being read from External Drives
  • Make sure that any other renderers are turned off in Plugins (e.g. if you rendering with Arnold, turn off Redshift)
  • Check whether Renders are working correctly interactively in both Linux and Windows (by interactively we mean if you click Render and see it onscreen)
  • Increase ‘Agenda (Frame) Timeout’ and try again


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request