Renderman environment variables1/8/2024 ![]() Shaders are discoverable if they are found in a search path and (for non-OSL shaders) have an associated Args file. Shader Discoveryĭuring startup RenderMan for Katana will automatically load all "discoverable" shaders. You can direct the render log output to another location if necessary using the following environment variable: RFK_REDIRECT_OUTPUT You can also use RFK_OVERRIDE_RENDER_ACTION When set, this overrides the default processing for render outputs to always render directly to the renderLocation specified in the RenderOutputDefine node without any copying or processing from Katana. These environment variables replace rather than append to the default paths, so you will need to include the default paths as well. If additional search paths are needed then you will need to set up the RMAN_SHADERPATH and/or RMAN_RIXPLUGINPATH environment variables to include your specific paths. Note that this variable is only needed when rendering with the Vray command line.Default shader search paths for RenderMan match the default paths in the rendermn.ini file. It is particularly important to keep the default value of this variable and only append the Golaem value, or V-Ray rendering will not work at all. See the tutorial for full workflow description. Note that this variable is only needed when rendering with the 3ds Max + VRay plugin. It is particularly important to keep the default value of this variable and only append the Golaem value, or V-Ray rendering will not work at all.Ĭontains the path to the directory where the Golaem shaders for V-Ray are located (e.g. the shaders /vray/XX folder in Golaem installation directory when using standard installation).Ĭontains the path to the directory where the Golaem plugin for V-Ray is located (e.g. the procedurals /vray/XX folder in Golaem installation directory when using standard installation). Should you need to add any environment variables, use the Advanced tab. Notice that the name of the variable itself is depending on the Maya version you are using. section contains several paths required for rendering Katana with Renderman. See Advanced Installation.Ĭontains the path to the directory where the Golaem plugin for V-Ray (from Vray Next) is located (e.g. the procedurals/vray/XX folder in Golaem installation directory when using standard installation). When using advanced deployment, it may be needed to set this variable for Maya to find and load the Golaem module. Set this variable to 1 if you want to skip the fetch of a Golaem PLE license on a computer. Set this variable to 1 if you want to skip the fetch of a Golaem license on a computer (such as a render node for example). If not found, it will fall back to a PLE License fetch. Set this variable to 1 if you want to force a computer to use a Lite license instead of a FULL license (typically on a lighting artist computer who needs only to visualize/edit simulation cache, or on a computer used only to batch export the simulation). Set this variable to 1 if you want to force a computer to only use a FULL license and not a Lite License else if it fails. The command glmBatchCrowdSimulationExporter set this variable temporary when called. The default value is 0 which prevents any computer to use a license while used in batch (so that Maya does not trigger simulation during rendering). Set this variable to 1 if you want to enable a computer to perform batch simulation export. These variables are not needed if using the Golaem plugin for rendering only (see license setup) or when using the auto-generated evaluation license.Ĭontains the full path to the Golaem license file to use ( (or license server information using the of these variables can be used (only one is needed), but it maybe more convenient to use the golaem_LICENSE variable to avoid issues with other software using RLM.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |