Please try this.

build some simple animation in the scene.

(this should work)
batchrender (using the batchrender-dialog from the rendering dropdown) the scene - saving the the rendered output to a sequence of jpg’s. - everything should work fine and you end up with a sequence of jpg’s

(this should create the bug)
Now batchrender the same scene again, only this time you use the net render option in the batchrender-dialog - ie you use backburner (i just run it locally here). This time you (if you have reproduced the problem) end up with only one jpg because the filename isnt incremented with each rendered frame.

EDIT:
It seems installing the connectivity extension for max 2010 fixed it for me :-)

I just thought I’d bump this old thread because as I found out overnight during crunch time of a very time-critical project, this is still a bug in Max 2011. Every single one of my Batch renders resulted in only one frame each. Ridiculous.

Now, I read that simply adjusting the render dialog to be either active or custom range would fix it, but I’ve tested and this is not the case. Perhaps if I delete and recreate my batch renders with this setting changed, it might have an effect, but as of right now, nothing I can change will make my existing batch renders output more than one frame.

I also watched as each node rendered the frames, and this is not simply a case of the machine not incrementing the filename.. Each node just keeps render frame 0. They never progress through the animation.

If you right click on the Task Summary entries in Backburner, it shows you the filename it should have been rendering to, so the Network rendering system clearly knows which frame and which filename it should be using, but somewhere it is not communicating that to the rendernodes.

This is a stupid bug that has been around since 2009 (according to this thread) and possibly even before that.  Is it too much to ask that we get a hotfix for this?

Once you change the Render Dialog to a sequence instead of a single frame, you need to hit the Render button.  Cancel the render job right away, but the settings change isn’t fully recognized until you tell it to render.

I just always leave it to the Active Time Sequence, then change from Production to Iterative (bottom left of the Render Setup dialog).  This makes it ignore many of the settings in the dialog.  Learn more about it from the Help menu.

3DS Max Design 2011 64-bit - Advantage Pack
Dell Precision T5500, Dual Six Core Xeon X5650 @ 2.67GHz, nVidia Quadro 5000, 24 GB RAM, Win 7 Enterprise 64-bit
Minneapolis, MN, USA

Oh man! This bug is annoying! I just wasted a weekend worth of rendering on a simple problem that has existed since Max 2010 and I’m using Max 2012 (servicepack 2)… When you choose a range of frames to render in the batch render interface you expect Max to be able to number them properly, not overwrite the same file over and over again!!!

Yes I can confirm that in the renderer common parameters it was set to single, but I didn’t expect that it mattered when I used the Override Preset and used range in the Batch renderer.

Has anyone notified Autodesk through the bugreport system, or is it just posted here, and expected them to find out by themselves? Since this is an old forum thread, I don’t expect anyone to read it anyways, but I will post a bug and refer a link to this thread!

--
Markus Schille
Visual Artist at Aker Solutions

Current System:
3dsMax 2012 - Servicepack 2 - Win 7 Enterprise 64 bit
HP Z800 - 64 GB Memory - Quadro 4000 (2 gb) - Intel Xeon X5675 @ 3.06 GHz (2 processor. In total 12 cores)

Just got hit with this one myself. I might have found a workaround though.

When sending multiple renders to backburner via batch render dialog, I unchecked, then checked the “override Preset” to refresh the settings. All the jobs that was beeing sent, was active before doing this.

Hi all

I’m actually coming from Maya but this was the only thread I found about this issue. I hope I am not breaching forum rules by replying here.

The problem in my case was I had frame renumbering turned on in Render Settings with each field set to one. This caused render.exe to renumber the saved frame to 1 each time, thus overwriting the file. Turning this off solved the issue.

A simple solution to an easily overlooked (for me at any rate) setting.

Tom

Still a problem in Max 2013!!!!

Hello Autodesk.....?!?!