Distributed Rendering, cache?

[tinuz]

Hi,

I'm having a really weird problem:

I have a character with a geometry cache attached which is inside the project folder.

2 of my 4 render hosts for DR are rendering the character ALWAYS on frame 1, the other two and the machine that is distributing the job are rendering the frames they are supposed to render,
so i get an image sequence where the buckets of the two faulty ones always show frame 1, and the rest of the buckets show the animation.

-I've tried killing and restarting vray on every host manually
-there are no error messages on the hosts
-textures are loaded correctly on every host
is there a cache somewhere I need to delete?
any ideas?

[tinuz]

ok restarting the hosts solved the problem..
But I am curious if this is solvable without restarting..

[Zdravko]

Try using "Restart slaves on render end" option which will automatically restart your render slaves.
http://www.spot3d.com/vray/help/150S..._rendering.htm

[vlado]

Try using "Restart slaves on render end" option which will automatically restart your render slaves.
http://www.spot3d.com/vray/help/150S..._rendering.htm

Hm, I don't think this option is in Maya... Do you render through Maya on the main machine, or through V-Ray Standalone?

Best regards,
Vlado

[tinuz]

isn't that a vray for max feature and non existent in vray for maya?
aha Vlado beat me

I am rendering via Smedge which starts vray standalone on my main machine
and that render uses four DR hosts..


I did found out that most of my problems were caused by crashed slaves on the DR hosts
So now we are in the progress to change our setup so that I can start and view output of the vrayslaves on my main machine, mostly because when vray is registered as a service you cannot see any output or errors on the slaves.

so i think my original problem was caused by crashed slaves..

another question:

suppose you kill vray.exe from the processlist does that leave any "dirt" around?

[Zdravko]

We researched about that bug and it turned out that this is a issue caused by Smedge render manager.
Please contact Smedge developers for any further assistance.

[tinuz]

yikes! nasty!

good to know, thank you Zdravko!

[tinuz]

We researched about that bug and it turned out that this is a issue caused by Smedge render manager.
Please contact Smedge developers for any further assistance.

I've contacted smedge support but they haven't responded yet.
In the meanwhile is it maybe possible for you to share any information from your research in this bug?
I can't find any other cases on the web..