Running windows vsts on Linux depends on Wine, so any program (DAW or whatever) that tries to run windows vst's on Linux is then very dependent on Wine's current capabilities which can change with different Wine versions and hardware/driver setups.
Running windows vst's on Linux is basically similar to running windows games on Linux, and sometimes Wine has missing bits that might get filled in later on and/or can be adjusted by real extra dll's and/or by tweaking certain settings.
D3D Wine/hardware driver problems are pretty common (can be tweaked) and having to use extra real dll's is pretty common as well.
The Wine D3D stuff is going through the Linux opengl driver, so a good opengl driver setup will help and there are various options depending on the opengl driver Nvidia etc and there is also xorg.conf setups for glx loading etc for some drivers.
Wine audio setup (wineasio etc) doesn't come into it for windows vst's running under a Linux native host, because the audio is handled internally by the host and whatever it's doing with Alsa/Jack.
I've picked up on that Wine seems to handle multiprocessing in ways that can interfere with what some windows programs might expect and also some GPU acceleration things can throw Wine for a loop as well.