Backburner and 3DS Max Design 2014

[Anonymous]

Hello!

As we have a little Renderfarm in our company and I experienced a lot of problems with the latest releases of Autodesk Backburner, I got very good results with Backburner version 2008.1. 
We are now switching from 3DS Max Design 2012 to 3DS Max Design 2014. I wrote a little script for sending my render jobs through Max to the renderfarm in Max 2012. After converting the script for the 2014 version I tried to send a job to the renderfarm. Everything works fine so far, the only problem I have now is that the sent job is tagged as "complete" after the manager received it. I tried to run my script with different versions of Backburner but my script won't work with that versions.

We also tried to upgrade to v2014 of Backburner and had good results with our script, the only problem is that it won't send the dependent job which is making the video. Its like the command line has some problem with the conversion of the flags (see screenshot)

Details about the jobs:
The first job will be sent through the Maxscript NetRender commands. This is the normal job to render video scenes. 
A second job is sent which has a dependency to the first one. After Job 1 is complete, the second one triggers a executable to convert the images from the first job to a video file.
Works fine on Max 2012. Not with 2014, because the first job is received by the manager with the tag "complete".

Structure of the farm:
One server handles the manager (2008.1) and one backburner server which is reserved for the dependant job which generates the video. This server doesn't render the scene.
Multiple nodes with backburner (2008.1) which render the single frames of the sent scene.

Does someone have the same problem? Or any suggestions for a solution?

Thanks.

[Laurent.Pallares]

Hi dear,

This will be more related to an ADN request, posting the request to the ADN forum, willd surely get a better feeback:

here is the link

[BenBisares]

Just wanted to chime in here.

We have an known issue (fixed but going through QA so not publicly available yet) that seems similar to what you're getting but not exactly the same. In a nutshell when using the "-servers" flag the first character of the server name would be changed, exactly what you're getting but with dependencies. The current workaround is to use the "-group" flag, creating a group consisting of the chosen server(s).

Although they're not the exactly the same I would try either the above workaround or not setting any particular servers to the job to see what happens. I'll try reproducing you're issue. I haven't recently did a command line Backburner job with dependencies.

I'll keep you updated with my findings.