Backburner Monitor Queue Control Weirdness

[roy_baker]

After updating our Backburner Manager, Servers, and Individual Workstations to 2014 we are now experiencing a weird error when requesting Queue control in the Monitor: When a user request control and is granted either via time expiration or explicitly given, the requesting user's Monitor will immediately act like the other user is requesting control back. Of course this is not the case and the requesting user has to select Deny to keep control. Any ideas?

This farm has been in existence for over 11 years using Backburner, updating to new versions when they are released, servers coming and going, and has never displayed this type of weirdness before.

[jneilon]

Yes we have the exact same issue. It is unusable as it is. We had to downgrade back to Max 2012 and wait for a fix. The other issue is that it does not generate errors for missing plugins anymore so it will just render regardless.... 

[samab]

---

@roy_baker wrote:
 

This farm has been in existence for over 11 years using Backburner, updating to new versions when they are released, servers coming and going, and has never displayed this type of weirdness before.

---

I still use BB 2008.1.1, because it works.

[jneilon]

Roy if you need to use Max 2014 you could look at alternative render managers. There is a list here

[Kreaction]

Yes exact same bug here since 2014 is on the renderfarm.

Anyway, going back to 2012 foe that is a bit overhelming ... Just click deny and that's all. But yes, it is annoying, specially regarding the price of subscription !!!

[jneilon]

We use scripts to submit to Backburner that use the request queue control command. This is no longer possible to use since its so buggy. We are stuck in using Max 2012.

[dbhinnant]

The problem I am having is the Monitor will not remember Queue Control.  I have to request it almost every time I want to do something.  It is also failing to refresh randomly.  If Backburner is not overhauled soon, we will be faced with canceling our subscription and not upgrading Studio Max anymore.  Maybe we are a small percentage of customers but Backburner is vital to our workflow.  It gets more bug laden with every new release of Max.

[zoubein]

I am also having this weirdness . Is the only option to go back to 2012?

Thanks

[jneilon]

Yes it is completely broken. We had downgrade back to Max 2012. Your only other option is to buy deadline or try smedge, royalrender etc...

[zoubein]

I guess we have no choice then. I was wondering i seem to get quite a few "the pipe has ended 109" messages when I send renders from 2014 to backburner 2012. anyone else experience this?

[Midge_S]

I've noticed very buggy behaviour with machines where Backburner was upgraded instead of doing a fresh install.

One farm has old Backburner installs present and gives all kinds of weird behaviour.

The other one had everything installed from scratch with only Backburner 2014 and doesn't have any of the problems present in the first.

[Hwagner]

the only issue i have seen on my system is 2013 can not use the 2014 backburner. not really an issue but just annoying. although my computer has a fresh install of all software.

[omri]

You could try uninstalling backbuner and installing an older version of backburner.

But do it on ALL machines, or you will get lots of strange behavior

We stayed on bb 2008 until we installed max 2014 with bb2014.

And yes a bughunt over backburner would be nice. We have seen lots of funky behavior with some servers not using maps they should be able to get to etc.

[jneilon]

Max 2014 with Backburner 2014 was released in April 2014 it is February 2015 and still there isnt a fix. I suppose we have to wait for Max 2015?

[zoubein]

Yeah I just had to roll back to 2012 in the end. I guess its a good time
to look into 3rd party managers.

[StevenBrodie6063]

Can Autodesk address this issue, as its becoming impossible to use.