MRayRenderAction

All of the MI file dependencies of the target image which set the Order per-source sequence parameter will be processed. The frame range rendered will be limited by frame numbers of the target images. The Action invokes a new instance of the Mental Ray renderer for each MI file. This is due to how Mental Ray keeps library information loaded when rendering multiple MIs. Since each MI file may potentially have a different set of library files and includes, a separate invocation of 'ray' is necessary to ensure that each one runs in the correct environment.

Camera Name

Name of the "camera" object in the source MI files used to render the target images.

Framebuffer Type

The data format of the target rendered images.

Keep Temp Files

Should the Action preserve the temporary MI files it generates for rendering.

Render Verbosity

The verbosity of render progress, warning and error messages.

Maya Shaders

Whether to generate "link" and "$include" statements for Mental Ray shaders provided as part of the Maya application.

Include Path

A semicolon seperated list of directories which overrides the path used to resolve "$include" statements in the MI scene file. Toolset environmental variable substitutions are enabled (see evaluate).

Library Path

A semicolon seperated list of directories that mental ray searches for shader libraries containing shader code before the default library paths. Toolset environmental variable substitutions are enabled (see evaluate).

Texture Path

A semicolon seperated list of directories that mental ray searches for texture files. Toolset environmental variable substitutions are enabled (see evaluate).

Extra Opts

Additional command-line arguments.

Contains

Each source sequence which sets this parameter should contain input MI files to render. This parameter specifies the type of MI data the Action should expect the files to contain and controls how the Action processes these files. The allowable types are:

ShaderIncs - Contains "link" and "$include" statements for custom shaders. Typically generated by the MRayShaderInc Action.

Lights - Contains light shaders, objects and instances used to illuminate the geometry being rendered and possibly required by shaders.

Shaders - Contains "material" and "shader" statements required by the geometry to be rendered.

Geometry - Contains "instance" statements for the geometry to be rendered.

InstGroups - Contains "instgroup" statements for instances found in pre-processed geometry MI files and "$include" statements for those files. Typically generated by the MRayInstGroup Action.

Cameras - Contains the camera object and instance used to render the images. May contain additional cameras as well, but they will be ignored.

CamOverride - Contains MI statements which should be used to override settings for the specified render camera as an increment. Typically generated by the MRayCamOverride Action.

Options - Contains an "option" statement specifying render globals.

If the environmental variable MRAY_BINARY is defined, its value will be used as the name of the renderer executable instead of the "ray" (Unix/MacOS) or "ray345.exe" (Windows). On Windows, the renderer name should include the ".exe" extension.

By default, the "python" program is used by this action when running on Windows to process the MI files. An alternative program can be specified by setting PYTHON_BINARY in the Toolset environment to the name of the Python interpertor this Action should use. When naming an alternative Python interpretor under Windows, make sure to include the ".exe" extension in the program name.

Field Summary
`static String`	`aBaseLibraries`
`static String`	`aCameraName`
`static String`	`aCameras`
`static String`	`aCamOverride`
`static String`	`aContains`
`static String`	`aFramebufferType`
`static String`	`aGeometry`
`static String`	`aIncludePath`
`static String`	`aInstGroups`
`static String`	`aKeepTempFiles`
`static String`	`aLibraryPath`
`static String`	`aLights`
`static String`	`aMayaShaders`
`static String`	`aOptions`
`static String`	`aRenderVerbosity`
`static String`	`aShaderIncs`
`static String`	`aShaders`
`static String`	`aTexturePath`

Method Summary
`TreeMap<String,ActionParam>`	`getInitialSourceParams()` Get an initial set of action parameters associated with an upstream node.
`SubProcessHeavy`	`prep(ActionAgenda agenda, File outFile, File errFile)` Construct a `SubProcessHeavy` instance which when executed will fulfill the given action agenda.
`boolean`	`supportsSourceParams()` Does this action support per-source parameters?

us.temerity.pipeline.plugin.MRayRenderAction.v2_2_1 Class MRayRenderAction

aCameraName

aFramebufferType

aKeepTempFiles

aRenderVerbosity

aBaseLibraries

aMayaShaders

aIncludePath

aLibraryPath

aTexturePath

aContains

aShaderIncs

aLights

aShaders

aGeometry

aInstGroups

aCameras

aCamOverride

aOptions

MRayRenderAction

supportsSourceParams

getInitialSourceParams

prep

us.temerity.pipeline.plugin.MRayRenderAction.v2_2_1
Class MRayRenderAction