Blackmagic Forum

Just installed fusion 17.2 but it won't launch, even with dongle connected. DRV 17.2 no problem.
Dell G5 5587, windows 10, 32gig of ram, Nividia Geforce 1060 with 6 gig of Vram.

Try temporarily moving Fusion.prefs to a different location, that's what I did in 17.1.

Tried it but still does not launch.

This seems to be a problem with some services blocking the port that Fusion uses to communicate with the dongle. On Windows, Synology's CloudStation service (not the backup software, but the service that runs all the time) is one such. McAfee security is another that may block it. Seems like there was one more that somebody mentioned just within the last few weeks, but I don't recall what it was.

It might be possible to determine if this is the problem for you. Try starting Resolve, then once its running, start Fusion. I don't know if this test still works, but it did back in Resolve 15. If it does work, then it confirms that you have a software conflict of some kind. If it doesn't, then it may still be the case. Or it may not.

Tried to launch Resolve then Fusion, but it still would not launch.

Oh, I just remembered another possibility: Have you tried the dongle on a different USB bus? I've heard of problems with specific ports before, especially the pass-through ports on monitors and keyboards.

Good idea. I tried all ports on the laptop and it still does not launch. On my other computer it launches even without the dongle connected.

Same here. Fusion Studio 7. 2 quits before loading both in Catalina and Big Sur. It never happened before and I have no idea how to fix it. Am I missing something? Thanks in advance

Same here, Fusion 17.2 didn`t launch after update (17.1 worked just fine before) on Windows. Resolve works without any trouble. Also under MacOS everything works fine.

Same here..got this error
this application failed cannot load Qt platform plugin"windows"

acrux7245 wrote:Same here..got this error
this application failed cannot load Qt platform plugin"windows"

Did you tried that ?
viewtopic.php?f=22&t=141305

Nicolas wrote:

acrux7245 wrote:Same here..got this error
this application failed cannot load Qt platform plugin"windows"

Did you tried that ?
viewtopic.php?f=22&t=141305

Didn`t help, but my symptoms is different though

That Qt platform error should have nothing to so with python so no idea why that suggested fix even worked. It is one dll with platform specific stuff that qt loads and uses for its libs and should be in the install dir under platforms/ subfolder. As I understand it, problem arises when qwindows.dll file is found from PATH or QT_PLUGIN_PATH, which loads before the one in install dir. And if there is a mismatch (qwindows.dll is tied to Qt version used for building the application), you get this error. So one suggestion is to check if env variable QT_PLUGIN_PATH is set and clear it (back up its value just in case) and if this doesn’t solve it, go through folders in PATH and look for platforms/ subdir containing qwindows.dll file. If it exists, remove said path from PATH variable.

Like said, no QT_PLUGIN_PATH or PATH and no qwindows in python36 folder (even empty python36 folder crash Fusion 17.2)
And no problem on same machines with Fusion 16.x, 17.0, 17.1, 17.1.1

So Fusion 17.2 definitely broke something there.

Might be that they packaged wrong file with new version.

Did you solve this problem? I tried 17.2 today on Windows 10 and had no problem starting.

Having the same problem.
But unfortunately it seems there is no solution.
There are some support requests here in the forum because of the same issue.
And i wrote an email to BMD - but got no answer till yet.

If anyone else having a solution, it would be fantastic!

Same, did write to support last week, no news.

This 17.2 doesn't seems production ready at all, we didn't deployed it here stil 17.1.1

Same here, no solution. I updated OS Big Sur to version 11.4 which came out few days ago, hoping it will solve it, but all the same. I had to roll back to 17.1.1.

Mac Pro (late 2013)
3 GHz 8-core intel Xeon E5
64RAM
AMD FirePro D700 6GB

Still not solved. I have one version installed on my workstation on windows 10 that run without problem. Is the one installed on my laptop that doesn't launch. BM Support told me to reinstall the OS. I downgraded in 17.1.1 instead.

Seems ok with 17.2.1 !

Not for me!

Davinci Resolve 17.2.1 works fine in my system. But I cannot install Fusion 17.2.1 to this date after following several tips in this and other forums. It's very fustrating. I need Fusion Studio badly.

Can't install is a different issue than can't launch. Would you mind starting a new thread so we can dissect that one in isolation? Please include a description of exactly what happens when you try to install and your system specifications. I've not yet encountered an inability to install the software, so I probably won't be any help, but at least it will be easier to gather data in a separate conversation.

My mistake, I'm sorry. I can install Fusion Studio 17.2.1 alright, but it quits or crashes as soon as it launches. I had this problem before with previous versions when I had some OFX plugins installed but I removed them and that fixed the problem. Now I have Fusion Studio 17.1.1 installed and it has no issues but of course I would like to update to the new version 17.2.1.
My system specifications are:
Mac Pro (late 2013)
3GHz 8-core Intel Xeon E6
64 GB 1866 MHz DDR3
AMD FirePro D700 6 GB.

I appreciate your response, thank you.

17.2.1 won't launch for me either on Catalina.

I'm using a license key, not a dongle.
If I deactivate the license on 17.1.1, then install 17.2 or 17.2.1 and launch it, it will ask for license number, then it opens normally... just once....
After closing it, it won't open again.

Hi,

Same problem here.
Fusion 17 won't launch, or only will randomly start depending on the network I'm connected to.
So I'm stuck with 16, which is a shame as the new layouts really helped on a dual monitor system...
I'm on a i9/32GB RAM/RTX2070 Laptop running Win10, Fusion Studio USB dongle.
Is that actively being looked into ? It seems to be a serious issue from the number of comments.

17.2.2 won't launch either for me.

17.2.2 of fusion would not launch either. No problem with Resolve studio 17.2.2, this is weird. Resolve is quite bigger than fusion.

Same here. Fusion 17.2.2 doesn`t launch

Simon

Same thing, fusion studio 17.2.2. won't start, Davinci 17.2.2. works fine. No error message shows, just silence. Tried clearing settings and installing 17.2.1 but to no avail(

I may have found a solution, in the Nvidia Control Panel settings you have to force fusion studio to use a high performance video processor. After this setting was applied, Fusion Studio started up

AlexYez wrote:I may have found a solution, in the Nvidia Control Panel settings you have to force fusion studio to use a high performance video processor. After this setting was applied, Fusion Studio started up

Good to know there might be a solution for windows, unfortunately there is no such a thing in OSX. Hopefully it will help BMD to solve the issue.

I installed Fusion Studio 17.2.2 and again It open briefly and quits or crashes. I also hope BMD can helps us fix this problem.

AlexYez wrote:I may have found a solution, in the Nvidia Control Panel settings you have to force fusion studio to use a high performance video processor. After this setting was applied, Fusion Studio started up

Yep. Now it launches. Thanks for the tip.

And thank you for the confirmation! I'll add that solution to my troubleshooting list. Some clarification please: Is this something that only shows up if you have multiple graphics processors available? I don't see it in my Nvidia control panel. A screenshot would be appreciated.

Today I have installed the new NVIDIA Studio Driver 471.41.
Now Fusion launch without problems.

Simon

Hi, everyone.

I'm having a project which I would need to use Fusion. I have an existing license for Resolve, but it would be more convenient to use standalone Fusion. As the same license should work I installed Fusion Studio 17.2.2, but I have same problem as many others in this discussion. At startup Fusion window opens and briefly has a text "Checking for License". Then it closes by itself without any error message. Below is list what I've tried, but is there anything else someone would know that I can try to get it working?

System:
- Laptop PC, Windows 10, AMD Ryzen 9 5900HX, 32gb
- Radeon GPU + mobile Geforce RTX3080 12gb
- External Display + Laptop Display

Tried:
- Fusion Studio 17.2.2 & 17.0
- Resolve open & not open same time as launching Fusion
- Updated latest Nvidia Game ready drivers (471.41)
- Closed all processes related to Synology NAS backup
- Deleted Fusion.prefs file
- Disabled Windows Firewall

Thanks.

Has everyone else succeeded getting Fusion running or is there others who still have the problem?

I’d be happy to hear suggestions what to try next. I don’t know if my issue is problem with license check during start or something else so it’s hard for me to find a solution. Is Fusion creating a log file during startup that would have relevant information?

Saku Partamies wrote:Has everyone else succeeded getting Fusion running or is there others who still have the problem?

Everything works as usual

For those who still have problems launching Fusion Studio 17.2.2 but can launch 17.1.1 without any issues, this could help:
1. Open Fusion Studio 17.1.1, go to window>view layout>reset layout to default (which means that Fusion layout should be visible only in one monitor if you have been working with two monitors), then go to preferences>global and Default Settings>Layout and click on Grab program layout and Save. This will reset Fusion layout to default. Then quit Fusion 17.1.1.
2. Install Fusion 17.2.2, restart and open Fusion.

This worked for me.

Thanks for that update!

I can add that when I first ran 17.2.2, it crashed within a few seconds of opening every time. I had to delete my Fusion.prefs file. Maybe if I'd tried resetting the UI first, that would have solved it, but I didn't try it.

Then the other day I suddenly got into the same crash situation, or similar anyway. I opened Fusion and it would suddenly crash within 30 - 90 seconds.

Moving my Fusion.prefs solved it again, so I compared what was different in my current prefs to a backup from a few days earlier. I eventually found the culprit:

Code: Select all

   EnvironmentVars = {
      FUSION_Log = "false"
       },

Earlier that day I had noticed Help -> Logging, and had enabled it:



It didn't actually seem to generate any extra logs at all. What it did do was cause Fusion Studio to die every time I subsequently opened it.

TLDR: Don't use Help -> Logging! At least on macOS, it adds a Fusion.prefs value that breaks Fusion Studio, and even toggling it off again doesn't fix it, because the mere presence of the EnvironmentVars -> FUSION_Log code I showed above is enough to bring down Fusion.

Attached is a crash log, in case anyone from BMD sees this (when I have time I'll report it direct to BMD support). I note that the top of the stack trace is:

Code: Select all

Thread 0 Crashed:: GUI Thread  Dispatch queue: com.apple.main-thread
0   libsystem_c.dylib                0x00007fff2034205d __findenv_locked + 52
1   libsystem_c.dylib                0x00007fff20342161 getenv + 54

"findenv" and "getenv" being related to environment variables, which fits with those new lines added to Fusion.prefs - adding (or checking for) FUSION_Log environment variable.

So it would seem that maybe Fusion Studio's environment variable handling is broken in Fusion Studio 17.2.2 - at least on macOS. I've not yet tested Windows.

Fernando Vargas wrote:For those who still have problems launching Fusion Studio 17.2.2 but can launch 17.1.1 without any issues, this could help:
1. Open Fusion Studio 17.1.1, go to window>view layout>reset layout to default (which means that Fusion layout should be visible only in one monitor if you have been working with two monitors), then go to preferences>global and Default Settings>Layout and click on Grab program layout and Save. This will reset Fusion layout to default. Then quit Fusion 17.1.1.
2. Install Fusion 17.2.2, restart and open Fusion.

This worked for me.

So far, it's working for me too on Big Sur.
Thank you

In 17.3 I've the same problem, I think...

I'm on Fedora 34.

Even if the dongle is connected, the "Activation Key" request appears and asks me a license key where as I have the USB Dongle.

It appears that FusionServer is not able to start:

Code: Select all

QSocketNotifier: Can only be used with threads started with QThread
DNX SDK API version 2.6.1-19-r
libDeckLinkAPI.so: cannot open shared object file: No such file or directory
Unable to read VR Path Registry from /home/eoyilmaz/.config/openvr/openvrpaths.vrpath
10:09:53,893 | INFO  | GPUDetect          | Starting GPUDetect 1.1_3-a5
10:09:54,060 | DEBUG | GPUDetect          |   - System Info: 166 ms.
10:09:54,076 | DEBUG | GPUDetect          |   - OpenCL: 3 detected in 16 ms.
10:09:54,078 | DEBUG | GPUDetect          |   - CUDA: 3 detected in 2 ms.
10:09:54,092 | DEBUG | GPUDetect          |   - Xorg: 3 detected in 13 ms.
FusionScript Server [35826] Started
Host 'Fusion' [35794] Added
10:09:54,115 | DEBUG | GPUDetect          |   - NVML: 3 detected in 22 ms.
10:09:54,115 | DEBUG | GPUDetect          |   - GPU Matching: 3 matched in 0 ms.
10:09:54,115 | INFO  | GPUDetect          | Done in 221 ms.
10:09:54,115 | INFO  | GPUDetect          | Detected System:
10:09:54,115 | INFO  | GPUDetect          |   - OS: Linux Fedora release 34 (Thirty Four)
10:09:54,115 | INFO  | GPUDetect          |   - Model: ASRock X399 Professional Gaming
10:09:54,115 | INFO  | GPUDetect          |   - System ID: 6112bf8a278f4b27af335d7395255a68
10:09:54,115 | INFO  | GPUDetect          |   - CPU: AMD Ryzen Threadripper 1900X, 16 threads, x86-64
10:09:54,115 | INFO  | GPUDetect          |   - RAM: 8.7 GiB used of 125.7 GiB
10:09:54,115 | INFO  | GPUDetect          |   - NVIDIA GPU Driver: 470.63, supports CUDA 11.4
10:09:54,115 | INFO  | GPUDetect          | Detected 3 GPUs:
10:09:54,115 | INFO  | GPUDetect          |   - "NVIDIA GeForce RTX 3090" (gpu:3bdb9858.0b957bcf)
10:09:54,115 | INFO  | GPUDetect          |     Discrete, 7 MiB used of 22.6 GiB VRAM, PCI:8:0.0
10:09:54,115 | INFO  | GPUDetect          |     Matches: CUDA, NVML, OpenCL, XOrg
10:09:54,115 | INFO  | GPUDetect          |   - "NVIDIA GeForce RTX 3090" (gpu:3bdb9858.5ad4b8df)
10:09:54,115 | INFO  | GPUDetect          |     Discrete, 7 MiB used of 22.6 GiB VRAM, PCI:9:0.0
10:09:54,115 | INFO  | GPUDetect          |     Matches: CUDA, NVML, OpenCL, XOrg
10:09:54,116 | INFO  | GPUDetect          |   - "NVIDIA GeForce GTX 1050 Ti" (gpu:10ade2ed.5f245765) <- Main Display GPU
10:09:54,116 | INFO  | GPUDetect          |     Discrete, 640 MiB used of 3.7 GiB VRAM, PCI:66:0.0
10:09:54,116 | INFO  | GPUDetect          |     Matches: CUDA, NVML, OpenCL, XOrg
10:09:54,116 | INFO  | GPUDetect          | Detected 1 monitors:
10:09:54,116 | INFO  | GPUDetect          |   - "Monitor" <- Main Monitor
10:09:54,116 | INFO  | GPUDetect          |     2560x1440, connected to "NVIDIA GeForce GTX 1050 Ti" (gpu:10ade2ed.5f245765)
QWidget::setLayout: Cannot set layout to 0
QWidget::setLayout: Cannot set layout to 0
QWidget::setLayout: Cannot set layout to 0
Host 'FusionServer' [35846] Added
Host 'FusionServer' [35958] Added
Host 'FusionServer' Removed
Host 'FusionServer' Removed
QWidget::setLayout: Cannot set layout to 0
QWidget::setLayout: Cannot set layout to 0
Host 'FusionServer' [36484] Added
Host 'FusionServer' Removed
QWidget::setLayout: Cannot set layout to 0
QWidget::setLayout: Cannot set layout to 0
Host 'FusionServer' [36780] Added
Host 'FusionServer' Removed
QWidget::setLayout: Cannot set layout to 0
QWidget::setLayout: Cannot set layout to 0
Host 'FusionServer' [37205] Added
Host 'FusionServer' Removed

EDIT: Fusion 17.3 launches without any problem in my work computer. The problem is in my home computer.

Finally I also got Fusion Studio running. I installed 17.3 and that works without a problem
I use 100% same computer and system setup and only difference is the Fusion version. 17.1 and 17.2 didn't start no matter what I tried.

Hopefully this latest version works for everyone else as well.

TheBloke wrote:TLDR: Don't use Help -> Logging! At least on macOS, it adds a Fusion.prefs value that breaks Fusion Studio, and even toggling it off again doesn't fix it, because the mere presence of the EnvironmentVars -> FUSION_Log code I showed above is enough to bring down Fusion.

This has been fixed in 17.3.1. Thanks for that.

After I updated Fusion to 17.3.1, I still had the problem. But, I think I found a solution;
starting FusionServer by hand solved my problem.

I also set the SELinux context for the FusionServer executable from "unconfined_u:object_r:usr_t:s0" to "system_u:object_r:initrc_exec_t:s0". This may helped too, I didn't check it. But Fusion runs properly now.