I do have the Maya batch plugin unchecked. There don’t seem to be any useful feedback in the logs. But I’ve attached one for you to check out if you like.
Job_2018-11-01_10-37-37_5bdb39e1c290561f608d56cd.zip (2.3 KB)
The Cannot open renderer description file "rendermanRenderer.xml" is somewhat common for Maya even without some new version.
It’s looking for that file in “C:\Program Files\Autodesk\Maya20XX\bin\rendererDesc”. If the file is there, then there might be a custom environment variable pointing Maya somewhere else, but I can’t find which one would control that.
I was wondering where that file was located. So is that file supposed to be put there by the RendermanForMaya plugin?
Make sure you have the modules and renderer description files either on the internal Maya paths or you modify the environment variables.
For example:
export RFMTREE=/mnt/software/pixar/RenderManForMaya-22.2
RMANDESC=$RFMTREE/etc
export MAYA_MODULE_PATH=/mnt/software/modules
export MAYA_RENDER_DESC_PATH=$RMANDESC
I have a script that contains all these variables (among others) that get sources on the startup of the machine and anytime a job starts. The Windows installer act a little differently though. They create the variables for the system and install the module file, but they end up in a weird directory with 22, somewhere in AppData if I recall correctly.
Cheers,
Mike
1 Like
hi Berkyjay to fix this you juste need put C:\Program Files\Pixar\RenderManForMaya-22.2\etc\rendermanRenderer.xml to C:\Program Files\Autodesk\Maya20XX\bin\rendererDesc and restart your machine
Thanks for the help here guys. Having experts sharing their experiences really helps myself and the community learn.
I did this and my render job was able to move forward. But I ended up getting even more errors. Did you experience any errors like this?
Job_2018-11-05_10-12-31_5be0880fc290561f3c1b7dce.zip (3.5 KB)
Looks like the install still isn’t quite perfect:
2018-11-05 10:12:28: 0: STDOUT: Error: line 1: RuntimeError: file <maya console> line 1: Plug-in, "RenderMan_for_Maya.py", was not found on MAYA_PLUG_IN_PATH.
For others, “exit code 211” means some file or other wasn’t read. Even if the scene renders fine, if a single file is missing Maya will exit with this number and that’s why we have an option in the submitter to ignore it.
OK, setting the “ignore 211 errors” worked! I’m getting renders too. But a smaller issue is that I’m getting job failures for the job…but it eventually renders. So it’s not a job killer but more of a time killer. I’m wondering if you guys know what’s going on with these errors?
Job_2018-11-06_11-12-51_5be1e7b3c290562408afed8e.zip (4.0 KB)
Looks like it is dying around license request. Can you provide one of the working reports to compare against?