Caches and Proxies


Workflow and restrictions

When you used files like texture images or caches, Maya do not create an internal copy inside the scene file but adress their paths. For this reason, when you changed the assets location, Maya will not be able to retrieve them without repathing them.

In most of the case, RANCHecker V5 will gathered external files and our housemade rendering batch will modify the paths to fit those of the RANCH rendering nodes.

However, due to softwares restictions some caches paths are not automatically changed or collected by RANCHecker.
One of the solutions to solve this issue is to work on the RANCH path, namely:


Or copy the project inside and change all the paths to fit the new location corresponding to the farm.


Alembics (.abc)

RANCH path: C:/Maya/Currentjob/cache/alembic/

Maya Alembic node do not let us change its path during the rendering process. Actually, Maya partially block this functionnality.

Warning, alembics shows relatives paths if you “Set Project” but in reality have absolute path
It is strongly recommended to check the VUA archive to be sure that all your caches are there.

For XGen alembics, please follow the plug-in documentation.

Method 1 (Arnold)

This method is fully automated et do not required modifications from you.
It is strongly recommended for Arnold users(except for cameras alembics).

  • Create a StandIn / aiStandIn
  • Adress your ABC files
  • RANCHeck and upload.

Method 2a (Alembic Node + Currenjob)

  • Copy your project in Currentjob and put your alembics in the RANCH path.
  • Modify the alembics paths in the scene.
  • RANCHeck and upload

Method 2b (Referenced + Currentjob)

This method is the most recommended for cameras alembics and others renderers.

  • Copy your project in Currentjob and put your alembics in the RANCH path.
  • Import your alembic as a reference
  • RANCHeck et upload

Method 3 (Alembic Node)

Also suitable for referenced alembics.

In your scene:

  • Modify the cache path by the RANCH path without reimporting it or changing its location.
    The path MUST NOT BE relative.
  • Create your archive with RANCHecker (Do not click on “Submit”).

In the archive:

  • Open the VUA (with 7zip for instance, right-click > open with: 7zip manager)
  • Create the folder “caches” and subfolder “alembic” if they doesn’t exist
  • Drag&Drop your alembics in the archive.

Before closing your Maya scene, we recommend to restore the path of your cache to prevent your alembic not longer being displayed.

sous-titre disponible en français et en anglais

Bifrost (.bif)

RANCH path: C:/Maya/Currentjob/cache/bifrost/yourPath

BIF are partially supported.
Only BifrostLiquidContainer caches will be collected

Please contact us before rendering your .bif cache.

The .ass.gz format is not supported.

Geometry caches (.xml + .mcx/.mc)

RANCH path: C:/Maya/Currentjob/cache/nCache/

Geometry caches are automatically supported on the RANCH with MCX format for single file or sequence files.

For the moment MCC format (.mc) required manual steps:

  • Copy the XML and MC files in the RANCH path
  • Replace the .xml in the scene
  • Create the VUA with RANCHecker (Do not click on “Submit”).
  • Open the VUA
  • Drag & Drop the MC file in the “cache/nCache” folder

Jiggle caches (.mcj)

Jiggle are not supported on the RANCH.

Jiggle caches are computed just before the rendering. However, as the animation frames are dispatched on multiple render nodes, the cache will be created in each node (or for each frame if you used the optional parameter for custom frame range) and will not match together.

It is a mandatory to create a cache for your simulations (ncloth, nfur,…) in your own computer to avoid continuity problem between images.


Arnold Scene Source (.ass)

RANCH path: C:/Maya/Currentjob/scenes/

ASS files are automatically supported for single files.

For ASS sequence, you have to manually insert the files in the “scenes” folder of the VUA.

Redshift Proxy (.rs)

RANCH path: C:/Maya/Currentjob/proxy/

RS files are automatically supported for single files.

Warning, only the From Scene option of the Material Mode will works (assigned to placeholder or name matching with prefix). Actually, RS files are encrypted, so we cannot access the material path of the From Proxy option.

Vray Mesh (.vrmesh)

RANCH path:

VRMESH are not supported yet.

Nevertheless you can try the farm path.

Renderman (.rib)

RANCH path: C:/Maya/Currentjob

RIB files are supported with the farm path.