Cubase automatically replaced the VST2 plugin Komplete Kontrol with the new VST3 version when opening an “old” project. VST2 Halion6 has also been replaced with VST3 Halion7.
Somehow there seems to be a plugin ID, and somehow the automatic replacement seems to work!
So basically what has happened is that if you already had the VST2 SDK, then you can keep using it. If you did not (typically because you are a developer who got into the business after Steinberg blocked access to the VST2 SDK, then you had no choice but to switch to VST3 only.
That said, VST2 plugins seem much more reliable and so unless you have no choice but to switch to VST3, I would stay with VST2 as long as possible - that’s certainly what I am doing.
If GP were just starting out now, we probably would not have been allowed to support VST2 plugins!
I haven’t updated any of the plugins I use in my live performance rig in years — if they aren’t broke…
Much as I am an early adopter when it comes to stuff on my desktop, my live performance system stays as stable as possible — still running macOS 10.14 on it even though there has been 11, 12 and 13 (apparently very buggy) in the last few years
Yes, that’s strange, but true. I tried it again with other old Cubase projects: Komplete VST2 is simply replaced with the new Komplete VST3 when the projects are opened. Without any problems. And that even now, when I have the old VST2 and the new VST3 on my computer as described above!