yannis wrote:Strange behaviour indeed!
Correct me if I'm wrong, but it seems that Fusion 16 now only uses DCTLs code for plugins, which makes older ones available until Fusion 9 (Studio only, never the free versions).
Most developers are waiting for the new SDK to upgrade their Fusion OFX and plugins.
You're conflating three different things.
DCTL is necessary for writing GPU-driven Fuses. It replaces the OpenCL Fuse support that was present in previous versions of Fusion. OpenCL Fuses will run in the free version of Fusion 9. I haven't looked into DCTL Fuses yet, but OpenCL Fuses run in the free version of Fusion 9. I imagine DCTL will run in the free version of Resolve 16, but as I said, I haven't investigated it yet.
The SDK is required for making native Fusion plug-ins like Krokodove, CustomShader3D, and Lit Sphere. These plug-ins cannot be updated until the new SDK is available.
OFX plug-ins do not depend on the Fusion SDK and should operate in Beta 16,
but the plug-in vendor needs to add Fusion support. I don't know the ins and outs of OFX development, but I would think at the very least the plug-in would require a Fusion control panel.
edit: I just tested Neat Video, an OFX plug-in. It works in Fusion Beta 16.
nbyteFX wrote:And I thought that resolve 16 and fusion 16 share the same foundation - program wise!
Fusion 16 and the Fusion
page in Resolve 16 share a code base. I expect the plug-in you're trying works on the Edit page, but not on the Fusion page, yes?