RPManager Forum

Hi

has anyone experienced 3dsmax 2018 64bit, with RPManager sending out instructions to Backburner to render 2 Stills each time you want to render a single image, even though it is told to just do a Single frame...

It also says a warning everytime i send a job to backburner that there is no output path set, images will not be saved, even though they are and they do save fine, so seems a false positive warning kind of thing.

Hopefully these minor Bugs can be fixed...

I am on max 2018, rpmanager 6.52 and have not experienced this issue, I suppose it does not happen with a regular backburner submission?
The output path warning I do have though, but I'm using vray framebuffer and the warning has always been there so I'm just used to it

We have ran into the dual rendering frames issue for a while, but only on occasion. We rarely submit a single frame for rendering, we've seen it happen with sending a 6 frame job and it renders on 12 nodes, so same deal. Still on 2017 for production here. I think it happens when we submit via commandline w/ RPM, which sometimes wind up having to do, usually toward the end of a project, when the scene stops wanting to submit with the normal RPM submission process. I always figured it was more of a backburner bug since it's backburner that is choosing to send the same frame to multiple machines.

Same problem here on 3dsmax 2016, first time i think it was a bb problem, but... If i try to launch à job without rpmanager, it doesn't render twice it...
Is there à way to solve that really boring problem that's cut my renderfarm in two...

Cheers!

Did anyone find a solution? I'm here almost a year later, having the same issue on MAX2017. It affects our entire renderfarm, and limiting Backburner to 1 job pr. submission, is not an option, as we do animations as well.

Cheers,
/Nick

So one theory I have is that this may be backburner getting ahead of itself and the job isn't fully submitted before slaves start picking it up - and despite being just one frame, multiple slaves have a go.

To test this, I've added an option at the bottom of the Extra options in the BB rollout, 'Submit suspended the auto resume'.

The idea is that the job is submitted suspended, so it can completely submit - and then RPM will resume the job after a 1 second delay internally. Note that the resuming requires queue control, so that will need to be granted (though it auto takes it after 10s unless someone presses the 'no' button).

http://www.rpmanager.com/installers/RPM ... p_6.67.exe

Let me know if this behaves any differently for this issue.

cheers,
grant