Sunday, February 2, 2014

Backburner running as service

If you're using Autodesk Backburner to control your network rendering and you have backburner set up to run as a service across your network, you've probably noted in Windows 7 that if you're using a local domain for your network, you need to use a login account for the service that has top level domain privileges. Otherwise, the service will have trouble talking to the manager.
What you may not have known is exactly which account 3ds max is using when it starts as a render service. You might have thought it was the login credentials you used to authorize the service or perhaps even the current user, but you'd be wrong. Backburner is using the account of the user who installed the software. Now if you have a well organized studio or even a small one of your own in which all this has been taken care of by a single individual, this probably hasn't been a problem. But when backburner rears its head and the log starts telling you about missing configurations this is a real difficult problem to nail down, especially with plugins, startup variables or map paths to network locations.
Happy Rendering! (OK, with backburner that's probably a lot to wish for...)

No comments:

Post a Comment