Couldn’t register Arnold renderer in Maya PIT file (error while parsing .pit file)

Posted on December 8, 2019 by xsisupport

For Arnold itself, you can ignore that message. Unless you have an Arnold license.

Couldn't register Arnold renderer in Maya PIT file (error while parsing
.pit file). Please contact support@solidangle.com.

For Maya, that message is a symptom of a problem with your Maya install: the Maya installation is not creating all the required files on your system.

If you finish the install (you can install without MtoA if you want), and then try to start Maya and nothing happens, then the ProductInformation.pit file is missing or corrupt.

The Maya install should create this file:

C:\ProgramData\Autodesk\Adlm\ProductInformation.pit

If there is any problem with that file, Maya (and any other Autodesk software) will not start.
Arnold will still render, but it won’t be able to use any Arnold license.

If that file does exist on your system, delete it.
Then remove all Autodesk software, and install Maya again (without MtoA)

You can install MtoA later (go to arnoldrenderer.com/arnold/download to get the latest MtoA).

If you still have problems with the Maya installation, log on to your Autodesk account to contact the Autodesk support team, or go to the Install and Licensing Autodesk forum at https://forums.autodesk.com/t5/installation-licensing/bd-p/24

The case of Maya and the missing ProductInformation.pit file

Posted on June 18, 2019 by xsisupport

One of the strange thing about supporting Arnold at Autodesk is that you have to be a guru-level licensing expert on Autodesk licensing (not RLM, but Autodesk licensing).

In this case, Maya 2019 would silently fail at startup. Sometimes you’d see the splash screen, but then that would just disappear.

There was nothing in the Adlm.log

No MayaAdlm log was created

The MayaCLM log had only this:

ERROR: checkoutLicense: Failed to authorize license

The clm log did have this:

JsProductLicenseFact.loadSelectedProductInfoKey - Unable to get selected product key due to unknown problem.

TIP All these log files are in the Temp folder.

On Windows, look in %LOCALAPPDATA%\Autodesk\Logs
On OSX, look in $TMPDIR
On Linux, look in /var/tmp

Process Monitor confirmed that the ProductInformation.pit file was missing:

ProductInformation.pit is an all-important file used by the licensing infrastructure. Every Autodesk product must be registered in that pit file.

If ProductInformation.pit is missing, or corrupted, then everything stops working.

[macOS] Rendering xgen procedurals in another app

Posted on February 1, 2019 by xsisupport

Or: how to fix the node “xgen_procedural” is not installed problem.

For example, suppose you want to render XGen hair in CINEMA 4D on macOS.

From MtoA, export your XGen hair to an ass file.
Set DYLD_LIBRARY_PATH before you start your application (for example, open a Terminal, set DYLD_LIBRARY_PATH there, and start CINEMA 4D the command line)
```
export DYLD_LIBRARY_PATH=/Applications/Autodesk/maya2018/plug-ins/xgen/lib:/Applications/Autodesk/maya2018/Maya.app/Contents/MacOS
```
Load the ass file into CINEMA 4D with an Arnold Procedural.
Set the Plugin Search Path to the MtoA procedurals folder

ShadingGroup has no surfaceShader input

Posted on January 29, 2019 by xsisupport

If you see this warning when you render

Warning: [mtoa] [translator polymesh] ShadingGroup exampleSG has no surfaceShader input

it’s because a shadingEngine node either has nothing connected to the surfaceShader port, or (more likely) it has an unknown node plugged into surfaceShader.

For example, if you load a scene that was set up with a different renderer, and that renderer is not loaded, then you’ll get some “ShadingGroup has no surfaceShader input” warnings.

Using triplanar as a bump map

Posted on January 18, 2019 by xsisupport

You can use use color_correct with alpha_is_luminance enabled, like this:

ERROR | [aov] more than one output statement was associated with single layer driver: defaultArnoldDriver@driver_png.RGBA

Posted on November 26, 2018 by xsisupport

This error means that you are trying to render multiple AOVs into a single file, and the file format (PNG in this example) does not support that.

JPEG, PNG, and TIFF cannot have multiple AOVs in a single file. The AOVs have to be rendered in separate files.

If you get this error, check the Common tab. If you don’t see the <RenderPass> token, then you’re going to get the “more than one output statement was associated with single layer driver” error.

For JPEG, PNG, and TIFF, you need the <RenderPass> token:

Normally, MtoA will automatically add the <RenderPass> token for you. But sometimes Merge AOVs gets enabled for EXRs, and then the Image format is changed to another format, like PNG.

So just switch back to EXR and disable Merge AOVs. Then switch back to the other image format.

backdoor Arnold: setting visibility

Posted on November 21, 2018 by xsisupport

If you want to control object visibility with operator, or the Arnold Python API, or by editing an ASS file, you need to understand Arnold’s visibility parameter.

In the UI, the object visibility options look like a bunch of separate parameters:

but in Arnold, all those options are stored in one visibility parameter.

For example, if an object is visible to the camera (primary visibility), and to transmission (both diffuse and specular), then that’s visibility 13.

Why 13? Because 13 = 1 + 4 + 8

camera rays = 1
diffuse transmission rays = 4
specular transmission rays = 8

The Arnold visibility parameter tells Arnold the rays to which the object is visible.

visibility 0 means the object isn’t visible to any rays
visibility 255 means the object is visible to all rays
visibility 253 means the object isn’t visible to shadow rays (so the object does not cast shadows).

Here’s the decimal values for all the different ray types.

To figure out the visibility, just add up the values for the rays you want.

Ray type	Decimal Value
Camera (Primary Visibility)	1
Shadow (Casts Shadows)	2
Diffuse transmission	4
Specular transmission	8
Volume	16
Diffuse reflection	32
Specular reflection	64
SSS (subsurface)	128

Denoisers in a nutshell

Posted on June 14, 2018 by xsisupport

There’s two denoisers. Here’s when to use them:

Use the OptiX Denoiser for fast (GPU-powered), slightly-lower quality denoising of IPR
Use the Arnold Denoiser (aka noice) for high-quality denoising of final frames and animation sequences

For more info, check the docs

The case of the too-low OptiX version

Posted on June 7, 2018 by xsisupport

In this case, when the user tried to render after enabling the OptiX denoiser, they got this error:

ERROR | [gpu] OptiX version 0.30.91 is lower than the minimum required version 5.0.0

This was with MtoA 3.0.1, which means Arnold 5.1.1.0

So, that means there is an incompatible version version of the OptiX library on the system, and it’s being loaded instead of the OptiX that ships with MtoA.

I probably could have just checked the PATH setting, but I used Process Monitor to absolutely sure, and I found this:

The problem is that another renderer added itself to the PATH. That’s a bad thing 😉

The solution? Remove that folder from PATH. Create a batch file or wrapper script to set the required environment when you start Maya to use the other software. Rather like the mtoa module file sets PATH when you start Maya.

NOTE In previous versions of MtoA, this would prevent MtoA from even loading.

kicking ass with debug shading

Posted on June 7, 2018 by xsisupport

You can use kick to render with debug shading. Here’s the flags to use:

-is to ignore the shaders assigned to the shapes
When you ignore shaders, a default utility shader is used to render the scene.
-sm sets the shade mode ( ndoteye lambert flat ambocc plastic metal)
-cm sets the color mode (color ng ns n bary uv u v dpdu dpdv p prims uniformid wire polywire obj edgelength floatgrid reflectline bad_uvs nlights id bumpdiff pixelerror)

Here’s some examples that show how to kick with different types of debug shading (I’ve used the Arnold Render View debug shading modes for these examples)

Debug shading	kick flags
Basic: disable all shaders in the scene, switching to a gray ‘ndoteye’ shader; a very fast shading mode.	kick -is or kick -is -sm notdoteye
Lighting: renders the scene with a white lambert shader	kick -is -sm lambert
Occlusion: use ambient occlusion shading	kick -is -sm ambocc
Wireframe: displays geometry as a wireframe	kick -is -cm polywire or kick -is -sm ndoteye -cm polywire
Normal: visualizes the normal vector (between 0 and 1, in tangent space)	kick -is -sm flat -cm n
UV: displays the coordinates of the primary UV set (red=U, green=V)	kick -is -sm flat -cm uv
Primitive ID: displays random colors based on the per-primitive (triangle, curve) index	kick -is -sm flat -cm prims
Barycentric: displays intra-primitive parametric coordinates (barycentric for triangles, parametric length, and width for curve segments)	kick -is -sm flat -cm bary
Object: displays random colors based on the per-object ID	kick -is -sm flat -cm obj

Arnold Support Corner

Tips, tricks, and troubleshooting help from Steve "xsisupport" Blair

Author Archives: xsisupport