DR Spawner Aggravations

[ValeroStudio]

I have finally gotten sick of waiting for my 4 core machine to render a still and setup DR spawner on another computer in the office. I waited so long because the few experiences I have had with DR have been spotty and I would consider it still a unstable feature in V4SU.

Guess I was right. Sometimes DR Spawner works like a charm and sometimes I want to throw it out the window. Is the latest version still have bug issues with DR? The issue I am currently having is 1) sometimes the other machine never starts even though I have everything config correctly and DR spawner is running on the other machine. 2) sometimes the other machine kicks in and starts rendering some other random scene, where the buckets it renders are at some other camera point??? Very bizzarre and very inconsistent.

[ValeroStudio]

cricket, cricket - no replies?

So.... is DR Spawner buggy right now? I have mixed reviews of it.

[dkendig]

We get mixed feedback. It works fine for some, and it's intermittent for others.

[thomthom]

I'm experiencing very random results as well. When I try to debug the problem in order to find a reproducible case to report it all works fine. But when I'm doing an actual job I need to complete it fails.

[ValeroStudio]

This is what I experience as well. Its like the DR Spawner knows when I am on a tight deadline and thats when it doesnt work!

[dkendig]

if it can't be reproduced reliably, that makes fixing the elusive bug a tad more difficult

[ValeroStudio]

A reboot of the server machine sometimes resolved the problem. Larger scenes definitely seemed to be more of an issue for DR, for obvious reasons.

[peerman]

Same here, Running OS X. I also have the problem of the DR slave renders another/previous camerapoint.