I’ve got an issue where I let vray go all weekend on a rendering (3200x1800 pixels) and came in today to find it stalled roughly two-thirds through. We had five dual machines working on it, and when it stalled the buckets were in all different parts of the render -- so it wasn’t a specific object or material that did it.
My coworkers say that they’ve had that happen before and they’ve only gotten around it by reducing the pixel size of the render. Just thought I’d ask if there were any known issues that might cause this out there -- otherwise it must have been a hiccup in our own network that caused it, which I’ll have to look into.
DR is a mostly not working feature in V-ray (thats what i have found).
There are too many problems and pits you can trap into.
Lets hope that they will make a production ready DR function for V-ray 1.5.
We have waited long enough.
But it seems to be a very difficult problem to code a stable and working distributed rendering engine.
Banshee (the DR engine from Brazil) is overdue for 5 months now and still no sign or release date.
I have had similar problems on large images even without DR and they went away after deactivating hyperthreading on my machine. I recommend doing so urgently if it’s switched on on one of the machines.
I’ve just started an animation on 2 computers to see that DR doesn’t
work on Max 5 too…
Here is not a problem of image size, it is very small (400*170),
I made a test in 640 480 with the same result.
Moreover, the wrong image is calculated on the master computer.The
slave works correctlt !!!
The problem here is due to Vray Material… Yes.It is badly calculated if
it has an image to render over an object.I thought it was a problem of
directory but no.
In fact, with a standard max material, there is no problem…
I’m going to search if some other people have had that problem
