Im curious to find out if the VFB has been fixed to work in OSX in the newer builds of Vray? I've been using the hack provided in the docs, but am having a multitude of problems by calling it this way. Im no mel scripter, so this could be failing on my part in customizing it to own environment. Below is a list of the more notable problems.
The Script:
$tmpfile = "/var/tmp/tmp.vrscene";
setAttr vraySettings.vrscene_render_on 0;
setAttr vraySettings.vrscene_on 1;
setAttr -type "string" vraySettings.vrscene_filename
$tmpfile;
renderIntoNewWindow render;
removeRenderWindowPanel renderView;
system ("/Applications/Autodesk/maya2008/Maya.app/
Contents/vray/bin/vray -scenefile=\"" + $tmpfile + "\" &");
system ("rm " + $tmpfile);
1. When executed, occasionally the VFB will render a completely unrelated scene that i've worked on previously. I assume this is because its linking to an old .vrscene and in fact, if I go into the folder its being written to, I can see a multitude of old .vrscene files floating about. The way im interpreting this script is that it writes a temp .vrscene, renders it, then deletes it. Why this only works sometimes is beyond me.
2. The store image button is missing when the VFB pops up.
3. The maya framebuffer pops up before executing the VFB and fails to close, which from the code it looks like it should do. Also, you have to close the VFB in order to get back to working in maya which is an annoyance.
Im posting this here in hopes that someone can better educate me on why I am experiencing these problems, or, better yet, post an improved version of this "hack."
Thanks in advance.
The Script:
$tmpfile = "/var/tmp/tmp.vrscene";
setAttr vraySettings.vrscene_render_on 0;
setAttr vraySettings.vrscene_on 1;
setAttr -type "string" vraySettings.vrscene_filename
$tmpfile;
renderIntoNewWindow render;
removeRenderWindowPanel renderView;
system ("/Applications/Autodesk/maya2008/Maya.app/
Contents/vray/bin/vray -scenefile=\"" + $tmpfile + "\" &");
system ("rm " + $tmpfile);
1. When executed, occasionally the VFB will render a completely unrelated scene that i've worked on previously. I assume this is because its linking to an old .vrscene and in fact, if I go into the folder its being written to, I can see a multitude of old .vrscene files floating about. The way im interpreting this script is that it writes a temp .vrscene, renders it, then deletes it. Why this only works sometimes is beyond me.
2. The store image button is missing when the VFB pops up.
3. The maya framebuffer pops up before executing the VFB and fails to close, which from the code it looks like it should do. Also, you have to close the VFB in order to get back to working in maya which is an annoyance.
Im posting this here in hopes that someone can better educate me on why I am experiencing these problems, or, better yet, post an improved version of this "hack."
Thanks in advance.
Comment