[b-kandor]

This is a crop of a coop image I finished this morning. It has three lines that run horizontally from one side to the other. The render had 4 machines, one rebooted during the night (so it showed 'lost'). I rebooted it this morning and the manager picked it up and resent the job - so it was included in the final merge still.

Any ideas? - Or how can I best recycle the hours I have invested here:

[tom]

This error rarely happens due to some unknown reason(s) while auto-merging. You can still find the cooperative.mxi files under each machine's OS's temp folder and merge them manually so you'd save the invested hours.

[b-kandor]

Hi Tom,

If I try to merge them manually (leaving out the one that has the lines) - I just get a message saying they have the same seed.

I have one mxi that is at 14.4 sl. If I want to resume that, but resume it on all machines so that the output can merge - is this possible?

ie. Can I copy the mxi 4 times, and resume manually specifying a different seed and then be able to merge them?

Thanks for your help,

Kandor

[tom]

If I try to merge them manually (leaving out the one that has the lines) - I just get a message saying they have the same seed.

Don't worry, it's normal because some of them are properly merged and merged ones are no more having unique seed. So you should ignore the error in this case, because it will always merge the available ones.

I have one mxi that is at 14.4 sl. If I want to resume that, but resume it on all machines so that the output can merge - is this possible?

You can only resume it on a single machine. It's mathematically impossible to resume the same initial seed as it's different seeds. Coop can only resume with locally created MXIs.

ie. Can I copy the mxi 4 times, and resume manually specifying a different seed and then be able to merge them?

Of course, no

Imagine if that was possible we could build a self feedback system which renders merges and redistribute and resume... Which will render any scene in a very short time. But it's impossible.

[b-kandor]

Imagine if that was possible we could build a self feedback system which renders merges and redistribute and resume... Which will render any scene in a very short time. But it's impossible.

Ok, I'm imagining - now, just remove the 'impossible' from the above and I think your onto something....

[tom]

now, just remove the 'impossible'

Removing... cya!