Hi all,
Anyone know the possible cause for this? While rendering with V-Ray RT-CPU, if an image used for a texture map is located on a network share, then it renders as black in the rendered image. It is as if the image cannot be read so the default color black is used in the render. If the image is placed on the local hard drive, the image's colors are used in the render. If the renderer is software based VRAY, the network based image's colors are used in the final render.
Is there a log anywhere which v-ray would output errors or a way to increase the verbosity of output while rendering so it is easier to debug this issue? I currently see no errors in the script / console window while rendering in V-RAY RT CPU
OS: Windows 7 Pro
V-Ray For Maya Version: 2.40.02
Maya Version: 2014
Steps we have taken:
1) We disabled the firewall on the Windows machine. It was on originally so we turned it off and reboot the machine. This did not solve the issue.
2) The user can read and write data in to the directory where the image is located so it doesn't appear to be permissions related, though there are advanced ACLs in place.
3) I used a different image format and the issue is the same.
Thanks for any tips.
Adam
Pipeline TD / Software Engineer
Anyone know the possible cause for this? While rendering with V-Ray RT-CPU, if an image used for a texture map is located on a network share, then it renders as black in the rendered image. It is as if the image cannot be read so the default color black is used in the render. If the image is placed on the local hard drive, the image's colors are used in the render. If the renderer is software based VRAY, the network based image's colors are used in the final render.
Is there a log anywhere which v-ray would output errors or a way to increase the verbosity of output while rendering so it is easier to debug this issue? I currently see no errors in the script / console window while rendering in V-RAY RT CPU
OS: Windows 7 Pro
V-Ray For Maya Version: 2.40.02
Maya Version: 2014
Steps we have taken:
1) We disabled the firewall on the Windows machine. It was on originally so we turned it off and reboot the machine. This did not solve the issue.
2) The user can read and write data in to the directory where the image is located so it doesn't appear to be permissions related, though there are advanced ACLs in place.
3) I used a different image format and the issue is the same.
Thanks for any tips.
Adam
Pipeline TD / Software Engineer
Comment