No I didn´t use "Get ID by Element" and "Tint by Element" in the Forest Color map. Didn´t even know it.
I checked forestpack.ini. It was set to 0. One render node didn´t have this file at all. So I copied it there. This time it stopped with the first image.
Did I make it worse by copying this file there? Should I remove it?
Now I deleted the forest objects to test if distributed rendering from batch still works at all.
Since rendering the whole sequence of 6 images takes about 2 hours testing takes a while.
During the last week I tried different things:
With smaller resolution (1/2) it worked.
Deleting Forest worked.
I tried turning off camera cliping but one node couldn´t flush its ram in between (?) - so I turned it on again.
I even started to install my workstation again completely. Now just running max. No other programs. Then I deinstalled norton 360 and switched off windows firewall in my network.
So does it work at all in this constellation?
After this test without forest is finished I will turn off cliped camera and erase big parts of the forest objects (grass) that are not seen with any camera to increase the faces/objects in the scene.
Have you any other idea how I could solve the problem using distributed rendering since I am not familiar with bucket rendering?
What is a bit strange is the fact, that it renders a different number of images fine. I can´t even really rely on one completely rendered sequence...