Can confirm

Waves told me they only support VST3 now, not VST2...

bitflipper
If an effect or instrument ships with both VST2 and VST3 versions, why on earth would you want to use the VST3 version (if you're not a Cubase user)? Is it the ability to save preset names in Chinese?

Well, it's one better, isn't it? It's not two. You see, most blokes, you know, will be playing at two. You're on two here, all the way up, all the way up, all the way up, you're on two on your VST. Where can you go from there? Where? - This one goes to three!
There are a few potential features that could be added in VST3 but I seriously doubt if Sampletank 3 or the Arturia instruments that caused me problems use any of them.
 

bitflipper
If an effect or instrument ships with both VST2 and VST3 versions, why on earth would you want to use the VST3 version (if you're not a Cubase user)? Is it the ability to save preset names in Chinese?

Well, if the plug-in AND the host implement the "only draws CPU power when actually doing stuff" feature, that would be useful. But I don't know how common that is yet.

Here is the list of changes made in the 3.0.1 update; hopefully you guys can report back if this fix, helps with the issues with Sonar and ST3.  Here is the list of changes:

Changes from version 3.0:

▪ Fixed issue with Big Pig pedal
▪ Fixed possible crash opening Settings Dialog in StandAlone version with a non-available Device selected
▪ Fixed possible crash opening Settings Dialog in StandAlone version with a non-available Device selected
▪ Fixed possible crash on startup with some ASIO Drivers
▪ Fixed crash on drive missing for ST3 Disk Path
▪ Effects Presets folder moved inside the Disk Path
▪ All content folders are now created automatically if they do not exist
▪ Fixed a bug that made MIDI CC assigned to element and zone parameters to not save and restore correctly
▪ Fixed a bug that when importing samples, made data from editable fields not reflecting the latest user input
▪ Fixed possible "boost::filesystem::remove" error while importing legacy instruments
▪ Fixed a possible mismatch between macros description in the info panel and macros enabled/disabled in the macro panel after loading legacy instruments
▪ Fixed Import of modulations from legacy instruments contained in the Xpansion Tank Vocal library
▪ Fixed possible BPM SYNC issues with certain hosts
▪ Fixed a bug when importing some kind of WAV files
▪ Fixed a possible issue when writing automation parameters on certain hosts

I have not yet had time to install ST3, but I had a question, this was IK's reply:

As for SampleTank 3 not working correctly in Sonar, we have received reports of 
this, but have not been able to replicate any issues with SampleTank 3 when used 
as a VST 3 plug-in in Sonar X3e build 352, used in either Windows 7 64-bit or 
Windows 8 64-bit operating systems. 

I'm NOT ranting or even questioning, BUT
 really?
Tom

DeeringAmps
I have not yet had time to install ST3, but I had a question, this was IK's reply:

As for SampleTank 3 not working correctly in Sonar, we have received reports of 
this, but have not been able to replicate any issues with SampleTank 3 when used 
as a VST 3 plug-in in Sonar X3e build 352, used in either Windows 7 64-bit or 
Windows 8 64-bit operating systems. 

I'm NOT ranting or even questioning, BUT
 really?
Tom

Maybe the VST3 fix will be another over ten years in the making?
 

Didn't Bit say it all?
"why on earth would you want to use the VST3 version (if you're not a Cubase user)?"
Who cares about VST3?
T
 

Skyline_UK
Why should I accept that I bought a product and part of it is broken?  We wouldn't accept this any other purchased item but for some reason we're willing to accept it when it comes to software; probably because we're conditioned by buying so much duff software over the years that in various respects turns out to be unfit for purpose.
 

Agreed that software needs to undergo more extensive compatibility testing...as we've seen with EZ Drummer 2 etc. I of all people know how tiny these companies are; if they lack sufficient staff for compatibility testing, I'd like to see more use of public betas. Propellerheads and Ableton have done that, which I think may contribute to the stability of their software upon launch.
 
There are two mitigating factors that provide some degree of consolation. First, more companies are making trial versions available so people can do their own compatibility testing. Granted, we shouldn't have to do a company's work for them but if they can't/won't for whatever reason, then at least we have an option. Second, unlike something like a toaster, software can be a work in progress and be fixed. In the case of IK, they have a history of coming out with bug fixes relatively rapidly. Amplitude was crash city when the 64-bit version appeared, but IIRC it was fixed within a month. Until then i used the older version; frustrating, but not the end of the world.