Messages have the following format:
API 0.1 error 301031: file.mi, line 123: call to undeclared function "X"
For explanation on mental ray modules such as API, go here
As for the rest of the header:
0 = Two characters (or more) for the number of the machine on the network, if network parallelism is used. Machine 0 is always the client machine where the rendering machine was started.
. = The decimal point separate host number and thread number. It is replaced by a colon if the thread is started by an application that mental ray is integrated into, rather than mental ray itself.
1 = Two characters (or more) for the thread number, if thread parallelism is used. Thread 0 is the mainline thread. Thread n is a special network communication (network parallelism only).
error = Six characters for the message level: fatal, error, warn, info, progr (progress), debugm and vdebg (verbose debug).
301031 = Seven characters for the fatal, error, or warning code number. The other message classes omit the number. The number uniquely identifies the message; it is intended for applications that mental ray is built into that need to know about problems without having to analyze an English text string. The number begins with a module ID (30 means API), severity (1 for (fatal) errors, 2 for warnings) and a sequential three-digit number that is arbitrary but unique for the module and severity.
The remainder of the message is a plain English description. Shader and Phenomenon scene elements.
Subscribe
Comments