All other major DAW developers included this VST3 feature. I think CW wants to have option to sell this VST3 platform twice. But they are not going to see my money on their account anymore. My opinion is that this is standard function of VST3 that should have been implemented, it is not something we must pay for extra. BTW nobody mentioned more important VST3 function yet...

BluerecordingStudios
Multi MIDI port isnt minor feature and IMHO it is one of the most important feature of VST3. Vienna Ensemble is used by professionals all over the world and if Sonar would like to be there, CW should react accordingly. If I search CW forum I can find numerous request of this feature even several years ago. Where is the problem, it is that hard to implement this in next X3 update?

+1. This is one of major reasons I can't work with Sonar anymore for serious film score work. VST3 support with VEPro and Cubase 7 is a Godsend. There's no way I could ever go back to working with such limited inputs...even Logic X is a PITA to work with in this regard (possibly worse than PT!!). I get the feeling Cakewalk isn't interested in the pro film composer community :(
Let's face it, most pro film composers use VEPro...it's a staple, especially for running large orchestral templates.
 
In addtion, the VST3 expression mapping is genius!

Well it's still gonna probably happen in X4 which is good news.
 
Oh and BTW:
 
"SONAR X3 delivers what other DAWs cannot offer, unlimited everything in all versions! You get unlimited simultaneous Audio & MIDI tracks, FX, Sends, and full VST3 support with our industry leading 64-bit mix engine. We believe that everyone deserves the full SONAR X3 experience." 
https://www.cakewalk.com/products/sonar/whats-new.aspx
 
So there is your ammo... Cake Marketing department will probably now run for cover...
I still don't need it (and I suspect most don't just yet), but please don't ever tell me that I'm not impartial ;)

It looks like we're going round in circles here. Please read this blog post to understand what VST3 is about. This information was posted about the same time that X3 was released.
http://blog.cakewalk.com/developer-notes-sonar-x3-vst-enhancements/
 
VST3 is a loose collection of interfaces that may or may not be implemented by either a DAW or a host. Even steinberg doesn't implement every aspect of the VST3 spec. For X3 we chose to implement a manageable subset of features that are supported by the vast majority of plugins. We decided to defer implementing this specific feature for a simple reason. It is supported by exactly one plugin and we didn't have the resources to do so for X3. We have finite resources and we have to pick the features we implement wisely. I have stated several times that we intend to implement this and we'll do so when resources permit.

.. which is fair enough and like I say, I would prefer to see the feature in X4 myself so most of your resources are concentrating on bug slashing, not keen on new features introduced in service releases myself unless it's the only way to squash a bug or a major usability problem. However the marketing blurb I quote above is factually incorrect and will need correcting I suspect, I'm not sure if there are similar quotes elsewhere.
 
Or are saying this isn't a VST 3 feature?

There is nothing factually incorrect with that quote. I'll say this again.
VST3 is a collection of interfaces that define a protocol for plugins and a host to communicate - that's it. VST3 itself doesn't contain any "features". It is up to the host and the plugin vendors to support any subset of features that the specification allows. This is exactly the same as VST2 or DX or any other standard. You can also build upon and extend the specification by adding extensions like we did with the Prochannel.
VST expression, multi port support, sidechaining, surround, plugin subcategories, parameter categorization, etc are all optional items. For X3 we chose to support the subset of items that were supported by the widest number of plugins. 
As an analogy SONAR or any sequencer for that matter does not implement every facet of the MIDI specification which was invented over 30 years ago. 
This thread has been answered multiple times. Its time to move on.

I understand, I think the confusion really is what does "full" mean in relation "VST 3 Support" from the end user perspective in a marketing blurb rather than what may be the technical reality. There is definitely an argument it could be misleading to the end user. Generally people think "full" means absolutely everything. Maybe it would be best to avoid this confusion?
 
I totally understand and sympathise with the explanation given however, the MIDI comparison is compelling. I still would prefer to see it in X4 rather than rush released in a service pack, and you have confirmed this to be so (more or less) which is good news for X4 (or X5 users maybe, although I would deem that extremely unlikely (pure speculation)).

Exactly. Cakewalk should know better than to advertise false features.
 
The OP's initial question relates to a feature that is most likely to be used by Sonar users.

'VST3 support is now fully integrated across all versions of SONAR X3. That means superior plugin management, low CPU loads, and improved visual workspace. It’s perfectly integrated into SONAR X3’s browser and shows you VST3 and VST2 plugins side by side.'

We explained the implementation pretty thoroughly when we launched. As Noel mentioned, we are one of a handful of DAWs that support VST3. We've received a lot of positive feedback and it wasn't an easy feature to implement. Of course there will be future developments to many features we develop and implement.