Page 1 of 1

Cooperative rendering buggy after 2.7.0.0 upgrade

Posted: Thu Aug 16, 2012 1:05 pm
by feynman
Cooperative rendering works once, then only uses 1 node on subsequent renders.

- No error messages in nodes, manager, etc.
- Task manager shows non-rendering PCs idle
- Happens with all combinations of 2-5 PCs
- First occurrence after upgrading 5PCs to 2.7.0.0; no other changes except Windows 7 upgrades
- Other software using >2 PCs (cooperatively) does work as before
- Also Time Elapsed shows wrong timing

Is this a known bug? Thanks in advance!

Image

Re: Cooperative rendering buggy after 2.7.0.0 upgrade

Posted: Thu Aug 16, 2012 2:52 pm
by Mihai
Is this the same scene, but difference output settings? If you can, please restart all the network components, then delete all temp files from Manager, Monitor, Nodes and try (File>Purge temp files). Did you install the 2.7.10 patch also?

Re: Cooperative rendering buggy after 2.7.0.0 upgrade

Posted: Thu Aug 16, 2012 3:27 pm
by numerobis
feynman wrote:Cooperative rendering works once, then only uses 1 node on subsequent renders.
Is the node showing "New job order received"?

http://www.maxwellrender.com/forum/view ... 72&t=37997


I have this wrong "Time elapsed" display too since the update to 2.7.10 (never tested 2.7.0)

[SOLVED] Cooperative rendering buggy after 2.7.0.0 upgrade

Posted: Thu Aug 16, 2012 4:26 pm
by feynman
@Mihai/numerobis Thanks, will do that and see how that goes. Failing that, maybe it goes away after installing the 2.7.10 patch...

Red ear syndrome - on the sluggish nodes, a viewport render was in progress, hence these busy nodes can't participate in a full render (at least, that's my understanding that the viewport render takes priority?) so now that issue has disappeared. That's one of the downsides when using 5 PCs with only one set of mousekeyboardscreen.