Page 1 of 1
Fusion license stopped working :oops:

Posted:
Mon May 26, 2025 7:31 pm
by Jon Angelo Gjetting
On a Macbook M3 max, macOS 15.5, Fusion 18 and 19. I only run this license on this one computer.
My fusion license stopped working. When it happened earlier it worked to just enter my activation code again. Now that does not work, and I am about to blow a deadline as the render is going live tomorrow morning early. What do I do?
Yes I've uninstalled and reinstalled. Rebooted the computer.
Called Blackmagic UK, and US. Wrote a mail. No joy. Chanted 'please suck less' while crying and lastly sacrified a goat. None did that matter.
Any help will be appreciated.
Thank you.
/Jon Angelo
Re: Fusion license stopped working :oops:

Posted:
Tue May 27, 2025 5:28 pm
by Chris Duncan
I think your problem is the goats. I recommend chickens, along with burning incense.
I upgraded Resolve Studio from 17 to 19 earlier this week and was never prompted for an activation code, presumably it just used what was already there from 17.
Today, it prompts me for the activation code. I entered it, saw it scrolling through no licenses available, then apparently deleted the least recently used seat, and finally came up as normal. A couple of shutdowns / restarts and I still get no prompt.
I'm posting this mainly to offer corroborating data that sometime in the last 24 hours something seems to have changed in the activation system and affects Resolve as well. Although I didn't have to resort to chickens or goats, it seems like something got broken.
Re: Fusion license stopped working :oops:

Posted:
Wed May 28, 2025 10:48 am
by Jon Angelo Gjetting
Oddly it works again, for now. The chicken sacrifice must have done it.
And did something change at the Blackmagic end? -if so what?
Lastly what can I do to make sure that much loved and depended on tools keeps working?
Re: Fusion license stopped working :oops:

Posted:
Wed May 28, 2025 5:47 pm
by Chris Duncan
My gut feeling is that this falls under a common software term known as, "Stuff Happens." They were probably doing some back end work, someone jiggled the wrong wire, they realized it and plugged it back in, and no one really wants to be the one who admits to said jiggling.
In any event, glad you're back up and running. And for what it's worth, in my experience, it's chickens for software and you only resort to goats if it's hardware. Burning of incense is required in either scenario.