Yes, i got crashes, too, when using them bridged - Sorry if I misled what i was doing -
I was only bridging to test them, as I have had others do the same.

As i suspected the VST3 seems to be a problem, so what I did was to move them to a folder I named "VST3 hold". (path= "Program Files\Common Files\VST3 hold\Kush\"). I do that so the scan will not find them, and will only see the VST2 version.

I COULD just rename them to "Goldplate.VST3.hold",etc, but moving them give a bit better way to quickly see what VST3 versions of different plugins are giving problems.

If you use the FL Browser and don't customize the Database then you should just be able to use the one that shows up when browsing to select.
They both seem to work fine in the VST2 versions. (I will test others mentioned here in the same kind of way)

If you DO customize your Plugin Database menu like me, and you made a shortcut (Goldplate.fst or UBK-1.fst) in the Plugin Database menu from the VST3 version, you will need to replace it with the VST2 one after the scan. (Looking in the 'Plugin Database\Installed\Effects\VST\)
Of course, if you do customize, you probably already know that, but anyway .... hahahha

 

@Jim Von Gucci & @PrettyPurdie :
What packages are you using of Scaler?
I have the [Scaler.2.v2.1.0-R2R-2020.09.16] & [Scaler.v2.2.0.Fixed-p2p-2020.12.20]
(not exact names of the posts, but the dates & versions are the key)
I am going to try the p2p from 2020.12.20 and see...
If it is a problem, i'll check if it is only a VST3 issue...

V2.2 seems to be working fine here- System: [Windows 10 ,1909 ] [FL Studio 20.7.2 (build 1863)]

 

Last edited: Jan 15, 2021

I had the same problem before. I uninstalled UBK-1 with revo uninstaller, installed previous K'ed version of UBK-1, and installed the latest release on top of that which worked for me.

 

I have the latest FL Studio version 20.8 because i bought fl studio . im also a legit owner of scaler 2 .
i reversed back to scaler 2.1.0 R2R for now, i guess its a problem with the latest FL version, but ill just wait for an update on both side and i think patience is the best solution right now

 

I have it and it works, I found a workaround for Liquidsonics too. Try enabling the "make bridged" and "external window" when loading the plugin