Instead of submitting scenes directly from Maxscript to Backburner, have cmdjob.exe run on Backburner, call up a copy of max and then run a script on it, with the script containing instructions to send a render job to backburner. So what you do is have a cmdjob task launch your actual render tasks. I can’t post actual code as this is for a paid job, but the basic process is this: cmdjob.exe can send jobs to backburner which have dependencies. The solution is actually relatively elegant now. – Using cmdjob.exe, the command-line backburner queue magician. Whilst this is potentially surmountable by checking to see what frame was rendered in the script, it also meant that each render node needed a licensed copy of Max if it were to open and close files. The problem here is that the post-render script is called every time a render server finishes its job – which might not necessarily be at the end of the actual job, of course. – Setting post-render scripts that perform a certain task when a render is complete. I managed to very vaguely get this working using dotNET but Telnet is not the most elegant of things, especially when in an automated system.
Autodesk backburner maxscript executemaxscript archive#
This is problematic as the only way to archive and unarchive a job (also not a function available via MaxScript!) is via Telnet, either through Python or dotNET. – Sending the job to backburner suspended, without any dependencies, then setting the dependencies by editing the (unused) XML tag in the backburner job folder, before archiving and unarchiving the job (so that the XML file gets re-read). There are a handful of options out there to try and solve this problem, namely…
![autodesk backburner maxscript executemaxscript autodesk backburner maxscript executemaxscript](https://src.onlinedown.net/d/file/p/2019-08-05/e61ff7a4eb8251b57efc9287619b99ee.png)
![autodesk backburner maxscript executemaxscript autodesk backburner maxscript executemaxscript](https://i.ytimg.com/vi/NtUiqkq8zvE/mqdefault.jpg)
Just submitting Max renders to Backburner using Maxscript isn’t a problem, though for some unutterable reason dependencies are not supported. I have today finally made progress with a problem I’ve been contending with, on and off, for a few weeks now! The problem is of using MaxScript and Backburner with dependencies.