Yeah, it could be down to the graphics card/driver and how well/badly certain graphics calls are being handled. But whose responsibility is it to investigate/resolve that?
 
Should Craig or anyone encountering a similar issue be left with no other option than to cope with higher latency (or perhaps turn to their DAW PC builder to troubleshoot)?
 
After all, it's a plug-in which CW have specifically bundled-in with X3PE and which only works with X3PE, not just some 3rd party plug-in which Craig or you already happened to have. So it wouild seem reasonable that CW would have tested it for compaitibility on various systems, and that CW would at least make some effort to investigate any issues which might arise (even if the user encountering an issue doesn't happen to work for their corporate parent).
 
(I'd guess it's actually being looked into further, at least would hope so)

Goddard
Yeah, it could be down to the graphics card/driver and how well/badly certain graphics calls are being handled. But whose responsibility is it to investigate/resolve that?
 
Should Craig or anyone encountering a similar issue be left with no other option than to cope with higher latency (or perhaps turn to their DAW PC builder to troubleshoot)?
 
After all, it's a plug-in which CW have specifically bundled-in with X3PE and which only works with X3PE, not just some 3rd party plug-in which Craig or you already happened to have. So it wouild seem reasonable that CW would have tested it for compaitibility on various systems, and that CW would at least make some effort to investigate any issues which might arise (even if the user encountering an issue doesn't happen to work for their corporate parent).
 
(I'd guess it's actually being looked into further, at least would hope so)

Well, I certainly don't expect Cakewalk to test every possible permutation of graphics card/driver combinations in existence (especially the less common ones) for every third-party plug-in included with Sonar. The fact that the full version doesn't have this problem would indicate there's some difference compared to the Producer version, and I would hope that Overloud is looking into it.
 
However...I did find out that my card was supposedly not capable of doing Aero, but a very recent driver update (which I installed) allowed for Aero functionality. I tried turning off Aero without solving the problem, but will try rolling back to the previous driver when I get some time to see if that's a solution. If it is, then neither Overloud or Cakewalk would have found the problem because the new driver didn't exist until after X3 was released.