[fv]

Hi,
I am trying to add a node that previously was released back to the same running job again.
But when I select the job and right click "add node" the selected node does not start coöperating. Although the status of the node shows its ready.

Probably overlooking something. Any help is apreciated. OSX nodes all OSX. Manager and two nodes on 10.6.8 and the node I am trying to add runs on the latest OSX.
I can stop the job and resume with all nodes back on duty though as a workaround.

Francois

[Mihai]

This sounds like a bug, we'll look into it.

[fv]

ok, tx.

something else,
when I resume a render the nodes start again at SL 1 but the reached level still looks to be updating slowly from level 16 for instance. While the previously stopped job showed all nodes just 1 or 2 (14 for instance) behind the combined SL level (16 for instance). Maybe thats normal but it looks a bit off.

Another very small "bug" in the Network monitor. When you ask for a preview in the display window you can't "command +" to zoom in or (-) out. That does work in Maxwell though. In the network monitor you can only use the scoll on the mouse. Thats ok but it would be nice if both behaved the same.

I just discovered network rendering and it works really great for the rest.
Francois

[numerobis]

i have similar problems adding and removing nodes from jobs. it's very unreliable for me and most of the time not working as it should.
The status display ("ready" ect) doesn't correspond with the actual status.
To remove and re-add a node to a job i have to first kill it remotely then remove it from the job and then add it again otherwise
the job will start on the node but is not recognized by the manager...

And i still have this problem with extreme delayed starting ( never starting) nodes. Sometimes only 2 or 3 of 9 nodes are starting.

And why does the "Reset selected nodes" button only kills the node but doesn't restart it?!? What is the difference to the "Kill"-button?

[Fernando Tella]

That has never worked here. Once I release a node I cannot get it back for the same job. Windows 7 64 bits. I thought it was already known.

[GMcDowellJr]

+1

[naxos]

+1

[gadzooks]

Same here as well!

[Bubbaloo]

In a cooperative network render, you can highlight a node that's rendering and stop the render in only that node. The node will send it's MXI to the manager and it will be ready to render the next available job. It's only advisable to add or remove a node from a PENDING job. It's also inadvisable to kill a node during an active render.

So to be clear, to safely remove a node from a job, highlight the node and click the stop button.

Of course, the safest thing to do if you want to make changes, is to stop the job, let the MXIs merge, then resume the job with the nodes you want.

It is a bit touchy, some buttons are dangerous at different times during the render process, but once you learn how to handle these tasks, it's actually very reliable.

[Rogurt]

... stop the job, let the MXIs merge, then resume the job with the nodes you want.

Even that does not work over here. No adding of nodes to jobs whatsoever. Only deleting the job completely from the manager and adding it once more gives reliable results.
I am really frustrated that this bug is unsolved for such a long time now...

Cheers,
Rogurt