What plugin format(s) do you use currently?

[rasmusklump]

Cubase thinks it has to pre-select what presets it shows to you in vst3 land.
You can have Presets in the right folder of a given plugin but when Cubase THINKS the presets don't belong to that plugin in it doesn't show them and you can't load them although they in fact ARE for that plugin. That's as stupid as it can get.

[Zeisner]

Using symbolic links can help with VST3 plugins and their presets. It can get quite messy though if you're using lots of plugins.

[VladK]

Because it's with every plugin that's got a name change for some reason.
Was never a problem with vst2 where you had a real folder selector box.
With vst3 you only get what steinberg preselects for a certain plugin. If I was able to chose the preset I am sure falcon would load it.

I would assume they not just changed plugin names, but also assigned new ID to these plugins. If plugin ID was changed, it is considered a different plugin according to VST3 standard AFAIK, not a different version of the same plugin.

[IvyBirds]

Because it's with every plugin that's got a name change for some reason.
Was never a problem with vst2 where you had a real folder selector box.
With vst3 you only get what steinberg preselects for a certain plugin. If I was able to chose the preset I am sure falcon would load it.

That's an issue with the way you have Cubase configured and not with Cubase itself. I don't experience any of those issues with Falcon or anything else

The first potential issue is that the VST2 version of any plugin uses 4-byte Hex Codes to identify itself to the system. This is a relic from the past as VST2 used simple 4-byte IDs as was common in the 1990s when VST2 came out, and they worked with Sysex coming from hardware Sequencers

That's a rather severe limitation on modern computers and DAWs so VST3 uses 128-bit Class IDs

Cubase doesn't see Falcon by name it sees a specific Hex Code expressed in 4 bytes The VST2 version is a separate plugin entirely than the VST3 version

You can remedy that issue rather easily in Plugin Manager. In Cubase, go to Studio > Plugin Manager and verify that both the VST2 and VST3 versions are active. You may need to check the box to turn on VST2

Cubase stores all of your presets in a Database. It sounds like your database needs to be updated. This can happen when you update a plugin.

So open the Media Bay from the menu or just press F5

Navigate to VST Presets > UVI > Falcon right click on the folder and select rescan

All your presets should now appear and work just fine

If you are storing your preset files in a non typical location on your hard drive you will need to point Cubase there, but it's easier just to keep them at the default location. In Windows that would be

C:\ProgramData\VST3 Presets\UVI\Falcon

If you custom made presets in the past with older versions if some plugins like Falcon they used to store them in

C:\Users\[YourName]\Documents\VST3 Presets\UVI\Falcon look there and if you see any move them to the current default folder

Any presets made in VST2 will be stored in C:\Users\[You]\Documents\VST Presets\UVI\Falcon\

Copy and paste the contents of that folder into the folder for VST3

C:\ProgramData\VST3 Presets\UVI\Falcon

Sometimes the issue isn't Cubase, but Falcon itself failing to "mount" the soundbanks that the preset relies on. So open Falcon, go to Preferences > Soundbanks. Ensure the path to your .ufs files is correct and that Automount is checked. If Falcon can't find the underlying samples, the Cubase preset will load an empty shell and not work

[Songsterr]

I’m strictly on VST3 and CLAP these days. Bitwig has been my main DAW for a while now, so CLAP support is a huge plus for stability and CPU efficiency. I’ve almost phased out VST2 entirely unless I’m opening some really old projects

Great to see devs asking for feedback, definitely focus on VST3/CLAP for the future-proofing