RenderTITAN
02-08-2008, 05:42 PM
Lately we discovered a problem with VRAY for Cinema 4D.
If we received a file from somebody that used “VRAY for Cinema 4D” and they used different "units" than our systems, items that are distance dependent (like light falloffs...) would no longer match as intended. What's worst is that whatever that unit is, that measurement is not recorded so we wouldn’t know what to set the units too without calling the client.
This setting could be manually changed on one workstation but when set in to NET Render, it would use some kind of default unit. (Ironically, even if we set the NET Render farm's default unit to match the intended unit, it still would use something different, but we haven't figured out what is NET render's default unit (maybe meter?) It seems the client software for NET has its own setting that can't be changed (we tried but it doesn’t work with the preference file.)
VRAY for Max doesn’t have this problem because the units is set only in the plug-in, not in Max.
However, we wrote a script that seems to overcome the problem. By adding this script, VRAY for Cinmea4D works great. We have already tested it here on our farm successfully.
When the user adds the script, they can enter what is the intended unit which will be remembered when sent to NET Render forcing the nodes to use the correct measurements (by forcing a NET Render "Unit" Preference). For safety, we recommend that the script is only added AS THE AS STEP before sending to NET Render. (Early versions had a few issues... This seems stable but use at our own risk please.)
Download here:
http://www.rendertitan.com/RenderTITAN_VrayForC4D_SetUnitsScript_v1.2.zip (http://www.rendertitan.com/RenderTITAN_VrayForC4D_SetUnitsScript_v1.2.zip)
(Only tested on a PC)
Let us know how it works for you!
Happy Rendering,
Mark S. Alameel
President
RenderTITAN
(www.rendertitan.com (http://www.rendertitan.com/))
If we received a file from somebody that used “VRAY for Cinema 4D” and they used different "units" than our systems, items that are distance dependent (like light falloffs...) would no longer match as intended. What's worst is that whatever that unit is, that measurement is not recorded so we wouldn’t know what to set the units too without calling the client.
This setting could be manually changed on one workstation but when set in to NET Render, it would use some kind of default unit. (Ironically, even if we set the NET Render farm's default unit to match the intended unit, it still would use something different, but we haven't figured out what is NET render's default unit (maybe meter?) It seems the client software for NET has its own setting that can't be changed (we tried but it doesn’t work with the preference file.)
VRAY for Max doesn’t have this problem because the units is set only in the plug-in, not in Max.
However, we wrote a script that seems to overcome the problem. By adding this script, VRAY for Cinmea4D works great. We have already tested it here on our farm successfully.
When the user adds the script, they can enter what is the intended unit which will be remembered when sent to NET Render forcing the nodes to use the correct measurements (by forcing a NET Render "Unit" Preference). For safety, we recommend that the script is only added AS THE AS STEP before sending to NET Render. (Early versions had a few issues... This seems stable but use at our own risk please.)
Download here:
http://www.rendertitan.com/RenderTITAN_VrayForC4D_SetUnitsScript_v1.2.zip (http://www.rendertitan.com/RenderTITAN_VrayForC4D_SetUnitsScript_v1.2.zip)
(Only tested on a PC)
Let us know how it works for you!
Happy Rendering,
Mark S. Alameel
President
RenderTITAN
(www.rendertitan.com (http://www.rendertitan.com/))
