Vray voxel error

Deadline
1

Good Morning,

A couple months ago we started getting the following error on deadline:

image
image2016×60 8.05 KB

Has anyone ever seen voxel errors like this on deadline or have any idea of where to start looking? We have tried looking at permissions, changing switches, new cables, etc and still get the error. Any info on where to start looking would be appreciated.

2

I would suggest contacting Chaos support, or posting on their forum. This is likely vray specific, could be related to vray versions, etc.
Are you able to load the same mesh locally?

1 Like
3

Everything renders fine locally if the assets are local. The minute we hit the network to our repo is when the problems arise. The only post I’ve found was from the chaos forums where a guy talked about solving it by changing from a mapped drive to a UNC path. I was curious if any other deadline users had seen this issue and if changing the mapping within deadline could help.

4

I suppose you have configured R drive in deadline correctly?

5

So this is the part we are a little confused on. Our drives are mapped at the windows level, but the mapped section in deadline is blank. Should the mapped section in deadline also be setup?

6

We had issues with this too. The drives are mapped by policy, but sometimes somehow they were not mounted on time or something.
You should definitely set them up in Deadline. Also I think svc_deadline can see different mounts than other users.