maybe it´s a problem with 32 and 64 bit… job is 64bit and manager runs on 32 bit…
there is such a file chaos with the last 3dsmax installations…everywhere the same named files…i have no check why this…
…so on my system here i have a backburner.xml in the folder of the backburner installation, one in the 64bit root of max in the network folder,one in the 32bit root of max in the network folder, and with max2008 i get one in a network folder that gets written in a direction where i save a new job irrmap (or picture)…
tomorrow i will edit all of them on the manager and renderclient…and i try to run the manager on a 64 bit machine…maybe this helps…
BB is full of bugs and misses several commandlines like “-ContinueOnError:1”
very helpfull if plugin are missing or a texture popup causes missing map error
unfortunaly are some cmds from the 3dsmaxcmd.exe not working
try to chance gamma values and you feel the pain
BB is working in the most cases but in special terms it sucks
that threads me to use a real rendermanager
beside that is BB not made nor supported by Autodesk
its a gift someone wrote in his sparetime
-------
just setup the scene ready to render -save path - frame ranges - etc
open cmd and execute
c:\path to max\3dsmaxcmd.exe “C:\path to scene\xx.max” -v:4 -rfw:1
and you can render forever
ps:
even I could not get rid of the timeout bug
i wonder someone could ?
I just wanted to agree with the previous post. 64 bit servers must have a 64 bit manager in order to properly set certain properties, one of which is the task timeout setting. Running Monitor on a 64 bit machine also correctly displays the frame numbers in the Task ID column, rather than “Task 1-301” or whatever, and of course you can’t edit settings for 64 bit jobs from a 32 bit monitor.
