CAnnnot render in the OSX terminal via maya render -r vray command

[3Dmotif]

every time I try to render via maya batch using the render command using -r vray
I get the following error:

Cannot open renderer description file "vrayRenderer.xml"


I checked and I'm getting conflating information and nothing is working.

I'm using OS X 10.9.2

Maya 2014 Ext SP1

I have the vrayRenderer.xml file in both :

/Applications/Autodesk/maya2014/bin/rendererDesc/vrayRenderer.xml

and

/Applications/Autodesk/maya2014/Maya.app/Contents/MacOS/rendererDesc/vrayRenderer.xml

please advise this is really annoying and seems to be kinda common on OSX so perhaps the installer can be altered to fix it.

But I really need to batch render and I cannot as of this moment

[tashko.zashev]

Hi,

Do you have more than one Maya versions installed on this machine?

Also check where MAYA_RENDER_DESC_PATH environment variable is pointed to.
You can do that by running the following in the terminal
Set |grep MAYA_RENDER_DESC_PATH

You need to add the path that points to "vrayRenderer.xml" which is /Applications/Autodesk/maya2014/bin/rendererDesc to MAYA_RENDER_DESC_PATH variable.

Hope this helps.

[DPGrafik]

Have you considered using Pipeline render management? I was in a tight spot regarding a deadline this weekend, and i neede to batch several frames on my very small render farm (4 machines.) I installed Pipeline and used vray standalone after i exported a vrscene file - no command codes or anything just a nice GUI job submitter from pipeline itself and your good to go.

[spacematt]

Hello, we're on Vray 3.1 now, and wondering why we're still having a problem with vrayRenderer.xml. Is it just being installed in the wrong place?

We don't use MAYA_RENDER_DESC_PATH, and the problem is fixed by...

sudo cp /Applications/Autodesk/maya2016/bin/rendererDesc/vrayRenderer.xml /Applications/Autodesk/maya2016/Maya.app/Contents/bin/rendererDesc


I thought it was just a bug in our first version, 2.4, but it's the same in 3.0 and 3.1

[svetlozar.draganov]

It seems that this issue is not fixed yet, I have discussed it with one of our developers and he mentioned that this is a very simple to fix and it shouldn't take much time.
I'll keep you posted.

[svetlozar.draganov]

This issue has been fixed for the next official service pack.

[ivaylo.ivanov]

Will be fixed in the next stable 3.1 build here:
https://nightlies.chaosgroup.com/mai...le/stable_3.1/

[spacematt]

Great news, thanks!

[svetlozar.draganov]

Would it be possible to test it into your environment and let us know if everything works fine or if there are any issues?