600 minute timeout

[invisiblecities]

I know its not really a vray problem but adesk are not being much help and i wonder if anyone has come across this problem? Backburner cuts off a render after 600 minutes , doesnt matter what time you have set in the monitor . Im running max 9 and the most recent backburner 2007.0.02.. any help would be greatly appreciated

[gilpo]

http://www.chaosgroup.com/forum/phpB...ic.php?t=15990

It's still a problem for us. Have tried using every combination of backburner versions and no luck.

[themaxxer]

with backburner 3.02 it worked for me, also if I set the time to 6000...
but I work with max8.

best regards
themaxxer

[invisiblecities]

maybe this

I did not have max 9 running on the machine where the manager i s located so I have installed it now and will set a render for tonight to see if it works

[gilpo]

Maxxer,

We're on Max 9 using a 3.02 manager.

Are you setting the time in the job dialog when you send it to the manager or elsewhere?

[themaxxer]

Maxxer,

We're on Max 9 using a 3.02 manager.

Are you setting the time in the job dialog when you send it to the manager or elsewhere?

I set the time in advanced tab in the job dialog. but i render stills under the time limit of 600 minutes. will it be reseted on every frame in animations then? if so I didn't reach the timelimit ever...

best regards
themaxxer

[cob]

i used to have the prob before, can't remember how exactly i fixed the issue.

try manually editing the "backburner.xml" file in ur "C:\Program Files\Autodesk\Backburner\Network" folder, and change the numbers to the higher recommended ones.

it also used to be a prob with the right/permissions to the backburner folder. once u give the user admin rights to that folder, it also helps.

see if that helps...

[invisiblecities]

problem solved morbid wus right

Yes .. all it needs is Max 9 installed on the machine where the manager is running then all is good..happiness returns ..12 hr renders

[bhchllc]

argh... we just upgraded to max9-64bit with backburner 2007.0.2 and this timout thing is biting us in the a$$. We have changed the timeout to 20,000 minutes on the manager machine and confirmed the xml file is correctly reflecting that number. We have changed it on the workstations and confirmed the xml file is correctly reflecting it there, and we have confirmed that the monitor also reflects this number for the jobs. Problem is, it is still bombing at 600 minutes.

Max 9 is installed on the Manager machine ... BUT ... that is a 32-bit machine (our server) so it obviously has Max9 32 on it. Could this be the problem? It appears that Backburner is a 32-bit app anyway as it installed in the x86 folder on the 64-bit machines so it is technically the same version of backburner running on everything. Any ideas... PLEASE? Can anyone confirm they have it working properly with a 32-bit manager feeding 64-bit rendernodes?

EDIT:
More info to add. If I open Max 9-32 on the manager machine and attempt to send a job from that machine, it is defaulting to the timeouts disabled and 600 minutes. If I change it and reopen it, it keeps reverting back to the default configuration even through the xml file on that machine has it at 20,000 minutes.

[invisiblecities]

why not run the manager on a 64 bit machine send a job and see if it works ?

[bhchllc]

I ended up just split scanlining it as a shorterm workaround to get this image out for a deadline but we will certainly be trying that as soon as we can afford to piss away 10 more hours on the renderfarm. I'll post a follow up when I have some results.