So mostly works for first release, but known not to work:

• audio buses setup
• keyboard handling is flaky
• cv not implemented, though ports are tagged as cv ports already

likely other stuff is broken, the vst3 stuff in DPF is quite new and not very well tested yet

Before anyone asks, seems the VST3 doesnt work on Ableton.
Don't know why yet.

Modwheel/MIDI CC support seems to not work in VST3 as well (at least on my Reaper Win8 64bit setup).

This is probably a known issue already, but I figured I'd mention it in case it helps with this issue. I use Studio One 5.5.2 (Windows 64bit), and the VST3 version of Cardinal lacks any interface whatsoever. VST2 seems to be working, so there's no rush. I just thought I'd mention this in case it helps.

Hi, if i try to grab the bottom-right triangle to resize the Cardinal window nothing happens. The triangle isn't draggable.

issue: display
os: Win11x64
commit id: 62181c1
reaper: v6.60
bespoke: 1.1.0 Nightly May 3 2022 (latest win release on download page)

Resizing and changing scaling settings appears to make no difference.

Screenshots: https://imgur.com/a/MoHe0Qj

Issue not seen with 22.05

Improvements coming in 22.06, to be released tomorrow.

MIDI CC input is now handled, and UI works better.
I was also able to load it in Ableton Live, though only FX and Synth variants. The "main" variant still does not load.

When I tried to open the VST3 version (v22.07) in Studio One 5, Studio One crashed immediately.

Last few days I been searching on this topic with no clear answer.
22.07 VST3
Ableton Live 10.1.43
Big Sur 11.5.6
I can use Cardinal and play external Midi into the plugin however AU, or VST3 versions do not allow me to send out. Totally greyed out on Host Midi Module so not even an option to send internally.
Midi Time works to sync Sequencers from the host (Ableton), and of course I can use external keyboard to play synths.

Is this a limitation or something obvious I missed?

AU MIDI out does not work at the moment, but VST3 MIDI out for sure works. I had it running just a few days ago while testing for other things.

Please see this is greyed out.

that is a label, for separating options related to input and output.
so basically you have:

1. input only options
2. output only options
3. input + output options

@falkTX Thanks for the fast reply, and I confirm it works now. Missed the obvious, but I couldn't find any documentation.
Suddenly I do not miss my Doepfer MAQ 16/3 anymore :D

VST3 generally works well in Ableton on Windows 10, although delay compensation is broken. It always shows 0 samples even on more complex patches and goes out of sync with the rest of the project.

I keep forgetting to ask; are there any VST3 hosts that implement the VST3 version of CV ports (like LV2 has)?

It is part of the spec, so I suspect there is at least one...
But I dont know of any myself.
Carla will get there eventually, but it is not ready yet.

As of latest nightly, I consider VST3 support stable.
For those not wanting to use nightlies / action builds, wait until 22.09 official release for all the fixes