[brodie_geers]

1. I ran some network renders last night and for each image checked the boxes for Render, Mat ID, Z-Depth, and Alpha. However it only produced the images for the Color Render and not the other three. Is this working as intended? I can go through and open the MXI's and save them myself (which I'm doing as we speak) but it's sort of a pain to open 5 different 500MB files and save those other three images.

2. I have one scene with 5 different cameras. It seems like I should be able to run each of those cameras as a Batch render but that doesn't seem possible. Am I missing something (beyond copy/pasting the scene so I have 5 of them)?

-Brodie

[Bubbaloo]

Can't help with #1.

#2. Is it an animation you are rendering over the network? Or just a few images of the same scene with different cameras?

[brodie_geers]

The latter, just a few images of the same scene.

-Brodie

[Bubbaloo]

You can add the scene to the queue multiple times, each time choosing a different camera/resolution using cooperative or single.

[brodie_geers]

Ya, that's what I ended up doing. It just seemed like the sort of thing that batch render should take care of.

-Brodie

[bjorn.syse]

1. I ran some network renders last night and for each image checked the boxes for Render, Mat ID, Z-Depth, and Alpha. However it only produced the images for the Color Render and not the other three. Is this working as intended? I can go through and open the MXI's and save them myself (which I'm doing as we speak) but it's sort of a pain to open 5 different 500MB files and save those other three images.
-Brodie

I experienced the very same thing. The alpha and material id were never saved as bitmap images when i did a cooperative batch render during this night.

- Björn

[bjorn.syse]

Actually, when I take another look at it, it seems they were never rendered in the mxi either. However, when i open the mxs, they were definately checked to render in there and I didn't change any settings at rendertime.

So they never got rendered using a cooperative batch render, but were part of the original mxs-files. (and the checkmark is still there in front of alpha and material id when I open the .mxs afterwards)

- Björn

[RobMitchell]

Actually, when I take another look at it, it seems they were never rendered in the mxi either. However, when i open the mxs, they were definately checked to render in there and I didn't change any settings at rendertime.

So they never got rendered using a cooperative batch render, but were part of the original mxs-files. (and the checkmark is still there in front of alpha and material id when I open the .mxs afterwards)

- Björn

I've been having this exact problem when I do batch renders on the network. The other channels are not being created when I run them this way, whereas if I was to render them individually they do. Even if I open up the MXI file they're not there, but on the MXS the nessessary boxes are clearly checked.

I'm creating the files on a Windows XP 64-bit machine and they're rendering to a Windows 7 64-bit machine on the network.

It's been quite frustrating really, but I've not had time to look into it/bring it up during my current set of jobs.

[bjorn.syse]

I'm on all XP 64 here.

[bjorn.syse]

Are there any news about this bug? I've email tech support at Next limit, but haven't received an answer yet.

[dariolanza]

Hello all,

We were studying the issue and fortunately we've isolated and fixed it.

It will be fixed in the next release.

By the way, I would suggest you two workarounds:

- Submit the jobs as Single jobs, instead of a Batch

- In the MXS scene has the extra buffers enabled (in the scene, not enabling them in the Batch dialog), and you don't change the scene settings in the Batch dialog (is this dialog what forces it to fail) then the generated MXI may have the channels embedded (even if they didn't stored them as so).
So you could always extract those extra buffers from that MXI.

The next release will have it fixed.

Thank you for your patience.

Greetings