MtoA defines a lot of batch render flags for Arnold. For example, here’s how to set the Arnold log verbosity and enable file logging:
render -s 2 -e 2 ^
-r arnold ^
-ai:lve 2 ^
-ai:ltf true ^
-ai:lfn C:/Users/blairs/Downloads/render.log ^
First, to use the Arnold batch render flags, you need to use the Maya -r flag to specify that the renderer is arnold (otherwise, you’ll get an “Invalid flag” error).
Then you can use the Arnold batch render flags:
- ai:lve sets the log verbosity level
- ai:ltf enables file logging (Log To File)
- ai:lfn is the log file name. I used forward slashes; I could also have used backslashes and put quotation marks around the log file name.
You can export an ASS file from Maya (with the XGen primitives) and then use an Arnold Procedural to load the ASS file into 3ds Max.
You need to add these two folders to the system environment variable Path:
- C:\Program Files\Autodesk\Maya2018\plug-ins\xgen\bin
- C:\Program Files\Autodesk\Maya2018\bin
For example, you can copy this:
C:\Program Files\Autodesk\Maya2018\plug-ins\xgen\bin;C:\Program Files\Autodesk\Maya2018\bin;
and paste it at the beginning of the current Path:
Restart 3ds Max after you do this.
Then add the MtoA procedurals folder to the Plugin Search Path:
The Arnold volume node uses the texture search path, so you don’t have to use an absolute path in the volume filename.
So if you need to set up a Maya scene so that the OpenVDB volumes work on any platform, you could put an environment variable in the Texture Search Path
Just note that support for volume filenames is still a little … rough. You can’t enter an absolute path in the aiVolume Filename box, then enter a texture search path, and expect MtoA to automatically export a relative path. That still needs to be implemented.
For now, here’s what to do:
- When you first create the volume, load the vdb file and leave the full absolute path in the aiVolume Filename box.
- Select the grids and set the other volume parameters.
- Then set the texture search path and strip off the path from the volume file name (leaving just the file name).
- Now the environment variable will control where Arnold looks for the vdb file.
The Arnold volume node also support environment variables, so you could do this:
But again, once you put the environment variable into the Filename, the path won’t be resolved inside Maya (but it will work when you render).
If you see something like this:
[Arnold]: MAXtoA_Shaders.dll was compiled against non-compatible Arnold 22.214.171.124
it usually means you have an older Arnold trying to load something compiled with a newer Arnold. There’s two common reasons for this happening:
- The system PATH includes the location of the older Arnold, so the older Arnold is loaded instead of the Arnold version included with the plugin.
- The plugin install is messed up, and has the wrong Arnold version in it.
To jitter color with user data, you need to connect an aiUserDataInt to the data input parameter, like this:
The user data is an mtoa_constant attribute on the shape. For example, if add an extra attribute named mtoa_constant_jitterID to some shapes, then you can use aiUserDataInt to read the jitterID.
jitterID is set on the shape
Jitter by user data (with a little jitter per face too)
aiUserDataInt reads the jitterID
If you want to use the shapes as standins, and be able to set the jitterID in the scene, then export the shapes without the mtoa_constant_jitterID attribute. In the scene, you’ll be able to add mtoa_constant_jitterID to the aiStandin node. The aiUserDataInt node in the ASS file will use that jitterID.
You can get individual log files for each frame:
- In the Arnold Render Settings, go to the Diagnostics tab.
- In the Verbosity Level list, click Warnings + Info.
- Click the File check box.
- Click the folder icon and choose a folder for the Arnold log files.
Or you can check the MayaRender log, which will be one log file, with the log messages for every frame.
On OSX, open the Console and look for ~/Library/Logs/Maya/mayaRender.log
New in Arnold 5.0.2! You can press T to get a cputime heat map. From the Arnold release notes:
- Added cputime heatmap view to
kick: When using
kick you can now toggle between viewing kicks default output and a cputime heatmap with the
T key. The mapping of the heat map can be scaled with the
To get the cputime heat map, you have to run kick interactive (eg with the -ipr flag):
kick -ipr example.ass