We're having a bit of trouble with railclone and distributed rendering with V-Ray. We are using Max 2014 on the workstation, with railclone 2.4.7. We are distributing to nodes with Max 2015 and railclone 2.4.7. Up until now we have been rendering very successfully with this set up. The problems have occurred when we have been working with a collaborator. They are using railclone 2.3.4, and they created the railclone objects that seem to be causing the failures. It's worth noting at this point the files in question are very large/heavy and complicated. Possibly not able to upload as the resulting .zip would be huge, but if someone from itoo can help I'll do my best to get it to you.
I have been through all the files associated with the master file and checked and double checked the paths for all files/objects/textures etc. and there are none missing.
The manifestation of the problem is that the render starts on the master machine, the process of transferring assets to the nodes is begun and the nodes start loading the assets/scene into their ram. At an un-definable point (at least I don't know how to define it) the slave machine gets a Max error and the loading process crashes out. The v-ray spawner re-loads and the process starts again.
I am not sure what else to try as I have also checked and double checked the nodes for plugins etc. As I said before, normally they render fine. It's just with one or two of this job's files that have been started by our collaborator. It's worth noting that it's not all his files on this job!
I hope someone can shed a bit of light on this, as we are having to resort to rendering on the desktop machine only, which is painfully time consuming.