"3ds Backburner adapter has stopped working"

[depictstudio]

Hi All,

 

Having major issues with our backburner here. Any advice is greatly appreciated.

P.S. We've just set it up so hasn't just started going wrong after working.

 

Basically when sending a Backburner render from our main machine to 3 other workstations 2 machines are failing with the following message: "3ds Backburner adapter has stopped working"

 

Running: 3ds max 2014 SP5

 

Cheers

Adam

[Scott Schroeder]

Is your backburner dialog throwing any errors? The one where it says if it's connected to the manager and all of the plug-ins it is loading.

 

Are you using IPv6? That is a known error causing bug with backburner. Have you installed this backburner, http://knowledge.autodesk.com/support/3ds-max/downloads/caas/downloads/content/backburner-2014-windows-version-for-3ds-max3ds-max-design-2014.html or the one that stock installed with 2014? If you have installed the stock 2014 backburner, try installing the one from the link and see if that fixes it.

[depictstudio]

No errors which is slightly confusing.

No not using IPv6.

I think its the 2014 version installed, will double check that now. Thanks for the help Scott.

[Scott Schroeder]

Also, make sure that backbuner has admin level rights to the machine and that it's not being blocked by a firewall anywhere. Double check that all necessary plug-ins are licensed correctly as well.

 

If you start max normally on those machines, does max launch by itself?

[Matt McDonald]

If you start max normally on those machines, does max launch by itself?

 

That's a very good place to start troubleshooting.

[depictstudio]

Cheers for all the help guys. Basically we ended up finding that the Controller Adapter in Backburner for our main machine sending the images was missing. Upon various attempts to re-install backburner, then re-install Max, we found that this did not fix the issue. Steps taken including amending the registry and running CC Cleaner to no avail. The solution was to do a format and re-install which resolved the issue. We suspect that the installation of max 2015 was the trigger, as all was working well until this point.

 

All working now.

 

Cheers again