By Jesper Pedersen - Sun Oct 02, 2011 2:54 pm
- Sun Oct 02, 2011 2:54 pm
#347513
Hi
We are trying to render an animation via backburner (windows 7 64bit, 3ds Max design2012, latest maxwell renderer (node 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. We do not have this problem if the images are sent as individual frames for network rendering, but obviously this is VERY tedious, when sending each frame of a 900 frame sequence as in this case. Also 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
We are trying to render an animation via backburner (windows 7 64bit, 3ds Max design2012, latest maxwell renderer (node 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. We do not have this problem if the images are sent as individual frames for network rendering, but obviously this is VERY tedious, when sending each frame of a 900 frame sequence as in this case. Also 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
- By Mark Bell
- By Matteo Villa