[Jesper Pedersen]

Hi,
I've posted this problem in the "3ds max plug-in" related forum also, but no solutions there so perhaps someone here can help;
We are trying to render an animation via backburner (windows 7 64bit, 3ds Max design2012, latest maxwell renderer (node license only on this machine))

The individual frame images can be seen updating for each new SL update in their destination location, and when the final version of a frame is almost finished it looks fine until just a split second before saving, the buffer frame window (sorry if I'm using the wrong term here) in Maxwell server is cleared to black and instead of saving the finished image, we get this fully black image saved as the final update, thus overwriting the otherwise finished rendered image. It seems the image channel or buffer frame window is clearing to black (perhaps to prepare for the next image in the animation sequence) before the final image is saved.

So we tried sending the sequence as individual frames for network rendering, ( obviously this is VERY tedious, when sending each frame of a 900 frame sequence), and this results in the output image rendering out correctly but at a reduced resolution !!!? eg our 1050 x 576 images render at 935 x 513 pixels.

Finally we do not have the problem when the sequence is rendered directly within 3ds max on our machine running the full version license of maxwell (FYI this is a windows XP 64bit machine, although I think the issue is a backburner or maxwell renderer problem.)

Finally, I forgot to mention, that the material ID or object ID channel, which we sometimes use, do not have this problem -their outputs are saved fine!

I know others have posted similar problems, but as far as I can tell from the forum, no solution have been found.
Any solutions / workarounds would be most appreciated. Thanks,

Jesper

[Bubbaloo]

So we tried sending the sequence as individual frames for network rendering, ( obviously this is VERY tedious, when sending each frame of a 900 frame sequence)

I don't understand why this would be tedious. Just set your render options for a sequence of frames, set your output paths, then go to File > Export, choose the MXS format, check the animation tick box with sequenced file numbering). Easy!

Then use the network wizard to render your MXS sequence.

Please, if you have any questions about the process, I will be glad to help you.

[Jesper Pedersen]

Hi Brian,

Thanks for your quick response.
I'll test out the process you're suggesting, but I've a feeling it'll mean adding several extra steps to our rendering workflow.
We currently render with maxwell, via backburner from within our 3ds max scene. This is effectively a "one click solution" with complete control over what images are rendered. I am not familiar with the method you are suggesting but am I right in saying if we use your option we have to open the exported mxs file (which is about typically about 500MB in size -opening this file takes about 2minutes alone!) send the render sequence from the maxwell studio etc !?

This would ceratinly be better than sending each frame individually, but it's not ideal.
I would much rather get our current method of working directly from with in 3ds max working correctly as it's a more efficient workflow. It has been working for us smoothly until recently so I may have to try reinstalling the Maxwell software -but to be honest it's an odd problem -I mean why would the output files not save / save black ? and what could cause the problem with output images being saved at a different resolution size than that specified?

Jesper

[Bubbaloo]

am I right in saying if we use your option we have to open the exported mxs file (which is about typically about 500MB in size -opening this file takes about 2minutes alone!) send the render sequence from the maxwell studio etc !?

Absolutely not. I never use Studio. Ever. You just open the Monitor, pick the nodes you want to use, add a job (animation, batch, still) then pick the MXS file(s) to render.

I strongly suggest digging in to the Maxwell network wizard. It is so easy. I use it daily with no problems.

As for the other problems you mention, I can only guess that the variable in the equation is Backburner. But with the network wizard, there's no need for it.

[Jesper Pedersen]

Hi Brian,

Ok, thanks for the tip. It still seems like an extra step to me but I also know how much time you put into testing new techniques so I'll definitely give it a go.
I might try reinstalling backburner also, just to eliminate the possibility of some error here.

Thanks again,

Jesper

[Bubbaloo]

Cool, keep us updated!