Page 1 of 1

OFX pluging failed to load

PostPosted: Tue Jun 15, 2021 2:39 pm
by Videoneth
The message used in the 17 Beta (I updated it to 17.2.1 now) was WAY better, one unique popup with a list with the OFX plugins, and ONE button to close it.

I would like to just have an unique message telling me some OFX plugins were not loaded (without blocking the access to the program).

Instead of having to close everything manually each time. It doesn't do that in Resolve

Re: Fusion 17.2.1 - OFX pluging failed to load

PostPosted: Fri Jul 30, 2021 8:38 pm
by Videoneth
The problem is still there with 17.2.2

using the "ESC" key is faster to make them disappear but it's still a bug imo

Re: [BUG] OFX pluging failed to load

PostPosted: Sun Sep 05, 2021 1:45 pm
by Videoneth
The problem is still here with 17.3.1

Re: OFX pluging failed to load

PostPosted: Sat May 14, 2022 10:29 pm
by Videoneth
:evil: Is it possible to do something?? These OFX plugins work on Resolve, but since they are in the same common folder, they creates these errors on Fusion Standalone

is it possible to get an option to bypass these errors? or do I miss something?

Re: OFX pluging failed to load

PostPosted: Sat May 14, 2022 11:33 pm
by Bryan Ray
You can create a blocklist to prevent Fusion from trying to load them. Do a forum search for ofx.blocklist and you should find instructions.

Re: OFX pluging failed to load

PostPosted: Sat May 14, 2022 11:54 pm
by Videoneth
Bryan Ray wrote:You can create a blocklist to prevent Fusion from trying to load them. Do a forum search for ofx.blocklist and you should find instructions.

Thanks, I think I found it.
Waaaa, this is complicated, it should be in the software itself. But it worked, I added the root path of the Red Giant Universe 80 plugins pack.

If someone find this post, go there for the "how to" : https://forum.blackmagicdesign.com/viewtopic.php?f=22&t=127650#p763288

Re: OFX pluging failed to load

PostPosted: Fri Jan 20, 2023 6:45 pm
by carsonjones
I just installed Fusion Studio 18 and am seeing this error window pop up many time when I launch the app. Is there a relatively quick fix or workaround for this?